The conversation

Lessons learnedExperience excerpt · English

Interacting with Claude Code felt like an actual collaboration with a fellow engineer

… Interacting with Claude Code felt like an actual collaboration with a fellow engineer. People like to compare it to working with a “junior” engineer, and I think that’s broadly accurate: it will do whatever you tell it to do, it’s eager to please, it’s overconfident, it’s quick to apologize and praise you for being “absolutely right” when you point out a mistake it made, and so on. I don't know what "fellow engineers" the author is accustomed to collaborating with, junior or otherwise, but the attributes enumerated above are those of a sycophant and not any engineer I have worked with. Finally, the author asserts: I’m sure that if I really wanted to, I could have done this modernization effort on my own. But that would have required me to learn kernel development as it was done 25 years ago. This could also be described as "understanding the legacy solution and what needs to be done" when the expressed goal identified in the article title is: ... modernize a 25-year-old kernel driver Another key activity identified as a benefit to avoid in the above quote is: ... …

Original discussionUsing Claude Code to modernize a 25-year-old kernel driver318 source comments · at import
4

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 4

Direct replies available in this import. Original-language excerpts.

RM

Gatekeeping is toxic. I love agents explaining me projects I don‘t know. Recently I cloned sources of Firefox and asked qwen-code (tool not significant) about the AI features of Firefox and how it‘s implemented. Learning has become awesome.

Full original
BA

> Another key activity identified as a benefit to avoid in the above quote is: ... required me to learn ... "...kernel development as it was done 25 years ago." Not "...kernel development as it is done today". That "25 years ago" is important and one might be interested in the latter but not in the former.

Full original
RG

> I don't know what "fellow engineers" the author is accustomed to collaborating with, junior or otherwise, but the attributes enumerated above are those of a sycophant and not any engineer I have worked with. I read "junior" as 'subordinate' and 'lacking in discernment'.. -- Sycophancy is a good description. I also like "bullshit" (as in 'for the purpose of convincing'). https://en.wikipedia.org/wiki/Bullshit#In_the_philosophy_of_... The point being, there's nuance to "it felt like a collaboration with another developer (some caveats apply)". -- It's not a straightforward hype of "LLM is perfect for everything", nor is it so simple as "LLM has imperfections, it's not worth using". > Another key activity identified as a benefit to avoid in the above quote is: > > ... required me to learn ... It would be bad to avoid learning fundamentals, or things which will be useful later. But, it's …

Full original
KE

To be fair, a "baseline knowledge of the internals of a kernel module" is not that difficult to acquire. I think a moderately-skilled developer with experience in C could have done this, with Claude's help, even if they had little or no experience with the Linux kernel. It would probably take longer to do, and debugging would be harder, but it would still be doable.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.