Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
A 'senior' dev just questioned us (by question, I mean scold) when I suggest writing some additional information regarding db patching scheme of our project on our Wiki, just thought it might be useful for other possibly new devs later.
Apparently that would be 'spoon- feeding' them and it is totally NOT GOOD.
Pending issues : 5. Deadline is nearing.
Tweaking around, I found some bugs on functionalities that for some reasons have magically passed QA. The bug was quite simple to be found.
Created 5 issues for 5 different bugs. Pending issues is now 10.
Manager : I am not happy. Last week we have 6 and we're going to weekend this week at 10?? Wtf you guys have been doing?? Why isn't there any progress?? Are you guys not doing any work?? You guys been lazy??!
Yeah, we been here sitting around play computer games all day.
Working on API part of current project, we were prepared with the API specs. The application that we are writing is supposed to replace the old and expensive on-the-shelf application that they bought licenses from overseas vendor years ago. In short, we writes an application that provides same functionalities at cheaper price for our client.
After it is all done, the client mentioned some of the API calls return wrong/incorrect response.
Furios, went to check the specific API call and confirmed that there's nothing wrong with it - all according to specs.
It turned out that the client didn't check against the specs, but with their current application instead.
That application didn't meet the specs they provide 100% (not broken functionalities but rather it was full with bugs here and there) and apparently the client have gotten used to it.
Now, we are writing our application to provide the same buggy API responses.... because the client doesn't want to introduce change to their clients.
I am writing to provide an empty json array instead of actual data....wtf
I had fever for 2 days and finally after resolving my assigned issues/tickets yesterday, I called my PM for a MC today - my fever is still quite bad.
My name was still called a few time in group chats asking for updates, by the same PM, as if I am working from home.
We're 2 months away from going live.
This has repeated for several weeks now :
Monday : 17 issues (aka bugs, incomplete features)
Work work work.
Friday : 7 issues
Nice. Lets get a good weekend rest and finished this next week.
Next Monday : 17 issues.
QA found some new bugs or some already resolved issues came back with different details.
...and repeat. Exact numbers, plusminus 1 or 2.7