41–50 of 52 posts
The few engineers I know that have this, went through some sort of ritual passage. A project or idea that forced them into digging.
The 787 design & assembly line spin-up work was done 2004~2007.
The big merger coming in the 99 being the creation of ExxonMobile which would create duplicate documentation systems spanning the dates the author gives.
Earlier quoted context omitted.
NASA wastes billions and billions of dollars on space projects that will likely never fly. Rest assured, there’s still plenty of political mileage to be had from space money.
Is Artemis really that upsetting... =3
This reminds me of the Saturn V. If I remember correctly, no one knows how it works anymore. https://en.wikipedia.org/wiki/Saturn_V
Lol, NASA literally left an instruction manual on how to go to space, and return safely. The contributions those folks have made over the years is related to just about everything you depend on these days. People just choose to ignore the documentation, as there is less political mileage in throwing money into space these days. =3
This, I'm so sick of this "no one knows how x works anymore" when it comes to ancient technology. Aerospace engineering is a whole field, do people seriously think we've just forgotten how to get to space?
This is something ive seen at three defense companies ive worked for. They will toss the new hires in bad times but hang onto the old timers and let them do as the please. The rto never applies to them and they horde like smaug. The best job in defense is to be one of these. Boeing made lip service to passing on knowledge but when it came to true core ppl they were never part of the process.
In terms of "Ars Longa, Vita Brevis" [1], I'm not as good of an indexer / teacher as I wish I was.
https://www.slatestarcodexabridged.com/Ars-Longa-Vita-Brevis
>Unfortunately, the internal team doesn't know what the secrets are, while I do. I even invented a few of them, and have my name on some related patents. I'm confused about how something can be both a secret and patented. Isn't the point of a patent that it is public and no longer secret?
Earlier quoted context omitted.
Git is only 19 years old, I suspect the bigger problems in this area are more likely to be 30+ year old, as most of the people who built such systems are likely to be retired.
Some git repos were ported over from SVN repos that were migrated from CVS. I never migrated anything into CVS, so I don't know if that was common at the time. But there are a lot of git repos out there with commits older than git itself (the Linux kernel itself I'm sure is the most prominent example).
Several embedded colleagues still work on pre-tarball workflows though: zip files and word documents.