The engineers who designed the #Voyager probes half a century ago even thought of the possibility that a wrong sequence of commands may point the antenna dish away from earth (like someone did a couple of days ago).

And they implemented a self-adjusting mechanism that a few times a year scans the positions of a few known stars to infer the position of the earth, and point back the antenna in the right direction.

50 years later, these wonderful machines are still working, tens of billions of km away from earth, with only 69 KB of RAM, and even a wrong sequence of commands won't put them out of use, while nowadays 4 GB of RAM aren't even enough to start VsCode or IntelliJ.

The more I understand how they were designed, the more I feel like an early Medieval engineer looking at the Pantheon or other marvels of Roman architecture. Some amazing skills, knowledge and attention to details have been lost from that generation to ours.

@blacklight forward thinking... missing in today's software engineers
@george @blacklight back then, software engineers were actually engineers, as opposed to the IDE google-jockeys we have now. Software cobblers?
The story of Mel

Software dev team A has an expert chiefly responsible for its main program. That genius routinely codes amazing optimizations incomprehensible to anyone else.

Team B distributes responsibility and authorship. Readability is consciously priorized over performance. Coding standards are obeyed.

Which team can implement a brilliant new idea?

Has fewer bugs?

Fixes them faster?

Will exist in 5 years?

Would I prefer to work in?

B. B. B. B. B.

@uastronomer @dnorman @george @blacklight

@george @blacklight or shut off by bean counters....
@george @blacklight A pretty good number of today’s software ”engineers” are ex-baristas who figured out they can take a 3 month Javascript and React course straight off the streets and earn 6 figures. No curiosity or basic knowledge of CS - what makes the machines tick. Everything’s a black box.