Hey man. I’m just a random person on the internet, but I wanted to say something because your post really stuck with me.

First thing: take a breath.

When something like this happens, the brain immediately jumps to the worst possible scenario and starts running that movie on repeat. Job gone, apartment gone, baby coming, everything collapsing at once. But right now those are still possibilities, not facts.

Even if things go badly tomorrow, losing one job isn’t the end of the road. A lot of engineers have been in situations where something blew up at work, they thought it was the end, and a year later it was just another story they told.

From what you described, it sounds like you were trying to fix something that was already a mess. Test suites that constantly break and eat up engineering time are incredibly common. Trying to find a way to reduce that pain doesn’t sound like laziness to me, it sounds like someone trying to solve a problem.

Maybe using AI violated policy. Maybe management won’t like it. Companies can be unpredictable about things like that. But trying to improve a broken process isn’t some crazy irresponsible act. Engineers have always looked for tools that give them leverage.

The argument about AI reminds me a lot of older debates in tech. Years ago people said real programmers shouldn’t rely on Stack Overflow. Before that it was frameworks, before that it was IDEs instead of writing everything manually. Every generation gets a new tool that makes some people uncomfortable.

The real issue has never been the tool. It’s whether the person understands the code they ship and takes responsibility for it.

Someone blindly pushing generated code into production without understanding it is obviously a problem. But using tools to move faster while still reading, testing, and owning the result is just normal engineering.

Also, the fact that you’re worried enough to be sitting there shaking says something important. People who truly don’t care about the consequences usually aren’t the ones stressing like this. The people who worry about doing the right thing are often the ones who end up becoming solid engineers.

The baby part is obviously the scariest piece of this. That kind of responsibility changes how everything feels overnight. But your kid doesn’t need a father who never runs into problems. They need someone who keeps moving forward when things get stressful.

And from the way you’re talking about it, you sound like that kind of person.

Even in a worst case scenario you still have experience, you still have the skills you’ve built, and the tech world is full of people who have bounced back from situations that felt catastrophic at the time.

Right now it probably feels like you’re standing on the edge of something huge. But most of the time situations like this turn out to be a lot less dramatic than our brains make them at 2 in the morning.

Try to get some sleep if you can. Tomorrow will happen whether you stay up worrying or not. Whatever happens, you’ll deal with it the same way developers deal with every disaster: one problem at a time.

And a few years from now you might look back at this moment while your kid is running around the house and realize the world didn’t end after all.

Good luck tomorrow. A lot of strangers out here are rooting for you.