3 ms·
This is long, and it's a lot to digest, but I find it pretty applicable to software systems. And it's funny how often we see software teams twiddling at the ed
by rpeden 8y ago
This is long, and it's a lot to digest, but I find it pretty applicable to software systems.
And it's funny how often we see software teams twiddling at the edges of a system, spending a ton of time on things than don't meaningfully impact the system's overall success. To give a concrete example, I've seen teams with crappy, slow, and unnecessarily expensive system architectures spend a huge amount of time on decisions like "should we use Vue, or React?".
Granted, there will be occasional times when your front-end framework is a make-or-break leverage point. But usually it's not. Maybe the problem is that the teams who are doing this yak shaving aren't authorized to alter the overall system. And so they spend their time arguing about the things they can change. :)
- agumonkey 8y agoyeah that is exactly the kind of thinking that I found missing in both college and the few jobs I had. There was very few deep/hard thinking about systems. A frightening amount of tinkering and superstition.. and endless meetings.