-
i don’t know if i really think this kind of code is “bad”...it’s saying a lot, when you think about it!
I think that it's a problem if new contributors find code so opaque that it's difficult to contribute to, which can often be caused by unreasonably generic code, or code that has been abstracted poorly
-
-
Yeah, strong agree with this. Maintainability and comprehension are important factors! But its all a balancing game with all the other components, perf, correctness, extensibility/replaceability. Engineering is all about tradeoffs, and one tradeoff is rarely universally correct
-
But the fact that we CAN express these kind of constraints is def good.
End of conversation
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.