https://mstdn.social/@mpv/110823276099826322

I'd say even "easy to change" is kind of a bet.
I more and more give zero shit about patterns, and I truly believe what actually matters is:
- good tests coverage, with *relevant* tests (help yourself with mutation testing), best with more integration and less unit
- shared contracts between providers and consumers (note: strong typing is exactly that at functions level)

The rest is "implementation details", it matters, but it won't have such impact on long term.

Mike Vosseller (@[email protected])

Don’t design your code anticipating future needs. Design it to be as simple and easy to change as possible because you can’t predict the future.

Mastodon 🐘