3 ms·
The title of this article, which makes rounds on HN, bothers me. It's not about choosing a "boring" tech. It's about choosing tools you understand well and a m
by nine_k 6y ago
The title of this article, which makes rounds on HN, bothers me.
It's not about choosing a "boring" tech. It's about choosing tools you understand well and a master of.
You can be totally excited about e.g. TypeScript or Elixir, but as long as you have a solid experience of working with them, and a good understanding of their internals, they are safe bets.
Choosing a perfectly boring thing like Cobol is not going to help if you have no solid mainframe experience.
- jonahx 6y agoFrom the article: > I chose “boring technology” as the pithy SEO-friendly title for this content, and I regret it most days. It’s kind of distracting. “Boring sounds bad, why is he saying it’s good?” Et cetera. It’s a real shitshow. > But what I’m aiming for there is not technology that’s “boring” the way CSPAN is boring. I mean that it’s boring in the sense that it’s well understood. It’s bad, but you know why it’s bad. You can list all of the main ways it will let you down. > It’s important to master the tools that you do pick.