|
|
|
|
|
|
by parasubvert
1558 days ago
|
|
|
I don’t think the assumptions are hidden. There is plenty of literature with a reasonable discussion of the range of definitions of performance and scale. It’s that people aren’t even looking for them. It’s about “Team Red vs Team Blue”. Or whatever buzzword needs to be on your resume alongside leetcode for the next interview. NoSQL vs SQL, FP vs OOP. Can’t get my raise if I’m building coffee shop solutions! The counter to TMTOWTDI is a set of principles and discipline, at least within a team or a project. Not to outright reject the alternatives, but to recognize the power of consistent behaviour and prioritization of tradeoffs, to try to counter the brand allegiances. |
|
|
And yet in the very article we're talking about, there's no explanation of what assumptions the author is operating within.
I'll even go so far to say that most technical articles omit the assumptions - because it's boring content and is less likely to engage the readers.