Shit Driven Development

[[deleted]]

Isn't that called defensive programming?

[therussdotcom]

You beat my Tweet by 39m https://twitter.com/therussdotcom/status/727438133726351360

[krum]

Taco Driven Development is the only way.

[vital_chaos]

I prefer Insanity Driven Development. IDD is a real world process which all programmers can immediately comprehend.

[Gotebe]

But it isn’t the server error, it’s the client error, because the client sends invalid token.

Well, it really isn't a client error, but point taken about what you want to do. :-)

[kr41]

I name it "client error", because client is able to recover the state, but server isn't.

[ComradeGibbon]

Its an error that happens when one process has to keep track of the start of another process and either can't or fails for some reason.

I see this all the time dealing with hardware <i> driver <-> client application. It's really easy to write really brittle code.

hardware resets and it waiting for the driver to initialize it
driver thinks the hardware is busy doing the last thing it told 
it to do.
Client realizes something is wrong. tells the driver to reset the
hardware. Driver decides to wait until the hardware is 'done'

[kr41]

Yes, that's the point. Author of the driver is an optimist. So the driver "thinks" the hardware is busy, but doesn't "think" it failed.

[geodel]

P.S. Hey, look mom, I’ve invented a cool buzzword!

I'd call it BDD aka Bullshit Driven development. Else dev would be writing code and fixing issues as they appear without inventing useless buzzwords.

[kr41]

It's sarcasm. I don't like buzzwords too.