Järlström was fined for using the title "engineer" unlawfully, not for his ideas being wrong.
448 karma · joined December 15, 2020
There are really two observations here: 1. AI hasn't commoditized skilled labor. 2. AI is diluting/degrading media culture.
For the first, I'm waiting for more data, e.g. from the BLS. For the second, I think a new category of media has emerged. It lands somewhere near chiptune and deep-fried memes.
https://www.slater.dev/about-that-gig-fixing-vibe-code-slop/
Low confidence to change it, low internal and external quality.
Also some differences: low age-to-quantity ratio, schedule pressure, inflated expectations.
It's most cost-effective to shift errors from runtime to compile time and from compile time to design time.
Unfortunately, AI rushes people to runtime as fast as possible.
Study an audience for their pains and worldview and what they buy. Earn their trust through writing and freebies. Then they will want to buy because it's from you specifically.
I can recommend https://30x500.com/
> AI now lets anyone write software, but it has limits. People will call upon software practitioners to fix their AI-generated code.
https://www.slater.dev/about-that-gig-fixing-vibe-code-slop/
By the author's implied definition of compiler, a human is also a compiler. (Coffee in, code out, so the saying goes.)
But code is distinct from design, and unlike compilers, humans are synthesizers of design. LLMs let you spend more time as system architect instead of code monkey.
I've seen it happen more than a few times that when software needs to get made quickly, a crack team is assembled and Agile ceremonies and other bureaucratic decision processes are bypassed.
Are there general principles for when process is helpful and when it's not?
Is this your firm's investment thesis?
The Programmer's Brain: What every programmer needs to know about cognition. By Felienne Hermans
If Trump were a software developer, he would commit directly to main
Love your neighbor as yourself.
I worked in WPF for a decade. I wouldn't go with it for a new project since it's Windows-only and doesn't support AOT.
At work we have a Blazor MAUI hybrid desktop app because it also has to run on the web. If we only needed a desktop app, I'd go with Avalonia.
[1] https://linklever.net/ [2] https://github.com/endurabyte/FitEdit
I thought about mentioning AOT and trimming, but my comment was already long.
AOT in ASP.NET is still a moonshot in most cases, and a non-starter in existing web apps due to dependencies not supporting AOT.
Worth mentioning that as of .NET 9 AOT is not supported on Android.
Joking aside, I do agree that ASP.NET Core is a behemoth. On .NET 9, I just now did `dotnet new webapi` followed by `dotnet publish --self-contained -p:PublishSingleFile=true` and the binary is 103MB. That would blow up the size of a mobile app considerably, just to listen to HTTP.
There a separate use case that SimpleW won't solve: When you're on a platform that .NET Core doesn't support, like Raspberry Pi Zero (armv7l). In this case all you have is the mono framework and binding to raw ports.
> LLMs as they currently exist cannot master a theory, design, or mental construct because they don't remember beyond their context window. Only humans can can gain and retain program theory.
Compare to Torvalds. You may or may not like his leadership, but nobody feels sour about his salary.
$ curl https://example.com -vI --stderr - | grep "expire date"
* expire date: Jan 15 23:59:59 2026 GMTAn LLM said it, so it must be true.
There was a joke that made its rounds here round about the time Queen Elizabeth died:
> Bob: "The queen's dead"
> Alice: "Dolly?!"
If you ride the train, be prepared for soot to get in your eyes.
I'm sure Dolly would be tickled silly to know a bunch of computer people were talking about her.
I think one shortfall of LLMs is their reluctance to ask clarifying questions. From my own post [1]:
> LLMs are poor communicators, so you have to make up the difference. Unlike a talented direct report, LLMs don't yet seem generally able to ask the question-behind-the-question or to infer a larger context behind a prompt, or even ask for clarification.