Hey Folks! It’s a new site. If you see bad links or odd behavior, please contact me right away. Thanks! – GeePaw
 Home  Home  hom  Meet with GeePaw  Meet with GeePaw  mee  Work with GeePaw  Work with GeePaw  wor  Who's GeePaw  Who's GeePaw  who  Blog  Blog  blo  Contact  Contact  con

RORA - Runs Once, Run Away

 15. August 2017

today’s muse, another damned geepawism: RORA technique. RORA means “Runs Once, Run Away”. it is the standard technique in a great many software dev environments.

a developer is tasked with some story. she codes it using a variety of half-assed techniques, including mostly GAK testing. more geepawism: GAK means “geek at keyboard” testing. you know the GAK drill: run the code. look at the output. fire up the debugger. look at the output. bless it. ship it.

RORA includes not just GAK-centric testing, but all the things we do whose essential focus is “it ran and it worked, so it must be done.”

where does RORA come from? one must be sure to understand, i’m not ranting here about developer responsibility or oaths or such-like. RORA comes from two facts. 1) geeks don’t know how to geek well when they start. 2) managers don’t actually understand what we do.

first, the weak-geek source. see, in this trade, we throw noobs over the wall to fight the boche on their first day. we do it over and over. as noobs, they’re mostly conversant with the basic language syntax and one compiler variant. no slur on them. they’re noobs. so they race through the mud and the barbed wire and the corpses and they charge that story’s machine gun nest. when the shooting stops, they’re dead or the nest is. and they report to us that they did it, and we move another story in front of them.

on the managerial side. ahhhh, it’s harder for me here, as i generally loathe that world. but i will try. there seem to be three sub-issues.

1) managers press for feature-movement cuz they’re pressed for it.

2) geeks, eager to please, say they’re done when they’re not.

3) managers don’t have the skillset to actually assess done-ness or stability outside of actually trying the product.

all of this adds up to gigantic pressure to go all RORA on things.

here are some RORA behaviors i’d call out.

soloing in a normally-paired environment leads to RORA. i can’t overstate the anti-RORA force working with a pair represents.

not versioning/staging output is classic RORA behavior in a web-service world. when i’m an upstream team, it’s not done cuz it works. it’s done because downstream can use it. and downstream uses it FOR DEVELOPMENT, which means they need it to be stable, version-tagged, or side-by-side with whatever was there before.

obviously, no automated tests is a very much a RORA-inducer. but i’d go a little further. i need automated tests of a particluar type, which is a muse for another day.

another RORA thing: does it deploy? if it doesn’t deploy, it ain’t done. if it’s upstream and it can’t be pulled, it ain’t done.

in my current environment, this isn’t true everywhere, the services are all pretty large-scale. this leads to nightmares. if your change is to a large-scale webservice, do you have an in-box version ready for your downstream to pre-develop against? RORA.

do you have actual pro-active contact with your downstream? can you auto-announce updates, not a fucking git comment stream, real updates? do the docs change? did you change them? if not, RORA.

i offer code-clients the geepaw guarantee. it does what i said it does. it does exactly that. if it doesn’t, call me, 247. i’ll fix it. if you’re not able to offer users of your code the geepaw guarantee, you prolly still have RORA aspects to your technique.