Show newer

god anything involving quadcopters that isn't flying is such a pain in the ass

Show thread

🦆 how to factory reset device

> buy a new $device if you want it reset to factory defaults

i really gotta fix my fucking quadcopter(s), it's been too long

(White) guy in Teams chat just said “hakuna matata” and it’s taking all my strength not to reply “Hatsune Miku”

every time i wear the 36c3 RESOURCE EXHAUSTION t-shirt i'm like big fuckin mood

finally joined the Dungeons and Daddies (not a bdsm podcast) patreon and now i have so much extra content to binge through

Even if only half the people loudly complaining about software performance and efficiency actually did the work of "understanding where the performance issues come from", things would be so much better right now

food 

mmm not sure what to get for dinner

#NixOS people are serious about testing :flan_ooh:

Their testing automation is impressive! :flan_hearts:

Firefix is tested by opening a page (from valgrind man page), playing some sound, verifying some sound is played, closing a tab, display the developer tools. If anything fail, then the test fails

github.com/NixOS/nixpkgs/blob/

Openarena (Quake 3 open source reimplementation) is tested by running a server, connecting two players, verifying the clients connect to the server

github.com/NixOS/nixpkgs/blob/

Minecraft client is tested by running the client in a VM and use OCR to detect if it asks for creating an account

github.com/NixOS/nixpkgs/blob/

software development, politics adjacent, long 

Potentially controversial opinion: I think that "making software more efficient" is the wrong thing to focus on right now.

There's a significant kernel of truth to the idea that "it's easy to make good code performant, but it's hard to make performant code good" - and so before going all-in on optimizing code as the primary objective, we should make sure that we're optimizing the right thing.

And right now, we're not. We're very much not.

There are significant problems to be solved in how we address software development, and the power dynamics embedded into it - the most obvious example would be the still-widespread fear of dependencies, which actively interferes with making software work better for people, and results in an endless treadmill of broken shit.

And guess what, there *are* significant efficiency benefits to be gained here - everybody using the same well-optimized implementation is going to be much better than everybody using their own homegrown half-optimized "clever" implementation.

But by putting all the focus on software efficiency and performance as the #1 priority, we risk removing all the oxygen in the room for figuring out better ways to deal with dependencies and many of the other industry-wide problems I haven't even mentioned here yet, and ending up in a *worse* place (even efficiency-wise!) than where we *could* be if we started with other problems first.

TL;DR: software efficiency and performance is important, but if you treat it as a goal to chase directly, you will end up with broken and faux-simple software that isn't even as efficient as it could be. Fix the big problems with software first, *then* think about how to optimize the remainder.

photos I took turned out quite well, the Rollei 135mm f/2.8 was a great choice even if I had to stand a mile away

Show thread
Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.