|
|
|
|
|
|
by lukecameron
2144 days ago
|
|
|
Has anyone heard of good resources that teach you "when to use X" instead of "why you should use X"? It's somewhat understandable that the official websites of frameworks/tools/libraries/languages/services tend towards espousing the advantages of the thing and leaving out most of the drawbacks. That's just how the incentives are aligned. But even the average blog article about a tool posted on HN rarely talks about what situations it is most effective, and what situations it should potentially be avoided. I suppose it's a natural consequence of blog authors only knowing so many tools, no single person knows them all. I'm not saying this information isn't out there – just that it seems like the exception rather than the rule. |
|
|
One of the goals of a podcast I started last year was to answer that type of question and more.
It's mainly a podcast where I talk to someone new every week to get a better understanding of why they chose a specific tech stack to build their app but it also goes into the "how" since we talk about how they build and deploy their app, lessons learned along the way, etc..
A list of episodes can be found here: https://runninginproduction.com/podcast/
Each episode has a "Motivation for using ..." time stamp so you can jump to that part of the discussion. It's usually within the first 5 or 10 minutes.
The goal here is to have a bunch of real world examples of why and when someone used X and they usually spend a few minutes talking about why they chose that instead of something else too. There's episodes ranging from solo developers working on a side project to high traffic services handling billions of requests per month.
The idea is to have loads of practical examples instead of trying to theory craft hypothetical scenarios.