Exactly.

I’m not interested in any company announcing what they ‘plan’ to do, I’m interested when they actually do it.

It IS going to happen, if you keep using big tech operating systems and services, because THEY want it to happen and will not stop pushing until it DOES happen.

Bad PO: “So it will only increase the chance of bugs if we don’t do it? There won’t necessarily be any. So we can skip it and just put the feature in.”

I hope you have a good PO who is on the same page as you, but to a bad PO, it still sounds optional.

A civil engineer doesn’t say “If we don’t put supports there’s a chance the ceiling will fall in and people may die,” because history has shown there are plenty of unscrupulous project managers who are quite willing to take construction risks, even with people’s lives. As a result of this there are now plenty of laws in construction, and a civil engineer has a convenient fallback of saying “If we don’t put supports it won’t pass inspection, and we won’t get paid.”

Everyone wants to get paid.

In software we don’t have many laws we can fall back on to justify our work, but we can still treat our tech debt and refactoring as if it’s equally mandatory.

“To add feature x, we need to resolve problem y. The feature can’t be added until we’ve completed this prerequisite.”

Here you go fam

Perhaps you could add some side panels to dress it up a bit

Pretty awesome!

Building it on a cart seems like a great idea so you get access from all angles to build it out or and change things around.

Good access is something my servers really suffer from, so your setup looks like a dream to me!

Cute JetKVM too :)

So infuriating when you have some dickhead making themselves unfireable by intentionally convoluting the codebase and chasing out any other hire. And even worse when management bought into it and think the guy’s an actual irreplaceable genius.

Probably even believes it himself. I hate narcissists.

As far as I understand, it’s purely marketing semantics.

The point of the ‘Turbo’ button is to slow the CPU down to provide compatibility with old software that was written with a fixed clockspeed, where the software would become unusably fast on newer CPUs.

Calling this a “slow” mode or “compatibility” mode wasn’t very marketing-sexy however, so manufacturers just flipped it around and called the normal speed ‘Turbo’.

With later systems, developers all became aware that varying CPU frequencies were a thing, and started to base their software timings on the realtime clock instead.

So in later systems there was no longer any need to have the CPU run at anything other than its maximum (normal) speed - and the turbo button simply went away.

Not in my case, no. The content was completely custom to the organisation. I assume they were big enough that they felt like a lot of the risk would come from coordinated spearphishing carefully crafted to look like genuine corp email.

No mom, I’m gonna BE a girl for Christmas. puts on programming socks

For real! A course is work. If I’m working I get paid for my time. End of story.

Don’t let them rob you! (any more than they already are)

Family member not giving a fuck what an ‘AWS’ is, more like.

We needed to label them because the requirement was not only that we don’t click them, but that we use the “report phishing” function on them.

Also some of them were pretty funny.

A previous (huge) company of mine sent out a lot of phishing test emails, some of which were pretty convincing.

As developers, we quickly discovered that all the emails had a metadata header in them which identified them as a phishing test, so we set up a filter for it so every email since is clearly coded with a bright red “Phishing test!” label.

Trying to ‘hide’ the use of a racist term because you’re a racist would be one thing, but using the term in a way that is not at all meant as pejorative is another.

In the automotive context, the term meant something like “Putting loads of pointless mods on your ‘shitty’ Japanese car that makes it look even uglier and doesn’t make it go any faster.” - and in that context it was unambiguously a slur, disparaging the Asian import scene in favour of the ‘superior’ western aesthetic and way of doing things.

But even in the automotive context, people can reclaim the term and say effectively “Yes - my car is ‘riced out’ - that’s the aesthetic I want, and I’m proud of it.”

In some ways it’s quite appropriate that this term would extend from Japanese cars into tricking out your operating system. Given the number of waifu wallpapers you see in screenshots, ‘ricing’ has quite a lot of overlap with anime aesthetic, geek cuture and ‘weebs’ (which is another term that was used as an insult, and now reclaimed by people who proudly describe themselves as such). People who have historically been looked down upon by most of society but internally wear their ‘weebdom’ as a badge of pride.

It’s hardly an insult when you are the one saying it about yourself, and doing so proudly.

The origins of the term undeniably are racist, yes, and I was also surprised that those using it weren’t largely aware of the fact.

But it’s also true that meanings unavoidably change over time, and the intent of what you say is also important.

The person you responded to isn’t wrong - there’s now a popular acronym people are using which is Race Inspired Cosmetic Enhancement

And yes it’s a backronym. The pejorative term came first, and the acronym later, but it’s certainly part of redefining and reclaiming the term to free it from its origins.

Like it or not, I think the term is very much here to stay.

I feel like that’s almost a macabre in-joke to the adults involved

You know those illustrated story books for children?

The ones with cute anthropomorphized animals going about their jobs in a fairytale animal society, posting letters and walking kids across the street and fixing cars in the garage?

If you can’t accurately depict yourself doing your job as a drawing in one of those books, it’s not a real job.

(I’m also a programmer, by the way…)

It’s not “people” who are causing the proliferation of formats like webp though, it’s the web industry.

If you are a web platform, you want a format that gives you acceptable quality for the smallest size to reduce your bandwidth. You also want one that loads as fast as possible from a CPU prospective, so your site renders as fast as possible.

These are factors webp was designed for.

To your point, for home users jpeg remains a good-enough choice with no reason to change it. A preferred choice even, due to broad legacy compatibility. But we aren’t seeing proliferation of webp because people are at home willingly going “file -> export as -> webp” - no, we’re seeing it because industry is converting uploads to it, and people are saving those images.

Same for me with Markdown. Love the simplicity.

I went through a phase a while back of evaluating a bunch of note-taking and to-do apps, and hating almost all of them for being proprietary products with so much vendor lock-in.

I eventually settled on Joplin because it just uses plain old markdown, and allows you to selfhost the storage back-end so you own your data.

So because of that, my recipes are just a folder (and some subfolders) with markdown in Joplin.