I still have the wooden 10" Keuffel and Esser that I inherited from my father and that I used in college. These days I use my HP15C unless I want to provoke glee and amusement in my younger colleagues by sporting my Pickett slide rule in my shirt pocket.
How does this compare to something that might be offered in a strong computer science, computer engineering, or electrical engineering program in the U.S. or Europe?
I've been writing go professionally for about ten years, and with go I regularly find myself saying "this is pretty boring", followed by "but that's a good thing" because I'm pretty sure that I won't do anything in a go program that would cause the other team members much trouble if I were to get run over by a bus or die of boredom.
In contrast writing C++ feels like solving an endless series of puzzles, and there is a constant temptation to do Something Really Clever.
"No one cared who your parents were." Did it never matter if my dad was a pfc and yours was the base commander? Ideally it shouldn't matter,but in practice?
Lots of apparently unexplored alternative explanations. In times of uncertainty, you don't hire unless you need to. Another junior developer or customer service agent can be delayed, and youngsters in the labor force are most exposed to this. But if you need a home health aide, you probably don't have a lot of choice: somebody has to change grandma's diapers. Tariffs top my list of uncertainties for businesses, but interest rates are a close second.
A competitive athletic program is a huge time sink: practices, weight room, travel, meets, game day. That time spent elsewhere can go a long ways to covering college costs, such as taking extra classes and finishing a semester or quarter earlier or going to a school with a good coop program. Even a low-paying on-campus job can be competitive if the per hour rates are fairly compared.
I experimented with TLA, and the graphical toolbox didn't seem to work or match the tutorial. Kinda disappointing: I wanted to use TLA, and I'm otherwise a big fan of Lamport's work, from the utilitarian Latex to the intellectually satisfying paper on time, clocks, and distributed systems.
When I worked at Google, Ian Lance Taylor was in the pool of randomly assigned code reviewers. He was polite, firm, and informative. It speaks well of Taylor and the project that he was doing this kind of review--- it's a version of the YC advice about founders doing customer support.
And maybe I'm shallow, but it was a thrill to see his initials show up on my code reviews. Thanks for all your work on golang.
Favors minimal text entry. You keep the type information in your head and enter fewer tokens. Historically you also reduced the work and improved responsiveness for the interpreter, which might have been running on an 8- or 16-bit computer at 5 MHz.
Heck, one of my co-workers at a FAANG freaked out when he realized that he had used his personal phone to take a picture of a meeting blackboard instead of his corp phone. He spent the afternoon trying to figure out how to scrub the photo.
We hoisted the weight way overhead in the field house on a pulley system. One pulley was for the hoist, and another simulated the anchor point that the leader was falling past. The weight was held by a releasable clamp, and when release was triggered, you got a simulated leader fall: lots of slack and lots of potential energy. The rope burn eventually healed...
I don't find the x86 minutiae objectionable. If you want to build or even just understand an OS that runs on real hardware, you will have to deal with processor and hardware minutiae, and this gives one example of what you might encounter and how to deal with it.
I used and rather liked Darcs in the dark ages when SVN was the best alternative. Then I discovered that it would happily accept largish binary files, but would later refuse to give them back when I needed them. I could have lived with an error on check in.
Bad title for the list. The books by Feynman, Weinberg, Sagan, Steinbeck, McPhee, and Levi didn't shape science. At best they are good descriptions of what happened in the century.
I've worked at startups and at a FAANG. For many years, I've told people that they should never do a startup for the $$$; their expected value is higher at a FAANG. They should do a startup only if they're interested in the technology or the people.
"...the child of Bobby's Nordic girlfriend..." does have a role in the modern-day episodes (probably). I didn't figure this out until my second or third reading.
K&R is the best known, but his other books are terrific. Software Tools showed how programs can simultaneously be powerful and simple, and decades later I still use things from Kernighan and Pike. Just today I wrote an AWK one-liner to process a log file.