The thing is I think there will come a time when AI tools will not be as accessible as they are now. I just don't know if it is in 3 years or more, because the

The thing is I think there will come a time when AI tools will not be as accessible as they are now. I just don't know if it is in 3 years or more, because the market can stay irrational longer than I can foresee. I saw this idea from elsewhere that the things AI helps with was never the "profit bottleneck" of companies. 10x engineering productivity gain does not translate to 10x more revenue if your profit bottleneck is customer acquisition and retention. In other words, your profit is limited by how many people are willing to give you money for your services and AI can't really affect that. And even the productivity gains per individual is a generous assumption. An individual can only prompt (and check! You guys check right?) so much. Sooner or later the pendulum is gonna swing in the other direction and it will be cheaper to build a team than equip individuals with AI _to deliver the same value_. I'm also assuming that AI is still in the VC-subsidized pricing stage. Hence why I think the job in the future is gonna be pretty similar to the job four years ago. > The next most important skill is persistence ;) -- writing stuff down before you forget it, in a way that won't make future-you hate present-you when you need to learn it again. Huge amen. Another thing I've found Claude very useful for is writing documentation for legacy systems and cleaning up my own notes on it. I only need Claude to be 70-80% correct because from there I can take it. That error margin is no different from moderately-outdated-but-still-useful documentation. When that pendulum swings, I will have a documentation binder that I will print money with.