RustySharp

break and continue are just goto in disguise ... use return instead of break

An if statement is goto in disguise. So is a return.

Some would argue having 10x 4-line functions are worse for readability and debugging than a single 40-liner, because to actually understand the code you have to jump around all over the page (another disguised goto - for your eyes!)

I can certainly symphatise. I've been pushed to temporarily take management roles, either client-facing or reporting directly to a C-level. Been encouraged by the team to take on the roles permanently.

What they don't see is how mentally exhausting it is to actually shield the team from the BS on the other side, when you genuinely care about the people in your team. Yeah, I could use the money, but I don't trust myself to not act on the homicidal thoughts that pop up once in a while during those times..

based on curiosity, which was short lived, because Linux (Mandrake) at the time was too challenging.

Story of my life back in high school. Except it was Slackware, from the back of a magazine.

Wasn't until I took Operating System Design in university that the whole linux/unix philosophy clicked.

Or, someone donated 2.5-12, Apple matched it and filed the whole thing under their corporate account.

grep is your very best friend.

This. And also, in many cases, an 'adjacent' grep may help. Say you want to move the "OK" button on one screen. Searching for the string "OK" would be overwhelming as that would be all over the shop.

But you notice there's a "Setup..." button next to it. Searching for that could potentially cut down your search results by orders of magnitude. The more obscure the text, the better.

Those were the times when I had to pull out my hard drive, ride my bike to my best mate's house, and plug it into their PC so I could finish up a report due the next day. All because Windows 95 didn't shut down cleanly and refused to boot.

Honestly, the joke landed anyway. I've done numerous uppercase-Q trying to quit, because I didn't let go of Shift fast enough after typing the colon...

I feel bad for you, son...

The meme refers to the old adage "C lets you shoot yourself on the foot. C++ lets you shoot both feet and gives you a shotgun to do it" - referring to the how C allows you to perform memory-unsafe operations (causing corruption, or worse, security vulnerabilities), and C++'s complexity, potentially obscuring such unsafetyness.

Rust's memory safety tries to save you from doing (un)intentional bad stuff, by giving you compile-time errors. It's also the bane of everyone so used to C/++'s ability to just pass around and modify whatever memory they want.

"Mark works for MS" is a massive understatement. He's CTO of Azure now.

And speaking of Sysinternals, arguably the most exciting update was when ProcessExplorer got a dark mode late last year :)