A lot of coding decisions come down to that elusive idea, judgement. Think about what the pros and cons are, what the scope is, budget, and... decide what to d

A lot of coding decisions come down to that elusive idea, judgement. Think about what the pros and cons are, what the scope is, budget, and... decide what to do. I've never come across one of these articles that doesn't boil down to "think about it". That's not to trivialize it, because of course it can take years to hone your development judgement powers, but essentially such articles are only useful so far as they tend to contain a long-form list of commonly encountered thinking points. More specific experience gives you more detailed items on your list. Level 0 of the performance considerations (relevant to every vertical) is maybe whether you can just throw more hardware at it. In my little vertical (finance) you might think about what data structure to use based on what instrument type you're building a system for.