Scratch

That’s got 70% isopropyl in it. Sometimes perfumes too.

If you don’t have any, or want a food safe alternative, soak the remaining sticker in cooking oil.

Isopropyl alcohol also works.

Steam Machines showed them they needed to enforce a quality floor that other manufacturers would need to exceed.

Yes, I’m still mad Steam Machines didn’t take off.

It’s true. Every book, movie, game or piece of software you’ve ever used (unless you made it yourself) has been subject to some kind of licence, that can be revoked.

The fact the internet actually works at all is nuts.

Just buy a good 3d printer for your first. Sure, it’ll cost money, but the heartache of constant troubleshooting and tweaking can just suck the fun out of the hobby if you just need this print to succeed.

Prusa Mini+ (I think) Bambu A1 Mini (this would be my #1 starter printer before the security updates they done)

Download a cracked version. You’ve already bought a license.

The graphics dated fairly quickly but I believe the ai, combat and atmosphere should still be excellent.

10mm HV Penetrator from F.E.A.R

https://fear.fandom.com/wiki/10mm_HV_Penetrator

thunk thunk thunk thunk

Are ‘super-clickbaity’ articles a thing of the past? The signs point to yes!

80% isopropyl alcohol. Use a soft brush wet with some of the alcohol. Brush around the affected areas. Let it dry and that’s all for me.

I wouldn’t recommend dousing electronics in less than 90%. Feels sketchy. But I have nothing to back that up besides “electronics cleaner” being 99% iso.

Ok

Pfft. Amateur. I have a grandfathered license from back when it was $100 one-time payment.

Let’s me install on up to 5 machines at the same time

Practice, imo. You can begin interactions with the mindset of “I want to make friends” and get used to that idea.

Difficult to make, too heavy to be effective, and iirc yeah, unreliable.

If something is growing in it; it’s not poison.

At least you know it’s not actually poison…

Or skin tone.

If you are open to friendship with this person, then you could still go for a drink. It can be nice to have someone who has experienced similar negative things to talk to.

The site doesn’t define what a code smell is, though. It’s just a list of Don’t Do’s.

That’s kind of the nuance I would be hoping for.

Something like:

Code Smells are clues that something is amiss. They are not things that always must be ‘fixed’. You as an engineer will, through experience in your own codebase and reading of others, develop a sense of the harm imparted by and the cost of fixing Code Smells. It is up to you and your team to decide what is best for your codebase and project.

(The rule of 3 formatting was intentional, given the community we’re in)

I think to present rules like this as hard rules, with little explanation and no nuance is harmful to less experienced engineers.

A prime example here is the Duplicated Code one. Which takes an absolute approach to code duplication, even when the book that is referenced highlights the Rule of Three:

The Rule of Three
Here’s a guideline Don Roberts gave me: The first time you do something,
you just do it. The second time you do something similar, you wince at the
duplication, but you do the duplicate thing anyway. The third time you do
something similar, you refactor.
Or for those who like baseball: Three strikes, then you refactor.

I’ve seen more junior devs bend over backwards, make their code worse and take twice as long to adhere to some rules that are really more what you’d call guidelines than actual rules.

Sure, try to avoid code duplication, but sometimes duplicating code is better than the wrangling you’d need to do to remove it.

Making extra changes also leaves extra room for bugs to creep in. So now you need to test the place you were working, and anywhere else you touched because of the refactoring.