I want a sci-fi show about an engineering team that debugs and deploys fleets of robots/organic aliens inside the bloodstream of a giant space whale creature in which, humanity itself is living on some sort of floating enclosed solarsystem bubble.
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...
Yea, Im on the other end of the spectrum: So IDP integrates with SN, OHS, ADP, RDC, Xym. The support is managed by the SSD, DC2 (and many, many more....). I think the Project and Product managers make these up to prove they are doing something productive. So many acronyms, and no documentation except the main project docs. So you need to read a mountain of documentation to even know what people are talking about. Even better when you have IDP, ADP, EDP etc and people from several different countries trying to pronounce all of these correctly.
My personal naming rules are "one unemotive word, two syllables max, with clear unambiguous spelling and pronunciation". Maybe go to three syllables if it's really fitting. Generally the name is not meant to reflect the function - the point is to be memorable, not descriptive (and not customer facing). This being said, I'm a small company guy, so I haven't run into the need for amazing amounts of acronyms or product names (I'm not sure how far my rules would stretch...)
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.
I'm a bit the same. It was really enjoyable, and then just bogged down at the end of the first season, with an amazingly trope-ish 'twist'. I think the lead actor is outstanding, being able to convey 'numb at the world' rather than just 'unexpressive/emotionless', but yeah, it's just too slow.
And when push comes to shove, while it's great to see actual tech in action, it doesn't actually matter that much to the story. As long as the characters aren't doing things that actively break immersion (blue ribbon award goes to NCIS having two people type on the same keyboard...), it doesn't matter to me so much if the 'hack' is real or not.
My favorite hacking scene is still from Scorpions (well there are two, the one below and the one where they are hacking a jet, with a RJ45 cable, from a car while landing).
"We need to hack NORAD!"
Guy reaches for keyboard (without touching it), "Done!".
Sarcasm apart, while Mr.Robot has good tech, I got bored by the story line around episode 4 or 5. I think it was just too slow for my taste.
There is a fantastic short (scifi) story about consumption/attention economies taken to their logical conclusion on SomethingAwful (I think), but I can't find it right now.
It's a _super_ tropish twist, but I think that's a knowing choice. There's a great Extra Credits episode (usually a video game analysis show) exploring that theme at https://www.youtube.com/watch?v=ghrI2Vb8u2U
In my mind (though future episodes could prove me wrong), Mr. Robot is taking its favorite tropes from hacker culture, anarchic culture, and corporate culture, and using them to paint an interesting picture of helplessness and instability.
I dunno, I certainly like the show. Maybe it's just the general malaise I'm feeling, but it's certainly poking at many of the things I feel are wrong in the world. God knows, if it were possible to accomplish what they did in season 1 I would have been more than on board.
