It's about practicing how to read and write. Skills that you'll benefit from in every form of knowledge work that you'll ever do.

I would cut almost every other class from the curriculum before cutting English.

That bears little resemblance to the Signal concerns. The reason people are worried about losing their personal messages is not lost productivity.

It's also not even really the same situation. A more apt analogy would be, if switching work laptops sometimes meant you could no longer read any Slack history.

Epic's fee for 3rd-party payments is 0%.

12% is if you sell directly through Epic's platform - nobody is claiming Apple shouldn't get a cut of that for their own platform.

ah, a classic TORTOF bug (time-of-ray, time-of-flip)

The entire thing literally reads like an Onion piece. If I'd read this exact article in The Onion I would've considered it brilliant comedy.

It's becoming increasingly hard to distinguish an Onion article from actual media. Post-truth indeed.

That's sensible, but I think default styles for specific elements are not part of the CSS standard, and are instead dictated by the user-agent stylesheet of your browser.

Great site!

I tend to advocate for people to study design patterns. Not for the purpose that you will necessarily ever use most (or even any) of these exact patterns in your software, but just that you've strengthened your mental muscle for software design in general. I encounter lots of engineers who simply aren't able to think "outside the box" when building something new.

I always wondered if people actually find it beneficial to follow these "design patterns" or not.

Personally, I prefer to learn FP patterns, which tend to be backed with nice mathematical properties behind them.

Your confusion seems to stem from the assumption that, making a statement is an implicit assertion that most people believe the opposite of that statement.

In reality, statements are often made rather for the purpose of emphasis or rhetoric.

That's a good point, and something I'll have to remember for the future, but I'm curious what the emphasis or rhetoric of GP comment would be.

> if vibe coding is the future of software development (and it is), then why bother with languages that were designed for people who are not vibe coding? Shouldn’t there be such a thing as a “vibe-oriented programming language?” VOP.

A language designed for vibe coding could certainly be useful, but what that means is the opposite of what the author thinks that means.

The author thinks that such a language wouldn't need to have lots of high-level features and structure, since those are things that exist for human comprehension.

But actually, the opposite is true. If you're designing a language for LLMs, the language should be extremely strict and wordy and inconvenient and verbose. You should have to organize your code in a certain way, and be forced to check every condition, catch every error, consider every edge case, or the code won't compile.

Such a language would aggravate a human, but a machine wouldn't care. And LLMs would benefit from the rigidness, as it would help prevent any confusion or hallucination from causing bugs in the finished software.

Sounds like Ada. A lot of the time, once you got your code to compile, it would work.

What about Lean?

I don't think there is a need for an output language here at all, the LLM can read and write bits into executables directly to flip transistors on and off. The real question is how the input language (i.e. prompts) look like. There is still a need for humans to describe concepts for the machine to code into the executable, because humans are the consumers of these systems.

> the LLM can read and write bits into executables directly to flip transistors on and off

No, that's the problem (same misconception the author has) - it can't. At least not reliably. If you give an LLM free rein with a non-memory safe output format, it will make the exact same mistakes a human would.

The point of a verbose language is to create extensive guardrails. Which the LLM won't be annoyed by, unlike a human developer.

"Networking", in the abstract, can be good for finding a job. As they say, it's who you know not what you know.

That being said, industry networking events, like conferences and such, are almost not at all useful for that purpose. In my experience they're mostly used for B2B sales (which is a kind of networking, I guess).

That’s still networking. Companies often have referral bonuses for open positions so if a lot of salespeople know you, when there’s a referral bonus available they might just put your name in. It’s something.