Foundations · 5 min

Why learn patterns

Three real reasons, and none of them is "to pass the interview".

1. You read code faster

Nuxt middleware, Vue's reactive(), axios interceptors, Redux reducers, Vite plugins — all of these are patterns the library authors already picked. Know the name and you can guess what the docs don't say: who calls whom, whether you can unregister, what order things run in.

Without the name, you read useFetch() like you're reading magic.

2. You make design decisions faster

Most architecture bugs aren't "wrong code" but "logic put in the wrong place". Patterns are a catalog of proven options: when you smell a 6-branch if/else tree, it takes you 5 seconds instead of 2 days to know what to do.

3. You communicate more precisely

"Let's switch to a state machine with a transition table, to block invalid state changes" is a very different sentence from "let's refactor this a bit". The first one can be estimated, reviewed, and followed by someone else.

The real cost

Patterns add classes, add indirection, and make code "less direct". If you're writing a script you'll run once and throw away, that cost isn't worth it. Learn patterns to recognize when the cost is worth paying, not to pay it everywhere.