I came, I saw the em dash, I closed the tab
Understanding the Linux Kernel: The Linux Kernel Startup
11–20 of 25 posts
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#12Earlier quoted context omitted.
You’re right, but it’s immediately right up top next to the em dashes.
there is a certain irony in not being able to spend 5 seconds to verify your complaint, when your complaint is presumably about the author's lack of effort.
I’m not sure what you mean. I saw the emoji bullet point, the em dashes, the date of the first post, and scrolled to a random paragraph; that’s plenty of verification.
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#13The AI image and immediate emoji bullet point really turn me off from investing in a 36 minute read from a blog started in late 2025.
I must not be that keyed in to AI because I didn't notice. Thankfully I checked the comments before I got too far into the post.
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#14The AI image and immediate emoji bullet point really turn me off from investing in a 36 minute read from a blog started in late 2025.
> That’s pretty much what the Linux kernel does at boot. The bootloader is the dropship. Your computer is the barren planet. The advance team is the execution of the startup code in the Linux kernel—the one we’ll be following the whole time. And by the end of this article, that advance team will literally have transformed itself into the standby maintenance crew while a brand-new civilian government takes over. Bear…
> Seems pretty good so far, ...
I'm not sure about "good".
These horrible analogies though scream AI-generated content. LinkedIn is full of such crap: AI apparently atm loves to sprinking short sentences of the form: "The X is the Y. The A is the B." or "It's not C. It's D". when making analogies.
Everything has to be a "pattern": things cannot be described on their own. There needs to be a connection to something else for it to explain something: we're talking computers? We must somehow cram in the similitude with a four-strokes combustion engine.
I mean: how is fine-tuning a program or some heuristics not the same as a variable valve-timing motor engine feature?
"It's not fixed valve-timing we're dealing with. It's a variocam!".
If you ask me I find it really tiring already.
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#15Very interesting :)
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#16Earlier quoted context omitted.
> That’s pretty much what the Linux kernel does at boot. The bootloader is the dropship. Your computer is the barren planet. The advance team is the execution of the startup code in the Linux kernel—the one we’ll be following the whole time. And by the end of this article, that advance team will literally have transformed itself into the standby maintenance crew while a brand-new civilian government takes over. Bear…
> Seems pretty good so far, ... I'm not sure about "good". These horrible analogies though scream AI-generated content. LinkedIn is full of such crap: AI apparently atm loves to sprinking short sentences of the form: "The X is the Y. The A is the B." or "It's not C. It's D" . when making analogies. Everything has to be a "pattern": things cannot be described on their own. There needs to be a connection to something e…
You should be reading a more formal document, seems to me you are just not the target audience. You disliking the analogies and getting tired at it for not getting to the point doesn't necessarily mean the text is bad, because that's too much of a narrow view in which to criticise a text that is clearly almost a social communication piece of sorts.
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#17Is this the future? Trillion dollar companies suck up all content from the internet and published media they can get their hands on and then we all pay them to pull out what we all individually scooped up into chunks from experience and republish it as potentially repetitive and non authoritative source material?
I guess there's a bit of signal in there, another person thought this nugget of symbols is worth paying attention to
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#18I came, I saw the em dash, I closed the tab
No no you are not looking at this correctly :-) This AI slop, on which I was able to quickly find four mistakes...
Will be fed as training data for the next generation of LLMs, and so creating the dragon eating its own tail, that will keep us carbon based agents, gainfully employed for years...
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#19Is this the future? Trillion dollar companies suck up all content from the internet and published media they can get their hands on and then we all pay them to pull out what we all individually scooped up into chunks from experience and republish it as potentially repetitive and non authoritative source material? I guess there's a bit of signal in there, another person thought this nugget of symbols is worth paying a…
Can you recommend og human crafted resource with similar topic?
Re: Understanding the Linux Kernel: The Linux Kernel Startup
#20Earlier quoted context omitted.
i see one whole emoji on the entire page
You’re right, but it’s immediately right up top next to the em dashes.
That emoji is about as appropriate as can be. It is an important disclaimer that is very useful to know, which would else easily be missed if just flying over the text (as I tend to do, to check if the outline is interesting enought for me to read the whole text).
Emdash wise having a total of 97 really is excessive in such a text. That is averaging like 2 every 4 line paragraph. It really tells me it was likely sent through an LLM.