it's not just a war of capabilities but a war of UXes. Is an 'AI Engineer' going to be an extension of an IDE (that autocompletes your routine or LOC like Cursor) or a 'digital employee' that autocompletes and auto-tests your thought (like Devin). Melty seems to be going down the Cursor route.
As an old-fashioned 'emacs and print out' guy, I prefer Devin type planner interfaces .. iff they can perform. Not quite yet.
Isn't the problem the context window. If the entire project could be slurped by AI and then the thing current task after it, would it then become feasible?
2 comments
[ 3.0 ms ] story [ 19.1 ms ] threadAs an old-fashioned 'emacs and print out' guy, I prefer Devin type planner interfaces .. iff they can perform. Not quite yet.