You are -mostly- right but there is also the factor where a specific sort of negative reaction can actually function as a recommendation later.
I've definitely missed out on work sometimes due to having a reputation for being about as subtle as a brick to the face with no lemon, but I've also -got- certain pieces of work as a direct result of being criticised and somebody who heard the criticism thinking "if he annoyed that person that way, he's probably serious about doing the right thing."
I would, however, suggest that probably I would've done better overall if I'd toned it down a bit.
For the past twenty years I've bought thinkpads which during productive time have generally run (a) Firefox (b) some sort of system that lets me get full screen X11+xterm+ssh to do the actual work on remote development servers.
I've gone through VMs, colinux, cygwin, and currently WSL2+VcXsrv for (b) and so far it's basically worked out fine.
(I'm aware that desktop linux wrangling is far, far easier than it used to be but this setup very rarely annoys me and if I'm going to do some recreational geekery on a "because I can" basis it's far more likely to be something like playing with a new programming language than reinstalling my laptop)
Once I'd worked it out - which was after the problems were public and therefore the price had utterly cratered - they were by far the cheapest storage per Gb available at the time (think "by a factor of two").
I would not have let a normal business user near one, but the developers I was supporting were most pleased about their larger than expected scratch disks for test databases and intermediate compilation artifacts.
Everything breaks. Things that at least break predictably make me happier than the alternative.
A friend of mine who was once at Google mentioned that in a meeting once their SRE group was told by their senior manager roughly "you've broken stuff in $time_period far less than your outage budget, and that probably means you should've been rolling out features faster".
Assuming you have the budget for it a worst case scenario of "I made my son happy while achieving nothing -else-" doesn't strike me as terrible at all.
The expense of fab node transitions back when every chip manufacturer built their own fabs seems to've contributed significantly to the demise of a fair few architectures over the years.
My favourite thing about my Indigo2 (bought second hand for relatively cheap in the early '00s) was that unlike all the x86 kit I had running, it survived power brownouts with a line logged to console mentioning it had happened.
When the area I was living at the time was having periodic power issues I'd check the console any time I got home, and if there was a new log message I knew I'd need to bring all the x86 kit back up once I'd had a coffee or three.
So far as I can tell, people still call ARM RISC because it's load/store and x86 isn't (feel free to correct me on this, I'm not a CPU person), and ARM's instruction proliferation gets glossed over.
I do remember writing asm for the arm26 (arm2) chip in my Archimedes and that was definitely actual RISC, but obviously these days not so much.
That's how we did it and so far as I'm aware is the most common answer to "How do we keep Tor while keeping the abuse mitigation efforts required within the resources available?" for services in general.
Back when I was staff on (pre-madness) freenode providing an onion address was pretty much the only way we could afford to support tor at all given the moderation resources available.
Smaller networks often (usually regretfully) end up blocking tor entirely if they don't have the capacity to set up such infrastructure.
Any chance of pavlok support? It doesn't exactly vibrate but ... (and if the answer is "patches welcome" I can always make another attempt to convince my rpi to talk to the bloody thing myself)
File::Slurp is broken AF though, and obsoleted by File::Slurper since the original can't be fixed without breaking accidentally working code in the wild.
Still mostly fine so long as you know you're only dealing with 7-bit ASCII, IIRC, but Caveat Emptor.
I've definitely missed out on work sometimes due to having a reputation for being about as subtle as a brick to the face with no lemon, but I've also -got- certain pieces of work as a direct result of being criticised and somebody who heard the criticism thinking "if he annoyed that person that way, he's probably serious about doing the right thing."
I would, however, suggest that probably I would've done better overall if I'd toned it down a bit.