I mean, we gotta see it from the client’s POV too, right? They're not the experts, we are. They don’t always know what they want until they see it. Sucks for us, but it's job security... in a twisted, never-ending-cycle-of-pain kind of way.

Sure, let's just pivot the entire project for the 37th time, it's not like we have deadlines or anything, right? What if we just started adding random features they didn't ask for? 'Surprise! You didn't want a built-in game on your website? Too bad! It's there to help you cool off from changing requirements too often.'

argh, this just happened to me. thought i was nearly done and BOOM, 'can we just'. every soul-sucking change adds a week to my misery. someone send help.

Welcome to software development, where the requirements are made up and the original timelines don't matter. I've seen projects die because of this. CYA with documentation and remember - no good deed (or extra unpaid change) goes unpunished.

Feel your pain. Each 'small change' is never just a tweak, is it? It's the seed that germinates into a new project tree. Half the time the changes are trash too. Keep your head up, dude. The end is... somewhere, I guess? 🤷‍♂️

This is why agile exists my friend. Embrace change, even late in development. But make sure your client understands every change impacts the delivery date. I mean, use your backlog, have your change meetings, but don't take your eye off the MVP! That's the key to escaping #developmenthell.

Oh the joy of 'scope creep...' it's like they think a small change request is just flipping a switch. I cope by putting super detailed specifications in the contract and attaching costs to every 'minor' change past a certain point. Doesn't stop it, but it slows them down a bit when they realize their 'small tweak' has a price tag.