// https://mcfunley.com/choose-boring-technology
I do feel like this is a weird abstraction (why not just talk about the system rather than make up a currency of "innovation tokens" with totally subjective value? is this supposed to be universal advice or is this directed at a certain kind of application?), and I disagree with a mentality that you can "just ship" everything - I suspect that what he really means in this article is, if you work on boring things (seems like he does), choose boring tech. BUT I do think there's some good nuggets in here around decision making and the whole article is worth it for "write down exactly what it is about the current stack that makes solving the problem...difficult", which is something often overlooked.
Sent by Jesse Ditson on February 4, 2021 at 10:38 am
Jesse Ditson·44m
IMO a better framework would be "choose technologies you understand, and re-evaluate your understanding of the integration of those technologies whenever adding or removing a piece"
Sent by Jesse Ditson on February 4, 2021 at 10:39 am
Jesse Ditson·42m
Because this article already looks silly for something like node, and at this point I think a non-ACID document store with low guarantees seems pretty boring to me, in that I can't think of any useful place to put it in an interesting application