

This sounds extremely elitist, even when I agree with the words that you wrote. 😅
Microsoft just doesn’t need to innovate, because they already hold a monopoly. If they do innovate, it’s something their investors care about, not their users…


This sounds extremely elitist, even when I agree with the words that you wrote. 😅
Microsoft just doesn’t need to innovate, because they already hold a monopoly. If they do innovate, it’s something their investors care about, not their users…
Yeah, this is probably going to sound like a truism, but to avoid shitty Scrum, you need to resist management trying to alter the processes, but you should absolutely tweak the processes to account for the needs of the devs.
Basically, yet another reporting meeting does not help deliver the software faster. But more (or less) meetings for devs to sync what they’re working on, that can help, depending on your team’s specific needs.


Global push-to-talk is going to be wild for meetings. In the gazillion years when my work laptop finally ships an up-to-date version of Plasma, that is. Still on 5.27. 🫠
I’m guessing, you mean this then: https://github.com/edc/bass
But well, I was rather thinking of when it’s using Bash-scripting-syntax to combine multiple commands.
Like, maybe there’s a for-loop in there. You just can’t paste that directly into Fish and have it work. Granted, you should probably put that into a script file, even if you’re using Bash, but yeah, just temporarily launching bash is also an option.
I have that occasionally when I want to copy a complex bash command from somewhere. But yeah, I can then just run bash, run the command in there and then exit back out of there.
It still gives you basically no advantage compared to just making your terminal emulator launch fish by default. And well, it does give you the major disadvantage that scripts without shebang will fail.
To me, it genuinely makes a huge difference that I don’t have to manually press Ctrl+R for history search. Because 9 times out of 10, I accept a history suggestion from Fish where I did not think about whether it would be in my history.
This includes really mundane commands, like cd some/deeply/nested/path/. You would not believe, how often I want to cd into the same directory.
But I’ve also had it where I started typing a complicated docker run command and Fish suggests the exact command I want to write, because apparently I already ran that exact command months ago and simply forgot.


Where I typically notice it, is that the text starts repeating a few handful of points.
The prompt will have been to write a story on those points, and because it doesn’t have much else to go off of, it will just shoehorn those exact points again and again.
I expect this to always be a telltale sign, because if your point can be made in the length of the prompt, there’s a rather limited amount of noise it can add to that before it would have to go off-script.


Yeah, they’re really dropping the ball here on the important stuff…


A bit like this, unfortunately: https://en.wikipedia.org/wiki/Dead_Internet_theory
LLMs have made that conspiracy theory quite realistic…


F-Droid blog post on the topic: https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html
It was posted before Google backpedalled somewhat, if I remember correctly.
Polydimethylsiloxane (PDMS) is the active ingredient in most fabric softeners. However, PDMS is a silicone oil that destroys absorbent properties.
The oil in the fabric softener latches on to clothing and creates a coating. Towels absorb water, but oil repels it. When an oil coating attaches to a towel, it causes the fibers to become greasy and slippery, which hinders its absorbency. When the soapy residue of fabric softener builds up on the towel, it causes it to become stiff instead of soft.
Source: https://www.towelsupercenter.com/blog/should-you-wash-towels-with-fabric-softener/
Yeah, the latter is certainly a big part of it. The way to make it compile-safe is to use macros to generate code, so that my users can write e.g. Package::my_frontend.version and that gives them the version of their frontend package.
Writing such macros, i.e. writing code to generate code, is certainly something I haven’t done a ton of yet, because you practically cannot justify doing that in an application codebase, only in a library, so it is new stuff that I learn.
But well, you did already call it a “nice abstraction”, which is another big part where my excitement comes from and where I think, the special nerdery is necessary.
Others might build projects which are visually tangible, like a sexy GUI, or which do something tangible, for example a colleague (who I will absolutely not deny his own special nerdery) is currently building a driver for a motor. If that driver works, you can see a motor moving in the real-world. Even non-nerds can at least tell that something is happening.
But with my project, my success is that you can write Package::my_frontend instead of Package::from_str("my_frontend")?. And that if you rename the package to super_duper_frontend, that the compiler will tell you to fix the code rather than it only breaking once you actually run the build code for the frontend.
No chance of explaining to non-coders why this is exciting or even just when you’re successful.
On Monday, one of our students at $DAYJOB asked me what projects I do in my freetime. After I infodumped on her for half an hour, she asked in disbelief “And you do these in your freetime, without being paid?”.
Like, mate, did you not listen how feckin’ excited I got just then? Of course, I do these in my freetime.
To be fair, though, the last project I told her about is very dry. It’s a library to help automate CI builds. And the thing I’m thrilled to build is a compile-safe API for accessing the packages in your workspaces. Like, yeah, it does take a special kind of nerd to get excited about that…
Pretty sure, people drawing for commissions would typically use a drawing tablet… ^^’
I mean, Rust does have a pretty inclusive community…
Ah, I think, I know what you mean, that the format is supposed to be written with foolish oversimplifications that are borderline incorrect, whereas “secured by TLS” just sounds like a normal statement from an expert…
I’m guessing that was supposed to be “secured by a thin layer of TLS”…
No worries, I did not get you wrong. I commented, because I (rightly) assumed that you care to not sound elitist.
I think, a big part of the problem is that saying one choice is superior kind of implies in itself that people who don’t make this same choice are not the smartest.
Obviously, in reality there is a lot of other factors, like inertia (you don’t have to be stupid to not want to learn a different system) and well, the system being separate from the ecosystem (all the light/dark mode features won’t convince someone to switch who strictly needs an application that won’t run on Linux).
But yeah, if people don’t pick up on this nuance or don’t give you the benefit of the doubt, that just is likely to sound elitist to them… 🫠