2019 is the year we stop writing “pure” functional or object-oriented code, and go back to getting shit done.
-
Show this thread
-
Any project of significant size, no matter what programming language it’s written in, will have places where OO techniques make sense & places where functional techniques make sense.
1 reply 24 retweets 114 likesShow this thread -
It’s ok to have classes with no data of their own and a single method called “run.” It’s ok to have functions that own data & mutate it. Breathe! And get shit done.
8 replies 16 retweets 128 likesShow this thread -
Sarah Mei Retweeted Alan Smith
THIS. I almost always start with a list of instructions anyway, even if I'm intending to end up with classes or functions. A procedure is always easier to understand than a set of abstractions decided too early.https://twitter.com/TheAlanSmith/status/1083783166043803648 …
Sarah Mei added,
5 replies 4 retweets 49 likesShow this thread
Chasing the 'purity' of an object by strict adherence to SOLID and OO design patterns is often detrimental to code efficiency and comprehension. I feel that Principles from 'S' in SOLID should be more abstract. DRY sometimes responsible for reducing readability too.
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.