(╯°□°)╯︵ ┻━┻

Software is hard to get right.

Most projects I’ve encountered are riddled with legacy, often lacking documentation, difficult to set up and modify, and held together by duct tape.

That’s the default.

And let’s be honest: Who wouldn’t prefer to work on a greenfield project using the latest frameworks and do it right?

The thing is …

Every software project starts this way. Then, the realities of business kick in: the scope creeps, people leave, the budget is tight, and corners are cut.

And you end up proposing a rewrite. Someone tells you to breathe.

So you flip the table, walk out, and calm down.

(╯°□°)╯︵ ┻━┻

And once you do, you’ll realize that the code (somehow) works and makes money.

¯_(ツ)_/¯

What is valuable is to:

• Make it easier to change.
• Make it faster to build.
• And quick to deploy.

Take out a core part and improve it. The test in front of users.

A rewrite won’t make it 10x better.

Making 1% improvements for a few years will make it 10x better.

That and constantly riding on a knife’s edge:

Are we making it better, or are we making it worse?

You’re good as long as the scale tips to better most days.

Best regards,

Taj