On the job training. Entry level pin setter mechanic training is fairly basic (Lock out tag out procedures, basic machine operations, simple trouble call resolutions (ball returns, re-spotting pins, that sort of thing)). Usually you'll be working with a full mechanic, learning how to do various repairs and preventive maintenance on the machines.
After working full time in a wide variety of tech since 1983 (embedded systems work on medical equipment and commercial fire alarm systems, hotel reservation systems, ramp and fuel delivery systems in aviation, multiple startups in Silicon Valley, etc, ad naseum) I’m currently taking a break and working as a pin setter mechanic at a couple of local bowling alleys. The work is physical (running up and down the back of the 40 and 64 lane alleys, climbing up on the machines) and challenging in its own way: the machines were designed in the 50s and are a complex assortment of pulleys, belts, gears, cams, levers, etc. There is even a mechanical “computer” that acts as a state machine directing the operations of the machine. I still get to use my problem solving skills but in a much more tactile way. Also, no pointless meetings, conference calls. Downside: the pay is terrible. Fortunately I’m in a position in my life where that is not nearly as important as it used to be.
I was a user of a very early version of Zortech C++ (one of the first native C++ compilers (late '80s); no running through cfront) and ran into a very subtle bug in the math routines: sometimes when doing math with 8 bit values the answers would be corrupted. Took a while for me to track down the bug but I eventually found it in the assembly output. Turns out that the math was actually being done with 16 bit registers and the high byte (AH) was not being cleared and this would sometimes set a carry (I think, my memory is fuzzy on the details).
Walter was quick with a fix. Sometimes it is the compiler, but usually it's not.
A real shame that Forth wasn't included in the tested languages. Chuck Moore has been an advocate for more energy efficient computation for a while now.
It goes into amazing detail on the history of the spacecraft and the events that made it possible. For example: the story of an intern figuring out the '3 body' problem and, from there, the concept of 'gravity assist' gave me goosebumps
I just installed GuixSD 0.12 last week on a Dell 13 7000. Went mostly smoothly (had to use Grub BIOS instead of UEFI, that's been fixed in 0.13) after I replaced the Intel WiFi card with an Atheros based one.
My needs are simple: emacs, Clojure (with Icedtea), Icecat and StumpWM. Plus all the guile goodness!
Just realized I'm living in a system with four Lisps front and center (guile, Common Lisp, elisp, and Clojure)
I'm working with the Brunswick A2 machines. Here's a link to the service manual if you're curious what these machines are like (PDF): https://brunswickbowling.com/uploads/document-library/Servic...