Parchives. Great for adding recovery to any file. :) I use them [now par2cmdline-tbb] religiously for archives. I started doing this years ago after having CD-R's burned on a drive (Plextor, no less) that I started having a hard time reading on any other drive.
Bitdefender likes to revert to default settings frequently. I prefer Windows Firewall (Win7) and have to turn off the Bitdefender firewall usually at least once a week.
LEDBenchmark [1] does a good job with their own spectrum and flicker graphs. So far, the LED bulbs I have gotten based on their results have been good.
A regional (to me) real estate web site that we had to work with had a data service that output XML. It was naively implemented and managed to output malformed XML. Mostly in the form of a CSV field crammed into an XML field with non-conformant XML markup.
A few jobs ago (factory automation), we had a story from one of our projects where a device (would have been a PLC or relay panel) was failing. Rather than dust, metal filings had gotten into the case and were shorting out connections. A "quick" cleanup, and the device was working again.
The old Right Stuf website catalog [1] (old catalog not accessible) would list their pages with the first two letters of the first item's title on the page. I found it immensely helpful, and even "borrowed" the idea for a directory on a local govt website (also no longer accessible).
My work machine is not nearly that beefy. :| I do often have 8-10 cmd windows open. According to task manager on my machine, each PS instance on start is 90-100MB. I didn't dig deeper to see if that RAM usage would shrink over time.
I know we have machines with lots of RAM now, but at 90-100MB (PS) vs 4MB (CMD) [1] RAM usage per instance (not counting the conhost instance that also spawns), I think I would still want CMD around.
[1] https://www.crashplan.com/en-us/business/