Sometimes the best design pattern is no design pattern

Published: August 28th 2025

Sometimes the best design pattern is no design pattern.

What do I mean by that?

When building out software, a lot of times the best way is to just get the thing working.

Get whatever the feature is, working as fast as you can, in any way possible, scrappy or not.

Don't pre-overanalyse about the best "way" or "pattern" to make it work.

Just get it working. And a lot of times the obvious patterns start to emerge on their own, as a result of the actual code needed to get the job done.

Also, you can always refactor once you have got it working. And that is actually one of the best times to make design decisions also, because you have all the actual code you need to refactor.

i.e you have more information available to make better design decisions around.