STFUDD
chriscontinanza.com
STFUDD
1–10 of 20 posts
Re: STFUDD
#2Akin to 'grow a pair' programming.
Re: STFUDD
#3See also the "shut up and calculate" interpretation of quantum mechanics.
Re: STFUDD
#4I fail to understand these two parts:
"In STFUDD ... you don't write anything at first. " "STFU Driven Development ... its How quickly can we Shut the Fuck Up and write something?"
So, which is it - don't write or write quickly?
I also fail to understand this part:
"we're all full of shit. And that's why you test. That's why you write a README."
How exactly "tests" and "README" connected to "we're all full of shit"?
Re: STFUDD
#5I fail to understand these two parts: "In STFUDD ... you don't write anything at first. " "STFU Driven Development ... its How quickly can we Shut the Fuck Up and write something?" So, which is it - don't write or write quickly? I also fail to understand this part: "we're all full of shit. And that's why you test. That's why you write a README." How exactly "tests" and "README" connected to "we're all full of shit"?
I think the point is, stop arguing about these things and get coding.
Re: STFUDD
#6It is late night, and i'm trying to practice the SRHNDD ("Stop Reading HN and write something") so STFU and post something interesting.
Re: STFUDD
#7I fail to understand these two parts: "In STFUDD ... you don't write anything at first. " "STFU Driven Development ... its How quickly can we Shut the Fuck Up and write something?" So, which is it - don't write or write quickly? I also fail to understand this part: "we're all full of shit. And that's why you test. That's why you write a README." How exactly "tests" and "README" connected to "we're all full of shit"?
I think the point is, stop arguing about these things and get coding.
Not quite IMO - Yes it means stop. But then I think it means - find the simplest thing that could possible work - and then get on with it. Works for me.
Re: STFUDD
#8"Conscious."
Re: STFUDD
#9Sure, there are some productivity benefits of the "STFU and start writing something" part, but this post itself has a few contradicting points. If everything is wrong in some context, why should i care about writing README and tests first at all times? Say when starting a project using a new language, I don't bother writing tests because I know I'll probably revisit for a rewrite soon enough, and by then my tests will be better. It worked better for me this way. How did I know that? Hmm sometimes I stopped and asked myself what approach to take so I just STFU & take the same approach later. Oops that violated STFUDD in the first place :)
Re: STFUDD
#10Zed Shaw imitation fail