I picked frameworks to look different, it took me years to notice
I write about programming at invasikode.com , and I have been writing code since high school. My day job now is mostly backend and AI plumbing, which is a strange place to arrive at for someone who spent years caring a lot about front end frameworks. This post is about those years. The first thing I built that strangers actually used was a school election system, written in Pascal with Lazarus…
The author recounts their journey through various web development frameworks over the years, driven primarily by the desire to stand out from their peers rather than technical necessity. They started with Angular, then moved on to React, Vue, Nuxt, and CSS frameworks like SASS, CSS, and Bootstrap, always choosing the option that felt different from the group.
They explain that this habit developed early in their career, when they had limited real-world experience and found that adopting a specific stack provided a sense of belonging and accomplishment. The author acknowledges that this approach led to several downsides, including shallow knowledge of each tool, frustration from others who had to work around their choices, and a tendency to judge others' decisions based on their own past preferences.
They eventually settled on a more versatile, vanilla frontend stack, but still consider Vue and Nuxt to be the most valuable tools in their toolkit. The author emphasizes that while it's acceptable to choose an unusual framework, it's crucial to have a clear, well-articulated reason for the decision and to be able to defend it openly.
They conclude by stating that their current, unassuming stack works well for them and that they regret none of the unconventional paths they've taken.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
