I'm with you. During most of my career, I was considered very technical and a good coder, but I never really loved the slowness of it. I enjoyed designing solutions but found "putting them into code" tiresome because for me the fun is in actually solving the problem.

But it's clear that many people feel otherwise. Software engineering has many classes of tasks and the difference in opinions about AI seem to exist because different people like different aspects of it.

▲

noufalibrahim 11 hours ago | parent [-]

Can you draw such a clear line? I put out some thing to experiment with an idea and then iterate over it till i get a solution and then spend time trying to polish that for production use. Thinking and coding are very rarely two separate states for me.

	▲	glimshe 11 hours ago \| parent [-]
		It's not that clear and still involves coding. But as I start coding and modules/APIs/classes take shape, it gets to a point where I say "ok, from here on it's just filling in the blanks". But filling in the blanks can still involve a lot of grindy, time consuming work where you iterate through collections, build parameters for other APIs, check invariants etc. All of that stuff is boring to me. What I'm trying to say is that most coding tasks require "senior level thinking" and "intern level thinking". The latter can sometimes be the majority of the work and I don't want to do that anymore.