... which I think is a totally worthwhile cycle. That's how you gain understanding. Or how I do, anyway.
-
-
-
@avibryant Yup. Worse is: this legacy code is overly complex, lets do a simple rewrite... Oops.
End of conversation
New conversation -
-
-
@sferik@avibryant@JorgeO Corollary: The most interesting code is that which has IO, and IO is an unstatable force. -
@evanphx@sferik@avibryant@JorgeO further: the most lucrative code does IO; there’s no money in pure functions operating inside a vacuum -
@therealadam@evanphx@sferik@avibryant@jorgeo I think there's a compelling counter-argument here, but not in 140 chars. -
@therealadam@evanphx@sferik@avibryant@jorgeo TL;DR: IO is necessary but not at all interesting. Haskell shows this well. -
@ReinH conversely, what I learned from Haskell is that programs that don’t do IO are next to useless and therefore pretty boring -
@therealadam@ReinH heresy. Parsing other programs that generate parsers to parse other programs is the only interesting task in CS! ;-) -
New conversation -
-
@avibryant@rabble sounds like a good reason to publish a test suite with your algorithmThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@avibryant what was the most recent example?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@avibryant it’s the only way I’ll learn.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@avibryant even worse is when you miss the edge cases and smugly produce "simpler" but buggy code :/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.