Thread by @Aaronontheweb

Playing with some ideas for this "ways in which software developers destroy value" blog post.

- Destroying optionality
- Frameworkism
- Domain omniscience
- Infrastructure coupling

https://twitter.com/Aaronontheweb/status/1405845587019407360

Difficult idea to express because many of these weaknesses are strengths taken to an extreme.

i.e. Frameworkism, building frameworks for building apps rather than just building apps, occurs when DRY gets taken to an extreme and the developer misses the point.

In other cases though, it's failure on the part of the developer to anticipate future changes to the project when they're inexpensive to implement, i.e. building an event-sourcing abstraction when you don't have customer data to preserve, which becomes a giant project later

I also want do a section on how many developers are somehow, simultaneously terrible at gauging opportunity costs but even worse at estimating real costs.

The adage "developers will spend months coding in order to avoid hours of planning" exists for a reason.

There's a bell curve to these types of behaviors and both ends of the spectrum are bad - copying and pasting the same method everywhere vs. frameworkism. The middle of the distribution should be pragmatic, contextual decision-making - but why does that not occur sometimes?

And how do you know when it's not occurring? And what should we do about it? That's what I want to write about.