3 ms·
Software engineering evolves to get the most out of your hardware. If you sort of turn that idea around in your head, software will always end up trying to bar
by m463 7y ago
Software engineering evolves to get the most out of your hardware.
If you sort of turn that idea around in your head, software will always end up trying to barely work on the shittiest hardware.
Think about it. Chips work on 30 nm. What's our next step, to make 30 nm more solid and reliable? No, it's to go to 20 nm or 10 nm and get the same software to work.
The same goes with systems stuff. Do we work on having much more reliable cpus? No, we work on using lots more less-reliable cpus (or gpus) with more unreliable storage over less reliable interconnects and networks and get the software to (imperfectly) abstract away the problems.
- hinkley 7y agoI've heard it said that the reason bits of the Roman aqueducts are still standing is that they were overbuilt by at least a factor of 2. The craftsman often wants to overbuild something. It's part of what gets them out of bed in the morning, or lets them sleep at night. What if you - or someone else - got your margin of error wrong, like the Citibank building? A little extra to deal with unexpected situations isn't so bad.
- jupp0r 7y agoIf you compare the aqueducts to software, you might draw the completely wrong conclusions. Software that was extremely well built in the 70s is mostly gone (or if it's still there, it's not exactly admired by todays software craftsmen (looking at you, airline ticket booking systems)). What makes software endure over time is its ability to react to changes of wildly different varieties (market shifts, changing hardware, new technology, ...). The Linux kernel might still be popular in 30 years, but it will likely look very different from today. If it looks the same in the way the aqueducts do, it won't be relevant anymore and will most likely be forgotten eventually.
- m463 7y ago> gets them out of bed in the morning I always thought you should do it as best as you could too. It took a bunch of time in the real world before I could actually grasp the concept of over-engineering in a meaningful way. The first example of over-engineering I could "get" was when someone (jwz?) ranted about over-engineered high-end audio. The deeper you look, having $1000 00-gauge cables just won't make anything sound better. It's marketing. The second example was japanese motorcycles. I started realizing that there was an envelope. If you made something bigger and stronger, the weight would go up and the acceleration would get worse. If you made it all motor, acceleration would go up, but handling would get worse. Some of the fastest bikes were actually lighter less powerful bikes that could still accelerate, but also go through turns. as an example, before the s1000rr era, BMW made big strong durable motorcycles... that weighed a lot and handled in a very mediocre fashion. (as to safety - yes, bringing safety or security into the equation ... you change the equation)
- hoseja 7y agoBut it won't look as good on the quarterly report. What profit has the managerial class extracted from the aqueduct?
- hinkley 7y agoWhat have the Romans done for us? Someone, and I wish I recall who or even where, once sold me on the notion that Roman expansion was empowered by the same kind of 'replaceable parts' strategy that powered the ascention of the United States. According to this person, everywhere the Romans went they left cookie cutter solutions to problems that made their military more fungible. If I move these guys from southern France, to northern Greece, everything is set up the same way and they can hit the ground running. Where we have standardized manufactured equipment, they had standardized infrastructure.