我创建了我的第一个AI辅助的拉取请求,并且感觉像个冒牌货。
I created my first AI-assisted pull request

原始链接: https://nelson.cloud/i-created-my-first-ai-assisted-pull-request-and-i-feel-like-a-fraud/

作者最近向 Hugo 项目(Chroma 语法高亮器)提交了第一个 AI 辅助的拉取请求,使用 Claude Code 添加了 ERB 语法高亮。尽管 PR 已经通过并合并,但这次经历让他们感到像个冒牌货,加剧了冒名顶替综合症。 作者承认 AI 让他们能够做出原本可能因为精神疲惫和复杂性而无法完成的贡献,但他们觉得这个过程缺乏乐趣——将其比作外包了一个个人挑战。这种感觉也延伸到工作中,即使 AI 驱动的交付成果产生了积极影响,也让他们感到“空虚”。 作者担心这是一种更广泛的行业趋势,它激励速度而非工艺,并随着 AI 成为绩效评估的组成部分,加深了不安全感。当 AI 能够在没有相同奉献精神去理解和保证质量的情况下产生结果时,他们质疑自己技能和作为工程师的身份的价值。最终,他们正在努力解决股东优先事项与他们作为开发人员所持有的价值观之间的脱节。

## AI辅助编程与“欺骗感”——摘要 一位程序员分享了他们创建第一个AI辅助拉取请求的经历,尽管成功贡献了一个新功能,却产生了一种令人惊讶的欺骗感。核心问题不在于工具本身,而是一种脱节感——在没有通常与成就相关的传统学习和努力的情况下获得了结果。 这场讨论引发了关于编程本质变化的更广泛的争论。许多评论者对此感同身受,强调了从*编写*代码到*指导*代码的转变。类比范围从电影制作到使用电动工具,强调利用AI并不会否定技能,而是改变了所需的*技能类型*。 一些回复建议将工作分为“快速且粗糙”的AI辅助任务和优先考虑个人工艺的领域。另一些人指出,目标是交付价值,不一定是要享受每一行代码。最终,这场对话揭示了人们对身份和目的的普遍焦虑,因为AI正在重塑程序员的角色,促使人们反思在新形势下成为一名“优秀”程序员意味着什么。
相关文章

原文

I created my first AI pull request for Chroma, which is the default syntax highlighter used in Hugo.

I used Claude Code for that PR. I didn’t learn anything. I felt like I was flinging slop over the wall to an open-source maintainer. I felt like a fraud and my impostor syndrome got worse.

But here’s the thing, I still contributed something of value. It’s something I have been wanting in hugo for a long time to syntax highlight ERB snippets in my posts. It was approved and merged by the maintainer (thanks for dealing with my slop, Alec).

It just feels odd. I know there are many people that are excited this new era of writing code. But to me this has sucked out all of the fun. I have never felt like a bigger fraud in this field. I’ve always thought that I’m privileged that I get to have fun at all in my line of work. As Ori Bernstein says: “using LLMs to write code is as fun as hiring a taskrabbit to solve my jigsaw puzzles”.

But then again, I know that realistically I would not have the mental capacity or skill to create a pull request like that without AI tooling. My brain is already fried from work on most days. I don’t think I would have been able to learn the codebase and get enough context to make that PR all by myself. It’s a lot. I just wanted some ERB syntax highlighting for my little blog.

Even at work I’ve used Claude Code and other AI tooling to deliver fixes and improvements that have real customer impact. But no matter how big the impact, I feel empty. I agree with Xe Iaso in the first sentence of their post: “Whenever I have Claude do something for me, I feel nothing about the results”.

Now that using AI is a normal expectation at work and how I’m evaluated in performance reviews, I suspect that this fraud feeling will only grow. The industry as a whole is incentivizing delivering code/features/fixes at a quick pace even if it’s all just slop.

I keep thinking a lot about how I perhaps tied my identity too much to my career. I’m not the greatest engineer, but I’ve always worked hard to deliver good work and learn as much as possible. I care a lot about understanding underlying systems as much as possible. I care about the craftsmanship of my code (to the best of my abilities). Unlike me, AI tools don’t care about any of these values.

At the end of the day, the shareholders care about delivering features, gaining customers, and making money. They don’t care how software is built.

I don’t know what to make of this.

联系我们 contact @ memedata.com