Yeah, and all because god forbid you give your (future) employees time to learn another language besides JavaScript. Nope, line must go up so programming must be further commodified.

Why is it so hard to accept that not everybody can stay awake while reading a scientific article?

I’m a PhD researcher and even I struggle staying awake sometimes.

No seriously, I fully agree, scientific articles are written for a specific, niche audience, i.e. not the general public. But science should be communicated to the public, in as accessible a format as possible. If you fail to do that, you get people saying “science is boring”, or worse, mistrust of science like it exists today.

And another thing: this shouldn’t be either-or between watching a video and reading an article. Watch the video, get a general understanding of the topic, see if it interests you. If you want to know more, dive into the article to deepen that understanding. I guarantee you’ll get a better understanding that way, because watching the video has already given you a general structure of the topic. Reading then serves to add details in that structure.

Seems like it’s mostly error handling, which makes total sense to me. In a function with a lot of error conditions, where it also takes more than return <nonzero value> to report that error, the code would get very cluttered if you handle the errors inline. Using goto in that case makes the normal case shorter and more readable, and if proper labels are used, it also becomes clear what happens in each error case.

Sure, you can do that with functions too, but it’s much nicer staying in the same scope where the error occurred when reporting on it. Putting things in a function means thinking about what to pass, and presents extra resistance when you want to report extra info, because you have to change the function signature, etc.

It’s not even the original spare I think. If you look at the middle brake light there’s way too much room.

Not unless you choose really slow hard drives, or stream very high bitrate media. Most hard drives can easily do 100MB/s sequentially (i.e. reading a large file, such as long video files). Meanwhile high-bitrate 4K video is only about 50Mbit/s, so about 6MB/s.

I agree with the overall sentiment, but I’d like to add two points:

1. Everyone starts off as a code editor, and through a combination of (self-)education and experience can become a software engineer.

2. To the point of code editors having to worry about LLM’s taking their job, I agree, but I don’t think it will be as over the top as people literally being replaced by “AI agents”. Rather I think it will be a combination of code editors becoming more productive through use of LLMs, decreasing the demand for code editors, and lay people (i.e. almost no code skills) being able to do more through LLMs applied in the right places, like some website builders are doing now.

C on Morello (or any other capability machine).

And they force you to use it if you want autosave, which is essential in a work environment given the stability of MS Office programs (or at least my ability to crash Excel).