Anyone who’s worked with me is probably sick of hearing: fail fast, feedback loop, cycle time, iteration, breaking into subproblems (among many other phrases I’m not aware of). https://twitter.com/chrisalbon/status/1171449109464502273 …
-
This Tweet is unavailable.Show this thread
-
Reflecting on this now, I think every single project that I have regrets about was because the iteration speed was too slow. It feels totally fine to fail after a short iteration but failing after a very long one is devastating.
1 reply 3 retweets 57 likesShow this thread -
Replying to @seanjtaylor
That's the point I try to make in the notebook debate. If you are not careful, they really can lead to hopelessly fragile/confusing code. But if you are careful, at least for me, nothing approaches the fail point faster, even including subsequent extract-to-package-and-test time.
1 reply 0 retweets 3 likes -
Replying to @generativist
Yeah it’s gotten to the point where I sometimes see “quality” code as an anti-pattern. You should be embarrassed at how crappy your prototype is. This is just like writing, btw.
1 reply 1 retweet 3 likes
Yes! I once did a total revisions by keystrokes to something I was writing (not via deltas, like actual keylogging) to see the difference between the final product and everything before it for something I was proud of writing. it made a huge impression on me.
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.