Let's share some of the worst-case scenarios and nightmare-inducing horrors in the work of the devs.
My #1 nightmare is cleaning up lengthy, real complex, unreadable, critically ridden code with bugs left behind by the previous developer π»π»π»
Oldest comments (54)
When the requirements change and you have to start all over again
That's a widespread situation in an agile environment. Too few customers are ready to employ waterfall approach (writing a full technical description, before starting the coding part).
"can't you just. . ." coming from the mouth of a non-technical senior person being "helpful". Possibly goes with some vague hand-waving. π±
On the more technical side, tricksy multi-thread concurrency bugs. Bonus points if it relies on a big service framework even to try to reproduce the problem.
Working really hard on something that is then never used by nobody or even scrapped and forgotten into oblivion
I learned a long time ago that you need to separate the code that you write from your sense of professional self-worth. Write better code than you did yesterday and try to better someone's workflow but the app is the company's (not yours).
It took a major toilet manufacturer canning a Spanish-language HR app that I worked month on to learn that lesson.
Joe,
Never thought of it that way. I know it seems pretty obvious, but "do today better than yesterday but the app is the company's" should bring us some relief...
I mean, if everybody thought of it that way, we would have so much people on the brink of war because of self-pride... :P
Ah hate when that happens. Once I was working on a new feature and then the CEO who's mind changes like the weather decided that he did not want it anymore...
When a critical bug occurs during the demo π
Anyone else pre-record demos to combat this?
Editing a production database that doesn't have a backup, and ruining the production data in an irreversible way.
Having to make changes to code that was written by someone who did not know what they were doing.π΅
Working on any project which requires cross-team collaboration. There's always last minute surprises and a lot of headache when you're someone tells you over lunch they want you to push out a change before the end of the day.
Working hard to produce clean, scalable and readable code, to see it declining in a matter of days when another dev is in charge on the project.
Tasks non well documented.
Tasks very well documented... 10 years ago
Oh since nobody has mentioned yet, deployment on Friday
Second that. Don't do it, just don't...