Personal

Code, Diapers, and Deadlines

3 min read
Software EngineeringPersonalCareerMental HealthFatherhoodEngineering Life

August 2024 changed our house.

I became a father, then learned how different work feels when sleep disappears. Midnight feeds do not care about standups. A crying baby does not care that you need to review code in the morning. I loved being a dad from the start, but the first year pulled more from me than I expected.

Work got rough at the same time. Deadlines tightened. Teammates burned out. Planning fell apart. One teammate left in the middle of the project, and the codebase became my problem to understand.

I thought I was getting ownership. I found a legacy system that needed more patience than confidence.

Every feature exposed another workaround. Staging and production behaved like two different products. The partner specs were unclear. QA could not test in the way they needed. I would fix one issue, then uncover another one hiding behind it.

The project management side did not help. One PM left. The replacement pushed for delivery while still learning the project. Partners answered slowly. Upper management heard that our team was slipping, while the blockers sat in API mismatches, missing access, and technical debt that had been ignored for too long.

I became the bottleneck people could name.

That hurt because I had spent years being the person who could push through. I used to trust my ability to ship under pressure. During that period, I opened my laptop and felt my mind stall before the editor even loaded.

At home, my daughter needed me. My wife needed support too. She was also learning a new version of life, with less sleep and more responsibility. I wanted to be useful at work and gentle at home, but many days I felt like I was late to both.

My wife kept me from falling apart. She listened when I repeated the same worries at night. She reminded me to rest. She handled more than I deserved during weeks when my head stayed stuck inside work.

I still remember mornings with cold coffee beside the laptop. I would stare at the screen and ask myself whether I could become my old self again. The answer did not come fast.

That year taught me that performance is not separate from life. A tired parent writes code with a tired brain. A stressed engineer brings that stress home if he does not learn how to name it. I did not need a heroic version of myself. I needed help, sleep, and a clearer boundary between work pressure and family time.

I am still ambitious. I still want to build good systems, learn hard things, and work with people who care about quality. I also know now that ambition without rest turns into resentment.

So I am looking at the next chapter with a different standard. I want work that challenges me without consuming the parts of me my family needs. I want a team that can talk about risk before it becomes a crisis. I want to keep growing as an engineer and as a father.

Some seasons rebuild you in plain, uncomfortable ways. My first year as a developer dad did that. I came out less interested in looking unbreakable, and more interested in staying honest enough to keep going.

Share:
Loading reactions...

Loading comments...