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 👻👻👻
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (54)
When not properly tested code (poor designed tests, etc, you name it) is being merged to the master branch and the whole project breaks down a day before the demonstration for the customer.
When they ask you something complex, that takes time and effort, but they change their minds in the end, so all that hard work was for nothing, and you still need to re-do the project, but you don't want to, because your heart is crushed.
Losing interest in a project halfway due to the client's deviation from brief initially given, repeatedly. No debugging can solve this particular nightmare, I simply sigh endlessly and pray.
I've been working on a project for over a year now and I absolutely love it, I've learned so much and, not to toot my own horn, but I love what I've built so far. But right now there's a lot of tension in the company's leadership I'm building this platform for and I'm super afraid it'll just die.
A single cascading error that stops payroll.
It was you're small change that started it.
Your rent is due tomorrow.
Basically Knight Capital.
To lose the hability to learn
For me it's just stagnation. The worst thing that can happen to a Dev is they stop learning, and write the "same code" forever.
"Ok, let's make this small fixes on the stage branch, just minor things"
1 month later the branch is near a brand new product.
"Hey, you are the guy who knows the rebase thing, right?"
True story that happened to me few weeks back. Our company is a subscription based company where we charge active users periodically. I've used an un-tested feature from one of our system which causes massive reactivation of users that have already unsubscribed. This leads to severe overcharging issue of already unsubscribed users to which till now I'm still cleaning up the mess. :-(
Having to deal with customers.
More requirements and tasks being added to a feature without the deadline changing.
My #1 nightmare is the flow and speed of the JS frameworks getting released everyday. Guess what, everyone will write that as a keyword when posting a job
Accidently dropping stash
Getting a deadline on front-end features, while the data & methods are not yet implemented in the backend.
“I had a thought. Can we try something?”
— Every non-technical client who thinks code is drag and drop