His post illustrates how many programming tasks have gone from problem solving to lego-brick programming, where library is piled upon library and each of them is incomplete and contains piles of bugs. What could possibly be wrong with that approach?
Just like Norvig, I don't claim that Python is bad per se or anything like that. All I've said is that it's painful to go from CL to Python in terms of the general features of the languages (not their tooling). If you have never done this transition, have never programmed sufficiently large programs in CL and Python, please don't comment on it.
Compared to problem solving which doesn't use "lego bricks" and re-makes the wheel?
And instead of a factory making it to recognized standards across that class of vehicle, it's an ad-hoc design for a particular vehicle.
Often it's also square.
As a programmer with full experience in both languages, I agree with this in 200%.