LogicIsTheEnemy

GettersAreEvil, but LogicIsTheEnemy.

I perceive a view of programming that says (conceptually), well, there's transistors and they get combined into gates and latches and such, and they get combined into registers and ALUs and such, and they are driven by micro-code and that gets driven by machine code and that gets macro expanded from assembler and that gets translated from RTL (or whatever) and that maybe came from some C generated by the middle layer of the compiler of the high level language I actually type into the editor. Different people have stacks that extend to different depths, and maybe ther'e a VM rather than a C layer, or whatever. But the general scheme seems quite widespread, or rather the symptom that I diagnose as being caused by this view, which is that programming is about logic. Specifically, about using logic to control the sequencing of combinatorial operations on bit patterns. This is the way C, and by syntactic inheritance Java encourage programmers to think.

Well, for certain domains, that's actually quite a good view to take. But for a lot more domains it isn't. As Edsger Dijkstra might have said, programming is no more about logic than mountaineering is about ropes.

But few climbers would say "ropes are the enemy". Niether is logic until it comes to predominate at the expense of a 'gestalt' or primary view.
Then you may get sucked in to the details of tying knots and miss the fact that you are going off route towards an unclimbable wall. --MilesD