![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
The Bug in the Computer Bug Story by Matthew Wills.
Learn something new every day! I've believed the "bug" origin story for many years.
I've also held onto this small art print by R.C. Matteson since my undergrad days. I don't need to have it out, but I like knowing it's there to express my programming experience some days.
I finished writing up my response to "The Manager's Path" by Camille Fournier. Here are a few links from there.
The Tyranny of Structurelessness by Jo Freeman aka Joreen, a classic essay on why managers are necessary.
On Being A Senior Engineer which includes the suggestion to use senior influence to sponsor (rather than mentor) underrepresented people in engineering. Recommend them for positions. Highlight their accomplishments. Praise them publicly. Also refers to What Does Sponsorship Look Like by Lara Hogan.
The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) by Joel Spolsky. From 2003, and still being passed around because it's needed.
The Mom Test by Rob Fitzpatrick. "How to talk to customers and learn if your business is a good idea when everyone is lying to you." I read this for generic interviewing advice, and the gist is don't go in asking for approval or thinking you know the answers. Ask open questions and listen a lot.
In 1947, engineers working on Harvard University’s Mark II computer found a bug gumming up the works—a moth had squeezed into one of the machine’s components. After extracting it, somebody taped it to the log book with the caption “first actual case of a bug being found.” That log book, with moth intact, is in the collection of the Smithsonian Institution’s National Museum of American History today. Scholar Fred R. Shapiro describes what supposedly happened next:
“The moth is said to have inspired the scientists to speak from then on of debugging the computer, with bug originating as the later back-formation from debug.”
So “debug” and “bug” were bits of computer slang that were eventually adopted by the larger culture. It’s a great story—but not very etymologically correct.
Learn something new every day! I've believed the "bug" origin story for many years.
I've also held onto this small art print by R.C. Matteson since my undergrad days. I don't need to have it out, but I like knowing it's there to express my programming experience some days.
I finished writing up my response to "The Manager's Path" by Camille Fournier. Here are a few links from there.
The Tyranny of Structurelessness by Jo Freeman aka Joreen, a classic essay on why managers are necessary.
On Being A Senior Engineer which includes the suggestion to use senior influence to sponsor (rather than mentor) underrepresented people in engineering. Recommend them for positions. Highlight their accomplishments. Praise them publicly. Also refers to What Does Sponsorship Look Like by Lara Hogan.
The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) by Joel Spolsky. From 2003, and still being passed around because it's needed.
The Mom Test by Rob Fitzpatrick. "How to talk to customers and learn if your business is a good idea when everyone is lying to you." I read this for generic interviewing advice, and the gist is don't go in asking for approval or thinking you know the answers. Ask open questions and listen a lot.
