[kayo_20211030]

> Converting instructions to code is essential complexity

I don't agree with that. If I want to add two numbers I'd like to write `a = b + c`. I do not want to write the machine code that effects the same result on whatever computer architecture I'm targeting. Precisely _how_ one adds two numbers is accidental complexity. Whether they need to be added, and what numbers should be added, is essential complexity.

Fortran removed that accidental complexity and left the essential stuff in place. There were no fuzzy lines.

[conartist6]

Without a method for how to do the work you won't be able to do the work. Is that not the definition of essential?

But the way you've stated it, as long as you're pointing your microscope at one thing, that thing is "essential" and every other thing in the world is "inessential".

[kayo_20211030]

Yes, I think where we ought to point the microscope is important - that's the judgement. Let devs focus the microscope on the essential stuff, the business-existential stuff, and let the tools remove the burden of having to deal with anything that's not fundamental to the solution of the problem. The tools, now, are just not structured to make this problem easy. There's a lot of mixing of what's essential and accidental that becomes unmanageable quickly - spaghetti novo. It will be an interesting journey. It'll take humans and machines (directed by humans) to line up on an agreement on where the microscope should aim.