>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?
Compared to problem solving which doesn't use "lego bricks" and re-makes the wheel?
Someone must have been going against best practices and remaking the wheel because I see different types of wheels everywhere I look. Shopping carts have a certain type of wheel, skateboards have a certain type of wheel, longboards have a certain type of wheel, rollerblades have a certain type of wheel, bikes have a certain type of wheel, planes have a certain type of wheel, cars, trucks, RC vehicles, toys, etc, etc, etc, etc...
In programming, the wheel gets remade multiple times for the same category of vehicle (e.g. skateboard).
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.
Brick-related xkcd: https://xkcd.com/1988/
Haha! The modern developer, right there!
> 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).
As a programmer with full experience in both languages, I agree with this in 200%.
Re:Python for Lisp Programmers (2000)
by nothrabannosir on Monday May 21, 2018 @06:20AM
(#17117305)
Please don’t swear. Please. There are no victories down this spiral. Only barren soil.
Re:Python for Lisp Programmers (2000)
by jonathanstrange on Monday May 21, 2018 @06:47AM
(#17117402)
I'm sorry, I honestly didn't realize that this counts as an instance of swearing in certain language communities. My apologies!
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.