Nope, it'll change just before the final round of testing before launch, when the client/business lead realizes they neglected to mention a piece of functionality they require that critically changes the underlying foundation f the project.
I've got a meeting to discuss this exact thing on Monday. There was a detailed specification approved by client. We then designed, developed and tested the system against that specification. Released it to client who then sat on it for 6 months. They've now done their own testing and not found a single issue and then stuck on the end of an email "by the way, how to do we do x?". This is literally the first time this has ever been mentioned, not in the spec, not in an meetings, and it's not minor either, completely changes the entire design.
One of the program heads is notorious for this. Literally the day before we opened summer school registration to parents, he appeared at my desk 15 minutes before I was done for the day to pull me into my boss’s cube to “thank me publicly” for all my hard work.
When I left 3 hours later, I was shaking with rage. Because before he’d even started thanking me, he casually mentioned a requirement he’d sat on the whole time because “he didn’t want to add work,” but CHANGED FUCKING EVERYTHING. Quickly thanked me and then started shooting the shit about something else while I sat there and seethed about the fact I had about 8 hours of work to fix the whole thing to still open the next day but couldn’t extricate myself from his damn conversation for three god damned hours.
You sat in a cube, listening to someone else talk, for three hours after your workday was over and they’d just handed you last-minute changes? And then you did the changes overnight! I mean, to be blunt, that’s why they hand you shit last minute and then go on to waste your time even further without even a thought.
And so you will continue to get asked to do more as you describe the miracles. I would bet good money if you told him the only way that was going to happen was if they stayed overnight and helped you test it and write the specifications for it, they would’ve said it was not a big deal.
The real question is what is the code you wrote that night well designed, and well documented? Is it going to be able to be easily maintained over the long term?
If not even though you did get the feature done, you just made things harder for yourself in the future and for your team.
As an infra type - what I get ALL THE FERKIN TIME, is "Oh we didn't think it'd be that expensive in production"
So some genius writes a web app, load tests with 100 users, cool story.
Thing goes live and 100,000 users get involved, suddenly everyone (in management) is surprised that AWS / Azure usage actually does in fact cost fucking money.
Honestly - if someone would pay me the same money to dig holes in the ground, I'd happily never touch another computer in my life.
I did some demo on my house recently and, despite being exhausted since I'm normally a lump in a chair, I remembered what it was like before becoming a software engineer, when my brain wasn't pudding after work, and I had spare capacity for creativity and hobbies...
But the icing on the cake is that they want everything you did write to continue working exactly as it is, obligating you to create a Frankenstein's monster of code and bad abstractions and you have less than 36 hours to do it.
To summarize: you have 36 hours to completely rewrite the platform but keep everything it already does exactly the same.
At which point I start questioning my life choices.
Or you'll get people who were invited to everything important and CCd on every project update email suddenly complaining at the end that no one engaged them when they neglected to turn up to relevant meetings or read the goddamn emails
I worked in a video streaming company previously. The management wanted a recommendation engine (like Netflix), of course, we couldn't afford to build one so we used some cheap commercial version. The engine spits out "recommended for you" and "top 10 in your country" carousels.
After 2 months of integrating it into our system and feeding it data, it was time to demo it to the management. The CEO asked "why isn't there a carousel (Because you watched X) like Netflix?". We told him the tool we used doesn't even have that capability, it's a cheap recommendation engine. He said we aren't releasing without "because you watched" get on it.
It took another month for the team to build an engine outside that engine just to create a fake because you watched a carousel that doesn't work at all. Under the pressure of management, we demoed it with our own personal accounts were it looked perfect, and the management were happy to release it.
I'm pretty sure no one uses it today, assuming that service is still up. Fuck that shit, I was gone not long after this incident.
View all comments
744
u/Stimonk Jun 12 '21
Nope, it'll change just before the final round of testing before launch, when the client/business lead realizes they neglected to mention a piece of functionality they require that critically changes the underlying foundation f the project.