toadpipe

8 ms·

1. 31.▲
   by toadpipe 17y ago

   If you think about it, this is basically outlining. You know, that thing your English teacher always bugged you to do because it would make your essays more coherent. If one insists on writing code before understanding the problem, this is
2. 32.▲
   by toadpipe 17y ago

   I note that every advantage of OOP you cite is a modularization feature (even subtyping, since OOP basically conflates modules with types). Clearly you are not entertained by rants based on my experiences, so maybe I should just cut 'n past
3. 33.▲
   by toadpipe 17y ago

   Really thoughtful article about balancing money with other things, purposelessness and self-discovery as a path to creativity, and creativity as a business strategy. All the things he talks about that relate to my experiences are dead on. I
4. 34.▲
   by toadpipe 17y ago

   It isn't because programming is too young, it's because programming is commercial. OOP retardation is new thing, it's not something we've been trying to do forever are are just now realizing is problematic. It was pushed by manager types wh
5. 35.▲
   by toadpipe 17y ago

   > OOP abstractions can sometimes be masochistic! You think? The article is a train wreck of analysis piled on the train wreck of "OO Design", which is itself a train wreck of an attempt to promote reuse by modeling code with data type