If things were working out with bad ideas in a bad language, imagine what you can achieve now that you know to try and improve them 
Patterns in your code often mean that your ideas aren't compressing well, either because they're bad or the language is.
-
-
This Tweet is unavailable.
-
-
-
-
"compressing?" sounds to me like you just aren't coding modularly like you should
-
It isn't only about modularity, it's also about using the same function and syntax for different types. How many functions exists in C for the same operation with different types?
End of conversation
New conversation -
-
-
If you read one of my classes, you need enough information to reason about the code in it. Complex hierarchies confound that, so you get some repetition.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
procedural languages are good at reusing exact syntactic trees, but very bad at reusing similar syntactic trees with different names or minor differences
-
What do you (someone) think as a paradigm good for that usecase?
End of conversation
New conversation -
-
-
I think this is usually called "boiler-plate" when it's the languages fault. I've changed my mind on this being bad though. Patterns and boiler-plate enforce consistency and make code easier to read. i.e. ideas aren't as compressed, so they uncompress easier for a reader
-
Which is why the ternary operator isn’t as common as it could be.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.