ハセン حسن@hasen_95dx
This sounds true if you are highly expeienced and proficient at systems level programming, like George Hotz or Jonathan Blow.
Most people are not.
For most people, the limiting factor *is* the code.
Not typing it, but figuring out what to type in the first place.
You may know the theoretical solution to a problem, but getting it to actually happen requires solving many sub-problems that most people are not capable of, either because they lack the mental capacity to handle it, or for lack of practice.
Managing complexity only comes to play when you actually have a system that is large enough where complexity actually becomes an issue.
Most programmers never reach that level, yet LARP into "managing complexity" with their towers of abstractions based "architecture".
The sub-tweet is obviously about AI progrmaming, so I will give my take on that:
* AI is not for writing the code you already know how to write; it's for writing code you _don't know_ how to write.
* You can still manage complexity without reviewing every single line of code: just manage system architecture and boundaries between sub-systems.
It's not easy per se, and, to concede a point, you probably cannot acquire the "taste" for where to draw boundaries without having spent a long amount of time hand coding a semi-complex system from scratch by yourself.