Post

The belief around bad software architecture and tech stack choices is that you can address them down the road when you're profitable, but the reality is that it just doesn't happen.

If scrimping over costs is the way you start the thing, that's not going to change once money starts coming in - it's part of the DNA of your product and your team.

If the commonly held belief about "fixing it later" were true, we wouldn't have disastrously poor user experiences like Slack, Teams and other Electron-based wrappers. Those companies are profitable enough to do the work, so the assumption is that the business just doesn't want to.

Still, it's wild that teams keep making these choices. I don't hold the business accountable for that - but it does raise questions in my mind about how good some of the developers starting these projects actually are at their jobs. There's a lot of unchecked hype.