This is accurate, and you can make it more extreme in most cases today as: *build* your narrow-scope-dependencies, unless it is really a complicated stuff. In the second case, internalize it and specialize it.
大多数程序员会慢慢出现两类症状。
一是不想写代码。因为写的没有 AI 快,也写的没有 AI 好,编程将沦为普通人的玩具(架构和工程目前还不是),程序员容易找不到成就感。
二是不想指挥 AI 写代码。由于一的存在,加上指挥一个没有感情的机器,去做自己不认可的事情,会比自己亲自去做更难受。因为躬身事中,疲于处理一个又一个的问题,会忘记自己的存在;而看着 AI 在自己不认可的方向,持续接近目标,会无数次巩固自己的存在。“我是谁?我在干啥?”
程序员应该做的,就是摆脱自己会写代码的标签,慢慢朝着用户价值层做迁移,去做自己认可的、喜欢的事情,或者用自己认可的、喜欢的方式做事情。😃
Everybody is adding a feature where you can manage your agents from your phone. Don't use it. You'll just get even more addicted, and will burn out even quicker.
It seems that many large OSS projects have AI contribution policies, and you can see that their overall direction is consistent.
CMake
- Contributors are welcome to use AI...
- AI tools and services are not considered authors. They should not be listed as co-authors
Kubernetes Community
- Using AI tools to help write your PR is acceptable
- Listing AI tooling as a co-author, co-signing commits using an AI tool, or using the assisted-by, co-developed or similar commit trailer is not allowed.
https://t.co/bZoiJyPYf7
https://t.co/Bv6Seh6FJE
Wow, this tweet went very viral!
I wanted share a possibly slightly improved version of the tweet in an "idea file". The idea of the idea file is that in this era of LLM agents, there is less of a point/need of sharing the specific code/app, you just share the idea, then the other person's agent customizes & builds it for your specific needs.
So here's the idea in a gist format: https://t.co/NlAfEJjtJV
You can give this to your agent and it can build you your own LLM wiki and guide you on how to use it etc. It's intentionally kept a little bit abstract/vague because there are so many directions to take this in. And ofc, people can adjust the idea or contribute their own in the Discussion which is cool.