Programming

17443 readers

169 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Feeling stuck on a never-ending software project (programming.dev)

submitted 8 months ago by yournameplease@programming.dev to c/programming@programming.dev

32 comments fedilink hide all child comments

Scene: Surprise meeting with the project owner 0-3 days before the go-live date

"Hey team, the business and I have decided to postpone the project release by n=1-3 months because [they aren't ready for it / it isn't finished /regulatory reasons]. And since we have some extra time now, we can tie up all the loose ends on this project (i.e., 'we've added n+1 months worth of backlog items to the MVP')."

I'm still a greenish dev, so maybe this is normal, but I've had the same story going on for over a year now, and it's really starting to burn me out. In the beginning, I was optimistic. Now I just hope for the project to fail, or me to get off somehow, but this thing just won't die.

Anyone with experience on similar projects able to share words of advice? Do they ever end up working out? Seems there's a death spiral, since we are always rushing to a deadline, forgoing tests and quality but never cleaning up our mess because we're already behind. Yet I somehow feel like I'm the crazy one for thinking this 6-month "quick" side project turned 2+ year half-rewrite will have trouble meeting it's Nth deadline.

you are viewing a single comment's thread
view the rest of the comments

[–] wiLD0@lemmy.world 10 points 8 months ago* (last edited 8 months ago) (1 children)

Look for another job.

Companies like that are very unlikely to change their view that engineering’s quality and sustainability practices are a perpetual waste of money.

That, and product doesn’t know what they’re doing, and they’re okay with making engineering also suffer for it.

Nor do they care in practice about the engineers getting burned out.

After you leave, when you glance back at the company at any time for the next 5+ years, you will see that they have learned pretty much nothing.

I’ve been burned out once, and I’ll never let it happen to me again, or anyone I work with. It’s like depression; it’s an indescribable experience.

Here’s one self-test to measure how burned out you are: https://www.peoplestorming.com/burnout-assessment.

[–] yournameplease@programming.dev 5 points 8 months ago

High on all fronts on that test, which does not surprise me. Though what you describe sounds worse than what I have. I'm just generally tired and pissed off, despite thinking myself a normally happy guy.

I'll take this as my nudge to put my casual job search into overdrive.