I would love to know if and how you disagree. I am (I thought obviously) making a jump here from her desire to make FLOW-MATIC human-readable. Also, I don't believe that AI will take developers's jobs, but I do believe a developer using AI will replace ones not using it...so I'm intentionally provocative there, yes.
This will be another abstraction layer that MANY people will use and be able to accomplish things that would have been impossible to do in a reasonable amount of time in machine code.
but you're right that "I firmly believe that AI will not replace developers, but a developer using AI will replace a developer who does not." could have multiple other readings too.
Let's be fair - I made it intentionally a little provocative :)
Just as the developer who refused to adopt version control, IDEs, or Stack Overflow eventually became unemployable, those who reject tools that fundamentally expand their problem-solving capacity will find themselves unable to compete with those who can architect solutions across larger possibility spaces on smaller teams.
Will it be used for absolutely every problem? No - There are clearly places where humans are needed.
But rejecting the enormous impact this will have on the workforce is trading hype goggles for a bucket of sand.
Would love to chat about integrating the models into Kilo Code if you’re interested
You can contact me at brendan [at] kilocode [dot] ai