GeekyOldFart
Three languages
And I'm not talking about programming languages, where most of us are fluent in half a dozen or so.
1: Regulatorian: This is the language of politicians and lawyers. It sets the mandates on banks, hospitals, schools etc. It contains nuances and terms of art that sometimes make a word mean something totally different to what you would infer if you heard it in general conversation.
2: Beancounterese: Spoken by accountantrs, salesmen and middle manglement. It sounds very similar to regulatorian but is sufficiently different in some of its meanings that it's as big a gulf as between old scots and english.
3: Geekian: The language of hard science, mathematics, real-world realities and the only one to use when specifying what a programmer needs to code. Because they will code what you tell them to, and it will work the way this language describes it.
The same word can mean different things in these three languages.
We have to be fluent in all three to accurately interpret requirements and predict what the emerging software will look like, to take error logs and demonstrate to (sometimes hostile) manglement what corrective action is needed and where it needs to be applied.
Michael H.F. WilkinsonSilver badge
Reply Icon
Re: Three languages
It gets worse, as there are quite a few Geekian dialects. I have learnt to speak a couple over the years, and know the word "morphology" can have radically different meanings, depending on whether you are talking to a medical doctor, an astronomer, or an image processing specialist. Great fun when you are in a project with different geeks each speaking their own dialect.
Shirley Knot
Reply Icon
Re: Three languages
Well said!
When writing specs for dev projects and talking to those speaking Regulatorian or Beancounterese it involves finding out what they actually mean, without saying "What the fuck do you actually mean?!" The skill is in performing iterative attempts without making them blow their stacks! The most frustrated person I had to deal with was a lovely chap that'd been doing his thing for decades, in manufacturing/engineering. He knew exactly what he was doing, but couldn't articulate it - quite understandable, not part of his world. Once he understood that I was just a white collar noob and he was the expert he calmed right down and enjoyed going into as much detail as needed. Explosive decompression averted and job done!
