hodwik
Joined 12 years ago
Joined 12 years ago
Support still gets done, because when you hire you specifically hire people who love doing support. Those people exist, and they get tremendously emotionally involved in the quality of their work, just like anyone else.
In every department there are people who struggle with the flat hierarchy and free range to work on what you like, who have a strong emotional need to know who is in charge, and to be told what needs doing. Those people struggle, but they are by no means relegated to any one department -- plenty of them are engineers.
Does anyone have any idea why that might be the case?
Using classes != OO.
Generally, Python programmers treat objects as structs with associated methods, basically the Go model. Python programmers rarely encapsulate at all. At best, they use a bunch of accessors (which is not itself OO). Implementation details are rarely hidden.
That's because dynamically-typed languages, the interpreter, and the Python culture, lend themselves more to exploratory programming, rather than a UML-design, with objects that relate to real-world entities, that are implemented after careful planning.
If you can show me a Python program where objects are really encapsulated, and aren't chock-full of accessors, I'll stand happily corrected.
For those of us who believe economic inequality is both good and natural, this is a great rhetorical device for undermining the left -- "in this time of great economic inequality, life is better than it has ever been for the general populace."
A person on the left may use the opposite rhetorical device, "in this time of great economic freedom, people are increasingly poor."
As this is written, there is no way to know which rhetorical device they were using.
As for the infrastructure, that's a rather more esoteric concern. It needs a distinguishing term.