15

So before the Age of JavaScript, when programming was trying to be an engineering discipline, I felt like we were getting close to figuring out what worked and what didn't. We had rules of thumb (more general than Patterns) and code smells.
Then JavaScript came in and no one had time to think about "engineering" anymore. I'm fine with MVP and small iterations, but the disdain I see for making code clean and extendable and improvable is baffling (and annoying). First-time coders might never have had to fix someone else's code, but two weeks in a chair should have fixed that.
It's not that understanding code is so hard (although it can be); understanding the _intent_ is hard. This MVP is great, but when no one had time to document what is actually supposed to happen, programmers have to reverse-engineer the *design*.

Comments
  • 3
    MVP just means it doesn't have all features and some parts are just mocks, not that it's spaghetti code... Code quality and documentation are imho very important part of MVP.
  • 1
    This sounds like an i hate javascript post more than anything considering the DRY principal abd writing clean neat code is all taught now. Hire better developers
  • 1
    @BirdLawExpert it's not the developers. It's the lack of information (documentation?) about how the system is supposed to work on a product, UI, API, and data storage level.
    Without that, each level had to guess in order to fix or enhance (let alone migrate). And they still won't know the assumptions made on the other levels
  • 0
    @Marqin If you can enforce that where your work, I envy you
Add Comment