5 ms·
If you believe that's all there is to those ideas, maybe you need to step away and think about them for a while. Sure, there's going to be some resume padding h
by viraptor 5y ago
If you believe that's all there is to those ideas, maybe you need to step away and think about them for a while. Sure, there's going to be some resume padding happening in larger orgs. But all those ideas solve real problems too.
I think you're just in a very negative space if you start with "Distributed systems" as something overly complicated. At some scale getting a bigger machine either doesn't make financial sense or is just not possible to implement efficiently. Some ideas are taken too far or implemented where not needed. But I'd rather recommend you to learn where each one of them started and why. Criticize for valid reasons, but don't become a curmudgeon.
- kasey_junk 5y agoWhat’s crazy is the scale a modern computer can operate at. There _are_ problems that need more scale than that but they are the minority. Meanwhile it’s out of fashion to spend time improving application performance and instead people go horizontal early, with devastating complexity issues.
- viraptor 5y agoThat's why I mentioned "doesn't make financial sense" too. If you can throw another $X/mth box at it, or have engineers spend weeks improving the system's performance for the same effect... there's a point where scaling out makes way more sense. Whether that leads to complexity issues is really case-by-case.
- phkahler 5y ago>> If you believe that's all there is to those ideas, maybe you need to step away and think about them for a while. Sure, there's going to be some resume padding happening in larger orgs. But all those ideas solve real problems too. They do solve real problems. The question is whether or not they solve the problem at hand, and if they create other issues in doing so. I was re-decking a back yard bridge with a friend and he brought a framing hammer. I'd never used one before and I always had a finishing hammer and didn't know the difference. I learned a new tool and even ran out and bought my own for the project, which worked fantastically well. It's still in my toolbox and hasn't been used since. You just don't use that thing to hang pictures on the wall because it may well f-- up the wall a bit. Using the right tool for a job is way more important than using a particular tool for any other reason.
- gfodor 5y agoI’ve never liked this best-tool-for-the-job mental model with software engineering. A given project has multiple needs, and unlike more physical tools there is a very high marginal cost for each incremental tool you use. So there is a huge balance between many well suited tools or a few but more generalized, less fit tools. This isn’t to say there’s an obvious place where to strike the balance, but the “best tool for the job” metaphor undermines recognizing it, and I’ve found this balance to be at the core of good tool picking for a given project.
- xpe 5y agoThank you for calling out BTftJ as a mental model. Recognizing the very idea of mental models is a huge step forward. Arguably, it could be used as a metric for how advanced an organization (or even society) has become.
- phkahler 5y agoI agree with you. But dont add a new tool (even a more general one) unless it fills a gap, or has other specific benefits.
- xpe 5y agoI also dislike the BTftJ (best tool for the job) cliche. Best according to who? Based on what priorities? Relative to what other options? Based on what kind of experience and expertise with the various options? My takeaway: BTftJ must only be a starting point for dialog and discussion. Shortly therafter, it is time to get real about each of our experience and biases. Otherwise, BTftJ is a only a thin veneer.
- phkahler 5y ago>> I’ve never liked this best-tool-for-the-job mental model with software engineering. I don't either. As photographers say, the best camera is the one you have with you. Same thing, the best tool for the software job is the one you already have and everyone knows how to use. Why anyone would want to introduce these high-end fads to an organization without proper reasoning is beyond me.
- philipov 5y ago> But all those ideas solve real problems too. All of them, except for blockchain. That one can go die on the trash heap of history.
- antris 5y agoWell, it's a good tool for money laundering and purchasing drugs.
- commandlinefan 5y agoThat's not fair, it makes a great Ponzi scheme, too.
- deleted 5y ago[deleted]
- ryanjkirk 5y agoIt's not.
- thebean11 5y agoHow many "darknet markets" accept anything else these days? What's the alternative, cash in the mail? Venmo?
- xpe 5y agoKeeping a permanent log for one's illegal activities seems... suboptimal.
- rvz 5y ago> That one can go die on the trash heap of history. As long as there are Rust jobs or blockchain related jobs there, you're going to have to cope and wait for a very very long time until that is ever going to 'die on the trash heap of history' to happen.
- dimgl 5y ago
- arinlen 5y ago> At some scale getting a bigger machine either doesn't make financial sense or is just not possible to implement efficiently. You don't even need to get scaling into the picture. You do not get any form of fault tolerance by deploying stuff in a single lonely box. If you care about reliability and resilience, you have to have multiple deployments up and running at the same time. Also, you already have a distributed system if you have a browser calling your server. And lastly, if you happen to manage an service used globally or regionally and perceived performance matters then you have no good alternative to have regional deployments.