Hacker News Reader

Comment by dylan604 | Hacker News Reader

Especially in startups clawing there way to MVP release and increasing users/income. Everything is write code to solve specific need now without time to see if it can be better used/implemented. Gotta be first. If we're not first, gotta get traction to overtake first.

Even knowing that and attempting to build something with best principles is still going to be a pain to maintain as it's always a moving target with no proper specs.

View on HN

There's best principles and then there's over engineering. Business domains can't be properly abstracted when the business itself is in the process of being defined, so if you're the kind of software dev that craves building to a spec that won't ever change, one possibility is that a fast-moving 12-person startup just might not be your cup of tea. Nothing wrong with that, just different.

And if you are the type that does well with band-aid code strung together with duct tape and bailing wire and even bubble gum, then don't get upset when your company gets bought and the entire code base gets rewritten into something that teams can manage

I'm not entirely sure why people who "sling code" would object to their code being completely rewritten -- particularly when the startup mindset is "we'll get something working right now, and once we figure out what we're doing, we can rewrite everything into something stable."

And those who don't want to participate in the "stabilization" effort typically move on to find the next shiny and exciting thing to work on.

Reply on news.ycombinator.com