Choose Boring Technology
Link: https://boringtechnology.club/
Discussion: https://news.ycombinator.com/item?id=37731798
-
@hn50
complaint:
>This article gets posted a lot, but I find it a little unsatisfying. I think it’s because it’s pretty vague about what “boring” means exactly, so it’s the kind of statement most can agree with, without it actually being a very strong statement.
I'd state it this way: choose known problems over unknown problems.
What's known depends on you and your organization and your anticipated organization (i.e., the job pool, language popularity), but this is an easy rule to apply. Your current set of problems have to be *very* big for it to be worth trading them for problems that you're not even aware of yet.
-
@hn50
>If you behave that way you miss out on the part of the curve that we call “mastery.” That’s a state to the right on this curve, where there are still problems. Everything still sucks but it feels manageable.
woah, it's 2023. It's called "mainery" now.
>The grim paradox of this law of software is that you should probably be using the tool that you hate the most. You hate it because you know the most about it.