They would have standup meetings each day (ever second episode) and you would see how a large organization would operate efficiently using something similar to Nexus-Scrum.
They would have standup meetings each day (ever second episode) and you would see how a large organization would operate efficiently using something similar to Nexus-Scrum.
I'm now at my third company where I'm the only techie that thinks internal code names are useful and everyone else just uses very generic terms like 'the app'. And when a second app is made, they all seem oblivious to the amount of time wasted in describing which app is which in nearly every damn bug or feature request.
Given that I'm the only ops guy and I have to package this stuff, I give them a damn name and that proliferates back through the rest of the techs. Anyway, the point of this comment is that the latest thing to come my way was a notification service called 'notification service', a seven-syllable horror that will cause confusion with another service that sends notifications, and it does things other than notify (it'll touch and mediate a few things over the network). I said "Can we please call it 'nexus' - because every company needs a bit of software somewhere called 'nexus'" :)
As a bonus, today I set up the first nexus server, for testing...
My favourite shortening was a netadmin friend of mine who worked at a bank a while back, describing coding schemes for network hardware: "blah blah ethernet concentrator blah address blah city makes XXXECO1" => "What's an 'ethernet concentrator'?" => "Is it a switch? Is it a hub? Is it (*rattles of a couple of other things I can't recall)? Who cares? They do similar things in the grand scheme..." And shorten down to a clear 'EC' to cover them all.