Quite a few major issues with the post:

  - Drinking wine solo is odd. Whiskey, vodka, or beer (and if you Russian) is the standard. Spelling mistakes like 'ever thing' support the idea of alcohol induced unordered thoughts, that's good.
  - Webdevs would one of the last to consider to be experts.
  - While I don't use darkmode, browser extensions solve the unsupported web pages. Dark mode used to be the only possible option on a black/green screen, glad that changed.
  - Pharmacist require a degree and quite a few years of studies and exams with tons of organic chemistry. 
  - HN comments being worthless is an awkward one. Lots of posts (e.g. Apple CEO change) had tons of useless stuff but it's very often the comments would bve better than the post itself.

>Lots of posts (e.g. Apple CEO change) had tons of useless stuff

Funny to read from someone else who noticed :) maybe broad appeal of the topic had a big impact

POV you don't live anywhere near Sonoma.

your comment on drinks is odd.

Tongue-in-cheek

their comments on HN comments is funny as well in light of the original claim

It was about getting fired (your manager stuff) and then moving to another job very shortly afterwards (the two weeks is correct)

> "$PROJECT bans AI" is just ridiculous

why so? If they don't feel like reviewing code (or ensure copyright compliance) they are free to reject that.

If you feel strong about it, go fork and maintain it on your own.

>reviewed by humans can be perfectly good, maintainable, and indistinguishable from regular old code

That depends on the 'regular old code' but most stuff I have seen doesn't come close to 'maintainable'. The amount of cruft is proper.

Another good example of "the people writing good code with AI are the people who could have done it regardless"

Generally if I see 'this' to refer to some unknown part in any title, I'd consider it low quality.

Agreed, it's subtle but it's definitely a form of clickbait-style writing.

trucks? Or they still considered cars?

which part would you consider overengineered?

realistically the only part at half a gb/s I'd care is latency. Latency is a lot more important than the throughput.

I read the article before the abbreviate definition inclusion as its very opening. I had never met the abbreviation before.

It'd be quite surprising the WITH statement in top a query to be the first feature to learn/use past basic SQL. Is it personal experience in some industry?

According to the article that's what 25% of people think.