Scratch

Let’s try more!

Oh damn. I had no idea.

Edit: see response for extra context and bad news.

Thangs aggregates other sites, or so I’ve been told.

Russia btfo

Bookmarking as I too am interested in this topic.

The idea cookie is the Subway double chocolate chip, microwaved for 7 seconds.

Warm gooey chunks with a crisp rim. The best of all worlds.

Honestly Subway should give up on their C- tier sandwiches and focus on what they do well.

Premium Pocket actually cached a copy of the page.

It also had human-curated recommendations.

you are supporting the Chinese regime (and probably Russia) by your actions,

Yes, lets all support the USA, currently a bastion of freedom for all.

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.

Started season 2 of Andor after rewatching season 1.

The step down in quality is really incredible. Apparently it gets better in the back half.

I’d recommend just re-rewatching season 1.

Yes!

(It might be the only Star Wars content worth watching in recent history. )

You can easily find out. 2 machines (even virtual machines) one set it’s DNS to the PiHole, one not.

Both hit the same sites in the same order. Compare network traffic.

Be a man.

‘git commit -am “changes”’

Anycubic has (imo) dire customer support. I’m rooting for you, but don’t expect any delivery updates until you hear your doorbell ring.

Start printing things first.

Check for issues and address those issues.

If you start disassembling, you won’t know what needs the most attention, and you might just get bored and give up, without knowing what printing can do for you.

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.