“Of course. Why else would I be wearing a hot dog costume?”

Yeah, but if the bubble lasts longer it’ll hurt us more when it does collapse.

Plus we’ll have to deal with more clanker bullshit in more of our daily lives for longer if it takes a long time for it to collapse.

God I hope so.

The behaviour is particularly interesting because physically replacing the memory on a Raspberry Pi is already well outside the scope of an ordinary upgrade.

I mean… aren’t hackers the target audience for Raspberry Pis?

Yeah, if the reasoning they give isn’t just straight bullshit, then I guess I don’t want to see them drown in support tickets. But it also seems like this move runs pretty counter to the whole point of the Raspberry Pi.

(Plus, can’t resellers buy 2GB models, redo some of the screen printing, and sell them as 8GB models without even trying to upgrade the RAM to 8GB? That seems at least as bad as getting a Raspberry Pi with a dodgy 8GB RAM chip.)

“One prominent theory suggests they may be a sigil used in the worship of the deity ‘missingno’.”

Time to go back to commissioning portraits from painters who forage to make their own pigments.

Ok, hold on. How to “back up an organization’s source control?” Are you saying the organization in question has a source control hosting solution of some sort and needs to implement a backup strategy for the contents of said source control solution?

Or are you saying the organization doesn’t have a source control solution and they need a source control solution.

The former question is an entirely reasonable sort of question to ask. (Not one I have much expertise on, but still a legitimate question.) If your question is the latter, let me say: source control is not a backup solution and conflating the two is a mistake.

I once talked to the guy in charge of another team at a company where I was working. We’ll call him Nick (because that was his name). I found out that Nick had instituted a policy wherein each developer on the team under him had their own dedicated branch in Git to which they were required to commit/push at the end of every day no matter what state their code was in. main was to be merged into these developer branches regularly (the only sane part of the whole scheme) and the developer branches would be merged into main with PRs which had to be reviewed personally by him. Then, if something went wrong and they lost work, they couldn’t lose more than a day’s worth of work (because at the end of the day yesterday, they’d pushed their code) – or so the “logic” went. Nick was a terrible person. Don’t be like Nick. (His whole mindset was “we have to protect the codebase from these ‘junior devs’ so they don’t ruin it! And we have to protect them from their own incompetence as well!” Weird guy. Definitely had a power-trip sort of complex.)

Commits are not a box you unceremoniously dump your code in so you can ship it off to put it in cold storage on the central Git repo backup server. They’re something to be curated. Push only atomic commits. (That is, don’t put multiple unrelated changes in a single commit. Also make sure that your commit covers the whole of a single, deliverable change.) Never knowingly push commits which put the code in a broken state or commits with half-completed changes. Strive for an ideal world in which any single commit in the central repo can be safely reverted without breaking other commits. When something is broken, your organization will thank you for not leaving a mess of interrelated and interdependent commits. And when one thing needs undone, they’ll thank you for making sure that reverting a single commit will accomplish it. The structure and content of your Git history is an important part of the product just like comments and documentation. (And that segues nicely in to another point: Write good commit messages while you’re at it.) There’s nothing more satisfying than a clean commit graph with good commit messages.

(One qualifier here. What you do on your own dev machine is your own business. Make sure that what you push is well formed. How you get there, who cares. If your coding style involves “oh, while I’m here, I’ll fix this unrelated thing”, that’s perfectly fine so long as when you push the unrelated things are in separate commit. Get familiar with git add -i and/or git add -p. And of course your team likely has requirements about things being committed under the correct topic branch and stuff. Those are good rules to follow as well.)

Hopefully you’re getting what I mean by “source control is not a backup solution” at this point. Source control is for collaboration.

Personally, if I’m working on code that nobody but me is expected to touch anytime soon, I don’t put it in Git. The source control I use is called “a directory”. If I need to keep previous versions of the codebase, I copy the whole codebase into another directory. To protect against hard drive failure, I back it up to off-site storage.

