4 ms·
Based on your post, I was curious how long the stuff I write will be around for. I write software for cars, so that means a lot of legacy stuff, I've seen code
by RealityVoid 2y ago
Based on your post, I was curious how long the stuff I write will be around for. I write software for cars, so that means a lot of legacy stuff, I've seen code written by coleagues hang around in the next generations of product for about 10 years. Then you have the life of the vehicles that varies greatly, but at least _some_ of the vehicles will reach 25 years, so I'd expect at least some of the SW I write to linger around for ~35-ish years. Not bad.
A bit unsettling when I think about the varying quality of software though.
- jeffreygoesto 2y agoCan relate. My in-vehicle SW is driving for 20 years and counting (and it is not just some standard AutoSar stuff but high performance video processing pre "A" "I" ;) ). When I see cars with it I always remember some funny anecdotes and good fellas that I was lucky to share some journey with. Making a durable dent feels satisfying for sure, but also doing "cyber physical" projects and moving real things around.
- aYsY4dDQ2NrcNzA 2y agoDent.
- scruple 2y agoYeah, I worked for an embedded company for ~8 years and there was a lot of old code kicking around that had been carried forward across product iterations. I know, from talking to colleagues who are still there today, that code I wrote ~20 years ago is still kicking around here or there in the current offerings. > A bit unsettling when I think about the varying quality of software though. That's just the business.