Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Feed
All
Post Types
- Rants
- Jokes/Memes
- Questions
- Collabs
- devRant
- Random
- Undefined
Cancel
All
-
Me: "can we go to the cinema this weekend?"
gf: "uhm, maybe if blablabla..."
Me: "boolean!"
gf: "true"
...9 -
Client tests the app and provides feedback ... This sucks! Full of bugs, hard to navigate, nothing works!
1 week later after version 2 client provides new feedback: This rocks! Love it. Easy to use and rock solid!
Changes made: background set to light blue.10 -
Just taking the temperature - how many people would be interested in a devRant podcast? We'd probably start with it being every other week.
It would feature things like inside devRant updates, guest interviews, rant readings, and anything else fun we could think of.
Any thoughts?60 -
Some guy my girlfriend knows, heard I'm a software developer. He had this 'great' idea on how he wanted to start a new revolutionary way of paying on the internet. He wanted to create a service like paypal but without having the hassle of logging in first and going through a transaction. He wanted a literal "buy now" button on every major webshop on the internet. When I asked him how he thought that would work legally and security wise, he became a bit defensive and implied that since I'm the tech guy I should work out that kind of stuff. When the software was ready, he would have clients lined up for the service and his work would start.
I politely declined this great opportunity14 -
Dev: this task is done, can I put it in review and do something else?
Me: sure, of course.
Dev: cool, just be aware I'll make some changes to it later.
Me: ... wait, then it's not done.
Dev: no it is, I just need to re-read it and make some changes.
Me: yeah, so it will be done when those changes are made.
Dev: but I don't know what those changes are.
Me: ... I get that ... but ... ok I'm extremely confused. Why do you think it's done.
Dev: because I've written everything I need to and I'm happy with it.
Me: ok so why do you want to make changes.
Dev: I don't.
Me: ... ... ... ... you ... you are really not being clear. If you don't want to make changes, and you are happy with it, why are you planning on making changes later ... after marking the task as done.
Dev: well if I re-read it and see something I don't like, I would like to change it.
Me: ok, so re-read it as many times as you like and make as many changes as you like. But don't mark it as done until it is done.
Dev: but it is done.
Me: no it's not.
Dev: it is, look.
Me: ... yeah looks ok at a quick glance.
Dev: ok so I can mark it as done?
Me: are you going to make more changes?
Dev: yes.
Me: then no.
Dev: why?
Me: BECAUSE ITS NOT DONE.
Dev: ok maybe I'm not explaining it clearly.
Me: ... we can both agree on that. Ok so to summarise, we don't mark something as done until we have stopped touching it. We don't half finish something and say it's done and comeback to it later. We mark it as done when we are happy with i.....
Dev: but I am happ.....
Me: *raises hand* I repeat, if it's done, we lock it away and stop touching it. If someone reads it and complains, we can come back to it with a new ticket. But it's not done until we think we are ready to send it on.
Dev: I am ready to send it, I just may want to change it.
Me: ... ... ... ... ... due to a new policy implemented just now, we are only allowed to send 1 email to a person each week. So unfortunately we can only send on 1 copy. So when you have that 1 copy, let me know.
Dev: ok, let me re-read it a few more times then.
Me: there you go.32