I put it in Git when I publish it. Whether that be publishing to the world under a FOSS license or publishing it to my dev team at work in the central Git hosting solution we have where I work.

Google sitting over there just like “sux to be you, dude”.

I think I’ve seen this horror movie.

The ZideX printer isn’t quite what you’re talking about, but it kinda has the same idea.

Here’s a video about how to build one that will give you more of an idea what it looks like and how it works.

The Java logging library “SLF4J” works basically this way. It’s a “broker” sort of library. You use the SLF4J API to log and there are different backend implementations that can tie your logging statements to an actual logging backend. So you can do things like switching backends without changing code or using one backend (say, to STDOUT) in local and a different one (Syslog, maybe) in prod.

I suspect most developers have a “favorite language” and are just going to respond with “the import style my favorite language uses”.

I’m going to have to go on some remote interviews sometime soon. I don’t know if Zoom is the way those are usually done or if they use some other software that’s more purpose-built for that. But whatever the case, I’ll definitely have to figure out how to run whatever it is “in jail” somehow.

Model collapse is finally landing.

For real. Some guy I knew introduced me to SuSE back when I was in highschool. It was great and all, but it made things easy by hiding details behind snappy GUIs. While I was in college, I started to realize I wasn’t learning anything about Linux. So I took a deep breath and installed Gentoo. Switched to Arch for a while, but I’m back to Gentoo now. I wanted to learn more about how Linux really worked and holy shit did I get my wish.

Good riddance.

What I’d love to see even more than that is some kind of pigment cartridge system. You’d use natural, unpigmented filament and the printer would inject pigment in different mixtures as it prints. Just seems… I dunno. More efficient?

I remember seeing a YouTube video (that I might search for and find again if I remember) where some company had developed (and probably patented) an approach that involved inkjet-coloring as it printed. I remember the colors looked pretty pale and washed-out looking. Not vibrant the way I would have hoped. But the approach might be one that could be improved on. 🤷

Took me a while to even figure out vaguely what you were talking about here. I use DuckDuckGo exclusively for search. (And I use DuckDuckGo for search mostly because they let me turn off LLM BS.) I wasn’t aware they offered a browser. (I assume what you’re talking about is the DuckDuckGo browser/app, right? Not, say, search or LLM services or whatever.)

When you say “browsing and tracking through my apps”, what do you mean exactly? Did you have the impression that having the DuckDuckGo browser installed on your phone will prevent other apps from tracking you somehow? Or are you saying that by using the webapp of whatever particular service through the DuckDuckGo browser rather than an official app, you avoid tracking built into the app? (If that’s what you’re saying it at least sounds plausible. But if you’re thinking having DuckDuckGo on your phone will prevent, say, Google Play from tracking you (assuming Google Play is installed on your phone), I can’t see how that could be the case. But I also wouldn’t think DuckDuckGo would make the claim that it would. Unless you and DuckDuckGo know something I don’t.) Or when you say “browsing and tracking through my apps” do you really mean web trackers? (Or maybe apps can interact with web stuff through the browser in ways that I’m not thinking of.)

I guess what I’m asking is what specifically is the privacy claim related to DuckDuckGo that you’re asking the veracity of?

Whatever the case, it’s entirely possible that the particular claim you’re asking about isn’t true, but that it’s also not a claim that DuckDuckGo makes nor that they’d expect people to think about their products and so isn’t any particular reason for your coworker to dunk on DuckDuckGo.

I’ve been playing a Gamecube game (Spiderman 2 (2004)) on original hardware lately (slight lie - playing on a backwards-compatible Wii, but with an official Nintendo Gamecube controller) and the analogue L/R are quite annoying. Given that the analogueness doesn’t do anything in the game I’m playing unless you fully press it, it’s more like a non-analogue trigger with a ridiculous depression distance.

It’s the best Democrats can hope for in Missour-uh.