> Code spitters are cooked, let's be honest here and accept the fate so everyone can move on.
I'm guessing "code spitters" here means people who consider their job to be manually writing code based on requirements produced by others.
Personally, I think the role of "developer" has already expanded way beyond that. If you're a technology expert who understands what is and is not possible to build, how it can be built, how to prompt that thing into existence, verify that the implementation is good, then get that implementation safely into production, you're not "cooked" at all.
> Code spitters are cooked, let's be honest here and accept the fate so everyone can move on.
I'm guessing "code spitters" here means people who consider their job to be manually writing code based on requirements produced by others.
Personally, I think the role of "developer" has already expanded way beyond that. If you're a technology expert who understands what is and is not possible to build, how it can be built, how to prompt that thing into existence, verify that the implementation is good, then get that implementation safely into production, you're not "cooked" at all.