3 ms·
I spend an awful lot of time and energy investigating new complexities in order to have good arguments why we should not use them. Economically, I think this ap
by dsr_ 4y ago
I spend an awful lot of time and energy investigating new complexities in order to have good arguments why we should not use them. Economically, I think this approach has been very successful. Psychologically, it's rather wearying to repeatedly answer questions from non-technical folks with variants on "that solves a problem we don't have" or "that would cost much more than what we do right now".
- yamtaddle 4y ago> Psychologically, it's rather wearying to repeatedly answer questions from non-technical folks with variants on "that solves a problem we don't have" or "that would cost much more than what we do right now". Even worse is when there's a technical person with more pull than you who's built an identity around being "an X professional", where X is some overhyped-and-unimpressive-for-general-use thing. You end up feeling like fucking Cassandra: able to perfectly predict the future, but everyone who matters ignores you.
- uoaei 4y agoI think the commenter above was talking about complexity in the backend ("serverless" architectures, all the data brokerage siphons, leading to 10s to 100s of requests per click at times) as much as the frontend (new noisy notifications, plethora of "tools" that don't add much value).
- trasz 4y agoIt’s not just the backend. Loot how many lines of code we need for Chrome, which is essentially a remote graphical terminal.