the problem is less that coders are the kind of idiots who'll say "you don't need a DoClearlyExpressedThing() method when you can just write <big pile of boilerplate> every time", it's that they're such cope monsters they build egos out of how clever <big pile of boilerplate> is
-
-
Replying to @chaosprime
Hmm. I'm guilty of taking pride/satisfaction on how well I can restrict the <pile of boilerplate> away into specific libraries, and write top level stuff like InitiateStuff() DoStuffA() while(1): StuffB() StuffC() HandleExceptions()
3 replies 0 retweets 3 likes
Replying to @mvhElmore
Chaos Retweeted Complexifire
sounds legit careful thohttps://twitter.com/complexifire/status/1259211659362668548 …
Chaos added,
Complexifire @complexifire
Replying to @chaosprime
this, but the opposite. i build my ego on how much clear "boilerplate" i can eliminate with DoClearlyExpressedThingFourLayersDeep() even though "ClearlyExpressedThing" is only clear while you're One with the code, and is arcane af even 2 weeks later
2:54 PM - 9 May 2020
0 replies
0 retweets
3 likes
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.