@GergelyOrosz: Situation 1: dev A thinks approach X is correct, dev B thinks Y is the right way. They argue and try to convince each o…
Summary
A tweet discussing how developer debates over correct approaches provide learning that is lost when using LLMs to implement code directly.
View Cached Full Text
Cached at: 05/19/26, 02:48 PM
Situation 1: dev A thinks approach X is correct, dev B thinks Y is the right way. They argue and try to convince each other.
Situation 2: dev A thinks approach X is correct, tells the LLM to implement it.
There is SO MUCH learning in Situation 1, lost when using LLMs….
Similar Articles
@GergelyOrosz: Knowing how LLM contexts work and how to work around context limitations – aka “context engineering” – is becoming so i…
Gergely Orosz tweets about a podcast with Dex Horthy on LLM context engineering, covering lessons like the dangers of shipping unread code and recognizing when an LLM session is trajectory-poisoned.
Ask HN: Is anyone experimenting with different ways of using LLMs for coding?
A Hacker News user asks the community about experimental approaches to using LLMs for coding, expressing frustration with current prompt-response loops and seeking fundamentally different methods.
@bcherny: LLMs still produce bugs, but those bugs are different than what they used to be. It’s less off-by-ones and more about s…
A developer observes that LLM-generated bugs have shifted from off-by-one errors to higher-level design and context issues, and recommends using adversarial code review (e.g., Claude's /code-review) to catch them.
@msimoni: How much control are you exercising over the LLM when you're writing, in the parlance of our times, load-bearing import…
A tweet musing on the degree of control developers exercise over LLMs when writing critical code, proposing a scale from 'vibing' to meticulous design.
Born Against, or why hobby programming communities are aggressively against LLM usage
A blog post reflecting on why hobby programming communities like OSDev and demoscene are hostile to LLM usage, arguing that the craft and learning process itself is the point.