@radiatoryang @cmuratori Yeah I wish I would've been able to read this 10 years ago :)
-
-
-
@crypticsea@radiatoryang Me too :) Would have saved me, like, ten years :P
End of conversation
New conversation -
-
-
@cmuratori Encapsulation for maintaining invariants is a good thing, but it is not nearly as good as not needing it in the first place.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@cmuratori I love your write ups!! Thanks!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@cmuratori another OOP advantage for big teams: You can spend 80% of your typing on solving 5% of the problem. Typed code is measurable!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@cmuratori Wrote an editor once (Saints Row 1) and I gently disagree with your negative portrayal of OOP. I'll have to think a bit.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@cmuratori Liking these articles a lot.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@cmuratori Looks good for switching between behaviours that share state structure. If I'm adding a lot of unique variables, I'd use OOP. -
@mintman_ But why? Have you actually determined that you are gaining productivity from it, and if so, what is it? - Show replies
New conversation -
-
-
@cmuratori I don't think this is so damning of OOP, but just of blindly using it w/o cost vs. benefit considerations (in C++). Nice article! -
@RedRivetStudios Yes. Although, in general, pretty much every instance where people use OOP, I would choose non-OOP. - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.