A developer going by shiojee on DEV.to published a candid reflection this week on what they wish they'd understood when they first started learning to code, and the core insight cuts against the grain of how most tutorials sell software development. The author describes their early mindset as one that equated being a good developer with accumulating knowledge—mastering as many programming concepts, frameworks, and tools as humanly possible.

The Knowledge Hoarding Trap

That instinct isn't surprising when you consider how the industry rewards credential-chasing. Junior devs get asked about algorithms in interviews; job postings list framework requirements like grocery lists. But shiojee argues this framing sets developers up for frustration because no one can stay current on every new library release, syntax pattern, or deployment strategy. The landscape shifts too fast.

Learning Over Knowing

The pivot came when the author realized that capability isn't measured in what you already know—it's measured in your willingness to learn, experiment with unfamiliar approaches, and yes, break things along the way. Getting stuck isn't a failure state; it's a data point. The developers who advance aren't those with photographic memory for documentation; they're the ones comfortable operating without a complete map.

What This Means for Tooling Decisions

For builders choosing their stack, this has practical implications. Obsessing over whether to learn Rust or Go, whether Kubernetes is worth the overhead, or which frontend framework will "win" misses the point. The ability to evaluate tradeoffs and adapt your tooling as requirements evolve matters more than picking the currently-trending solution. Your knowledge base becomes obsolete; your learning velocity doesn't.

Key Takeaways

  • Stop optimizing for what you know; optimize for how quickly you can learn what you don't
  • Treat getting stuck as diagnostic information, not a personal failing
  • Experiment deliberately—build things specifically to break them and see why
  • Framework fatigue is real; focus on transferable patterns over syntax

The Bottom Line

The industry keeps selling the lie that you need to know everything before you're qualified—but that's a trap. The developers who actually ship are the ones comfortable googling in the dark, breaking things on purpose, and admitting when they're wrong. Pick your battles, build things that teach you what you don't yet understand, and stop treating confusion as a character flaw.