I work on legacy software for an embedded system that supports transportation infrastructure. I'm pretty sure it has a year 2038 problem (based on first-princi

I work on legacy software for an embedded system that supports transportation infrastructure. I'm pretty sure it has a year 2038 problem (based on first-principles; I haven't confirmed that with a test). The 32-bit time is baked into a serial data format and at the beginning of every internal device file. I don't think this is on anyone else's radar where I work. The only other person who spelunked in the software at this level retired at the end of 2022. (For better or worse I don't retire until after 2040.) I anticipate this is going to occupy part of my career just like Y2K did for a generation of programmers before me. That is, it will if and when I can convince management to prioritize it. Cynically I wonder if they may run out the clock, playing chicken with the last possible moment to begin to move on it. Our manager likes to say, "political, fiscal, technical - in that order" as an amoral description of how things operate. But this is different than refusing to implement, e.g. IPv6 by an artificial deadline.