Is it possible for you to share a bit more? I'm sorry for being vague but I assume anything would be of interest of the HN public right now. If there is really a need for a topic, I couldn't help but Googled your name, looks like you are involved in a project called "Poppet", maybe it is possible to speak a bit about that one?
Thanks!
I've shared this before but a really interesting internal publication from the mid-80s was A Year in Development with lots of interviews and photographs. https://archive.org/details/year-in-dev/mode/2up
https://metatalk.metafilter.com/13606/Jessamyn-in-Valley-New...
Data General History: The Fair Bastards http://www.teamfoster.com/billteamfostercom
via https://news.ycombinator.com/item?id=33793837 - no comments
http://archive.computerhistory.org/resources/text/Data_Gener...
Must be interesting time though. I love those "Byte" and "Dr.Dobb" magazine ads in general. They are all very creative and sometimes do not shy away from "exotic" stuffs such as beautiful ladies and such. I wonder what sub-industry still has that kind of culture :)
That said, it IS still a great book, and given that Kidder's not an engineer, he did an amazing job.
Maybe I'm missing some crucial context or something.
Nice interview with Sonderegger.
"what a dummy he was for believing us" -- I don't know if that's really what they thought. Maybe it was more like "he didn't try to verify anything, ask any hard questions, or get any context on it." It's been too long since I've read the book.
Did you like the bit about him telling the Marines, "I want to be a close air support pilot in 'Nam!"
And they said, "No, you're going to be a computer programmer!"
It goes counter to the folklore that they ignore your background and just hand you a rifle.
I don't even know the name of the position of the guy who decides where draftees are sent after basic training, but I expect that as with so many other things, some of them are a lot better at their jobs than others. And perhaps the Marines do a better job of it than the Army.
A mainframe is a high-RAS (reliability, availability, serviceability), high-performance, high-cost, modular multiprocessor machine with specialized coprocessors; running a hypervisor-style operating system that is largely concerned with allocating resources and managing security partitions. Interconnections among modules happen at system bus latencies and bandwidths.
I didn't mean to attack an individual, and my management comment was more general than just Tom. I saw Tom's actions as reactions to a bad situation.
My comment is more directed at the people I worked with who took the wrong message away from the SOTNM folklore. Being against the ropes and fighting for your survival at all costs isn't something to look forward to, and definitely bot something to expect from employees.
For context, DG was about to go obsolete, but Tom (and others) recognized this where almost nobody else would've, and managed to transform the company from a mainframe company to a minicomputer company, with a small, ragtag team of dedicated engineers, without a map or prior art, and with desultory support from the checked-out, incompetent C-suite.
Tom's idiosyncratic, no-nonsense style wasn't for everyone, but I can think of very few tech leaders who could have succeeded as a manager in that situation.
Source: worked directly for Tom at Data General for several years.