Lead Developer, business owner, US Army veteran. I build things for the web. My website is a bunch of HTML pages that didn't need a framework. Yours can be too!
I stayed up for 32 hours working continuously to meet a deadline (never ever doing that again). In the middle of trying to do all this work, as tired as can be, your logical processes are breaking down and your ability to fix the problem starts to slip away.
Luckily that employer both recognized the problem with that happening AND understood the damage it did to the codebase (Many would have blamed me instead of recognizing the real problem).
Within a week we were able to stabilize all of the bugs that were introduced and the very next task was to take a design week to pull out the good, and toss the bad (one of the most important things about writing bad code is to a) Know you're writing it, b) know why, and c) do your best to plan for the refactor). A week after that, we implemented a much more elegant solution than we had time for in the rush to go to market.
In that initial 32 hours it was all I could do to keep from saying "this is hopeless".
Just remember that 9 times out of ten, the answer is to walk away, rest your brain, maybe get some sleep and come back to it with fresh eyes. My team was invaluable. My manager was up, working just as hard on that code as I was, understood every shortcut and decision made during that time AND resisted the urge to try and take over, focusing on working on the things that I didn't have the capacity for at the time and supporting where needed).
If you feel like you're in a hopeless situation, rest and lean on the people around you to help dig out of it!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hopelessness almost always comes from overwork.
I stayed up for 32 hours working continuously to meet a deadline (never ever doing that again). In the middle of trying to do all this work, as tired as can be, your logical processes are breaking down and your ability to fix the problem starts to slip away.
Luckily that employer both recognized the problem with that happening AND understood the damage it did to the codebase (Many would have blamed me instead of recognizing the real problem).
Within a week we were able to stabilize all of the bugs that were introduced and the very next task was to take a design week to pull out the good, and toss the bad (one of the most important things about writing bad code is to a) Know you're writing it, b) know why, and c) do your best to plan for the refactor). A week after that, we implemented a much more elegant solution than we had time for in the rush to go to market.
In that initial 32 hours it was all I could do to keep from saying "this is hopeless".
Just remember that 9 times out of ten, the answer is to walk away, rest your brain, maybe get some sleep and come back to it with fresh eyes. My team was invaluable. My manager was up, working just as hard on that code as I was, understood every shortcut and decision made during that time AND resisted the urge to try and take over, focusing on working on the things that I didn't have the capacity for at the time and supporting where needed).
If you feel like you're in a hopeless situation, rest and lean on the people around you to help dig out of it!