This is cool. I had no idea about most of these.

I always leave my project in a state where it doesn’t compile or run (not commits, obvs) so I’m forced back into understanding exactly what I was doing when I left off to fix the error.

How do I remember what the command even is? Like how would I discover the grep tool without using the Internet?

Online

Ok but what if my Wi-Fi isn’t working

In a past career, I was a mechanical design engineer; I’ve probably spent 10,000 hours of my life in SolidWorks. Not once did I feel like a 3d mouse would speed me up or otherwise solve my problems. I trialed a spacepilot for several months and just couldn’t be arsed after awhile. What do others get out of them?

I started using Python ~15 years ago. I didn’t go to school for CS.

Compared to using literally anything else at the time as a beginner, pip was the best thing out there that I could finally understand for getting third party code to work with my stuff, without copy paste… on Windows.

When I tried Linux, package managers and make were pretty cool for doing C/C++ work.

Despite all that, us “regular” engineers were consigned to Windows.

We either had to use VBA or a runtime that didn’t need to be installed.

From other discussions I’ve seen, the guy stepping down was frustrated by having C code rejected that made lifetime guarantees more explicit. No rust involved. The patch was in service of rust bindings, but there was 0 rust code being reviewed by maintainers.