3 ms·
This article reminds me of the adage about ops people which goes, "You know you're doing a great job in operations when nobody thinks you do anything." The pro
by ChuckMcM 8y ago
This article reminds me of the adage about ops people which goes, "You know you're doing a great job in operations when nobody thinks you do anything."
The problem with taking the experience that "future proofing" is never worth it, is that it suffers from survival bias, which is to say that when you did it and it made the future event a non-event, it didn't even register on your brain. If you practice more mindful engineering you can teach yourself to recognize the things you did in the past that made what you are doing today easy or even possible.
That is not to say that all future proofing is good, especially if it ties up the group in knots trying to predict all possible futures. That is where the mantra of keeping it simple really helps. Simplicity is the greatest protection against the future precisely because it has the smallest disruption surface. The simpler a process or product is, the more difficult it is to find a change that would invalidate its effectiveness.
- suzzer99 8y agohttps://www.quora.com/What-are-the-growth-stages-of-a-programmer/answer/Andreas-Blixt https://www.quora.com/What-are-the-growth-stages-of-a-progra... Second phase of a developer: 2. The philosophizing abstracter "This code works for now, but if I move this part into a factory, and create an interface for these methods, it'll also support all these future cases I can think of!" They've read all the articles on how to structure code. There's a lot of patterns out there for object-oriented (or functional!) code. Their code has all sorts of useful interfaces, abstraction layers, factories, extension methods, data structures. Things break down when the project needs to move in an unexpected direction and it turns out that implementing the change requires changing a lot of the codebase because there were a bit too many abstractions that ended up creating hidden dependencies across the code.
- josephg 8y agoYep. Some of my favourite programming advice is that the easiest code to change is code you haven’t written yet. In other words short, straightforward code is always the easiest code to adapt to new requirements.
- sitkack 8y agoSimple systems are easy in nearly every dimension (extension, debugging, performance), and they are at natural odds with the state of affairs. There are hoards of programmers waiting to do a tech debt driveby to "look good" for having bolted a feature on in minutes to days. Simple systems require extreme vigilance to remain simple.
- bunderbunder 8y agoSo, to me, "future proofing" has some very specific connotations. It doesn't mean building for eventualities that you know will happen and already know how to build for (though, if it takes extra time to do so, you do need to be mindful of the cost of delay), and it doesn't mean things like writing well factored and loosely coupled code (within reason) so that you get a system that's generally easier to modify. It means going out of your way to try and handle scenarios that you don't know will occur, or whose details you don't really understand yet, with clever one-off facilities. E.g., I've come into a couple projects now, where I'm supposed to add in some new feature, and I discover that the original author has thoughtfully added a bunch of extension points to try and help me with that. Both times, I also discovered that building in those extension points accounted for a large amount of the pre-existing complexity in the code, even though they weren't actually being used for anything yet. And both times I also found that none of them actually addressed my needs, so all that extra effort and complexity was a waste. One time I was unfortunate in that the existing code was of the "600 line functions and a whole mess of mutable state and temporal coupling" variety, so changing it would have incurred excessive risk, and I opted for just jamming my square peg into that round hole. The second time it was well-factored code, so it was easy enough to rip the round holes out to make room for square ones. But it would have been even less effort if I could have skipped that cleanup step and just jumped straight to adding the extension points.
- Zanni 8y agoExactly. When people talk about "future proofing," they're imagining the future as a predictable, linear progression--which it definitely isn't. The people best equipped to deal with the complications of the future are those who have direct experience with it ... in the future.