If there were comments for each conditional, it should still be refactored as
return a || b // comment 1
|| c // comment 2
// long comment 3
// on multiple lines
|| d;
Many years ago, "lines of code" was the classic example of nonsense management metrics. Today, there are somehow HN users who argue that lines of code is indeed a good metric and ask "But what if the code had comments?" as if they have never seen comments interleaved with code.
> In that case, it may be better in its expanded form, and you should let an optimizing compiler do the collapsing.
This is nonsense. This optimization is not about compiler optimization for efficiency. It's an optimization for human readability and maintainability.
The decline of the US government is the faster than "Europe", because it's been declining rapidly in a few months. The US government currently has a monthly quota for ICE arrests. ICE agents racially profile people and ignore non-white people telling them they are US citizens because they assume they are lying. Non-white US citizens need to have papers on them that prove their status (US citizen), or else might be disappeared. The US government now bans immigrants from a list of dark skin countries but fast-tracks White South Africans for immigration. It politically persecutes their political opponents and ignores the rule of law. It is preparing for war with Venezuela, which would conveniently tie up US resources as Russia positions itself for entering Europe.
The UK is rapidly declining as a close second, but calling it "European" (especially when UK citizens see themselves as non-European) is just a lazy generalization.
Why would the Chinese government want to regularly launch cyber attacks against US infrastructure, except it's been happening for years? US security companies and governments have been defending against it for years and have even cataloged the state-sponsored attack groups.
I've been doing API development for over ten years and worked at different companies. Most PMs are not technical and it's the development team's job figure out the technical specifications for APIs we build. If you press the PMs, they will ask the engineering/development manager for the written technical requirements, and if the manager is not technical, they will assign it to the developers/engineers. Technical requirements for an API are really a system design question.
PMs wouldn't be able to ask the right questions. They have zero experience with developer experience (DevEx) and they only have experience with user experience (UX).
I believe they are arguing against vibe-coding categorically by pointing out that high-level programming languages are for human expression. It's a reductio ad absurdum against the logical conclusion that follows from vibe coding as a premise. If vibe coding is like a using a compiler, why not just translate English directly to machine code or lower level languages?
Software development jobs must be very diverse if even this anti-vibe-coding guy thinks AI coding definitely makes developers more productive.
In my work, the bigger bottleneck to productivity is that very few people can correctly articulate requirements. I work in backend, API development, which is completely different from fullstack development with backend development. If you ask PMs about backend requirements, they will dodge you, and if you ask front-end or web developers, they are waiting for you to provide them the API. The hardest part is understanding the requirements. It's not because of illiteracy. It's because software development is a lot more than coding and requires critical thinking to discover the requirements.
> And training is the main money sink, whereas inference is cheap.
False. Training happens once for a time period, but inference happens again and again every time users use the product. Inference is the main money sink.
"according to a report from Google, inference now accounts for nearly 60% of total energy use in their AI workloads. Meta revealed something even more striking: within their AI infrastructure, power is distributed in a 10:20:70 ratio among experimentation, training, and inference respectively, with inference taking the lion’s share."
It's not an argument by analogy. It's a reductio ad absurdum on the generalization that reality always lies in the middle but not always at the exact middle.
If there were comments for each conditional, it should still be refactored as
Many years ago, "lines of code" was the classic example of nonsense management metrics. Today, there are somehow HN users who argue that lines of code is indeed a good metric and ask "But what if the code had comments?" as if they have never seen comments interleaved with code.
> In that case, it may be better in its expanded form, and you should let an optimizing compiler do the collapsing.
This is nonsense. This optimization is not about compiler optimization for efficiency. It's an optimization for human readability and maintainability.