How to actually run a software project without burning out

Lucas F. Costa writes up eight rules for managing software teams, and the first one is the one everyone ignores: scope creep kills projects. You set a deadline, you set the features, and then the stakeholder adds one more thing. The team works harder, the code gets messy, and the launch gets pushed. The fix is simple — if it's not in the original scope, it's a new project. Period.

The rest of the list covers the real work: write things down so you can explain them to someone else. Build small pieces and ship them. Cut the features that don't matter. Make the hard calls early instead of delaying them. These aren't Silicon Valley ideas — they're the same rules any working team uses when they're trying to get something done without the whole crew losing their minds.

The point isn't to follow these rules religiously. It's to have something to fall back on when the project starts going off the rails and you can't tell why. Most teams skip the writing, let scope creep in through the back door, and then wonder why the thing they shipped six months late doesn't work. Costa's list is just a reminder that the boring rules are the ones that keep things from collapsing.

Why this matters for us: lots of our folks run side businesses and freelancing gigs where they're the only dev — these rules are how you keep your own projects from eating your life.