Re: Public services are probably at higher risk
They're all architected to the same shoddy standard, though, lowest common denominator development, make it secure as an afterthought..
446 posts • joined 1 Apr 2014
Absolutely that's the way it works, with an additional step - between the highest management signing and the finer details, there's a big announcement about how much better the new is going to be and how much will be saved. Then half the workers on the old proceses are ditched and replaced with SNOW customisation 'experts'...
"Unfortunately, in this case, JetBrains had to explain why second place was really first place."
Still coding to 71 characters, 72nd character the continuation line, and the last 8 the sequence number in IBM assembler, but when I started in 1990, we used 132 column emulators for listings, system dumps etc. Ah, VM (now z/VM), what a wonderful development and test environment!
Downvote because "Ginni Rommety was a good CEO. But she frittered away a of IBM's technological opportunities and advantages."
As you later put it, morale is in the sh1tter too.
And centralised bureaucracy (a result of large sites methinks) is also bloated.
If this is a good CEO, then goodness me, I don't want to see a bad one.
"I know for a fact that some of IBM's current gear will run COBOL that I wrote in the early 1970s unaltered."
Indeed, the z series is backwards compatible with assembler too (I'm still active).
How did they end up in their legacys situation with their cobalts and their assemblers? Outsourcing, downsizing of anything that works, refusal to replace retirements, ignorant people in charge who fail to realise the importance of the IT systems they rely on; they're called mission critical for a reason.
Cobol/assembler on mainframe (whether IMS or CICs or whatever (I program on whatever)) technically has no issues. It's a manpower issue. There just aren't enough people employed who know the business systems well enough to touch them, or even to understand them so they can be adequately specified.
The big g will no doubt fire up its Cornerstone acquisition and convert to java. Imagine, if you will, a sprawling java monolith that can only be understood by looking at the original cobol and that still operates in the same way as the original... once you hit a hardware choke point (even in the cloud), you're f'd...
Process, process, process, and more process. Need a pencil from the store cupboard? there's a service now twenty minute workflow for that. Laptop dead? Open a service now ticket! Can't get to service now because your laptop is dead? Open a service now ticket! In a support role and want to do no work provisioning new links? Set up an incomprehensible service now workflow that requires you to learn how to provision the link before you can open a ticket.
I hate it.
edit: oh yeah, and let's automate offboarding so we can automate deleting all our contractors at random points in the quarter while they work out the difference between "one" and "all"...
Never mind the security, feel the process. Six months at my place for the promised split tunnelling to relieve the already creaky VPN.
Re: security - almost certainly your VPN already whitelists all those MS addresses to make o365 and OverDose work, so all you're saving is a round trip through your infrastructure...
Absolutely; "edge case" me hoop.
Everything you don't test is an edge case, that tells you nothing about either how common it is or what the impact of a failure is.
FMEA should tell you that you don't load a quick-fix to broken code in key infrastructure, you fall the original code back and fix it properly and test it properly. It also tells you your original code was insufficiently tested the first time, since it was loaded with a bug in it.
They blew it similarly in the mainframe market. Overcharging license costs, slow and underfunded software capabilities and OS expansion. Products like CICS, TPF, even MQ are milked for all their worth. They are sadly end of life. There may be some twitching, but alternatives exist and if, as an enterprise, you have to re-engineer to reduce cost, you might as well re-engineer onto a different platform.
"The ethos was pretty much "make it work any way you can. I don't care how, just do it quickly", the obvious undertone being "make it look like it works, I'm expecting a botch job that's good enough to get a sale"."
They now call it agile development. The way it is implemented, particularly scrum, is exactly this. Sweatshop it out the door, never mind testing it.
" These technical reviews are expected to turn up glitches and gremlins for Boeing engineers to fix, so this is kinda to be expected."
is just wrong. Very, very, wrong.
The FAA are not the PO, they're not there to do a demo to. It suggests Boeing don't know how to code safety critical systems.
Replatforming is almost never a business initiative. It is a tech initiative ostensibly to save costs, but with entirely doubtful projections. Generally it hits the point of "cutover or cancel" as it drains the company dry. The decision is often to cutover badly performing systems. In the case of TSB, it appears unfixably badly performing, since they're outsourcing the entire fiasco.
here continueth the rant:
and even if the edge cases tests are run, when the inevitable design errors are found, they are ignored because "we're too close to cutover and anyway that's an edge case". Fast forward two years and the product no longer works for so many edge cases that happen daily (when you hit volume, nothing is edge) and the agile prophet has moved on to leading the design of another key piece of product.
Never mind not having any idea, they don't care that it isn't going to work.
WAD has become WBAD - Working Badly As Designed.
More likely the maintenance system ran only on old operating systems, Win XP or older.
If it is the maintenance systems scrambled and they don't have a historical backup, the planes are effectively scrap. Without a documented maintenance history, they won't be permitted to fly (leaving aside the maintenance scheduling aspects and the requirements to confirm). It may be they can fallback to paper, but my guess is the paper processing skills have long since been made redundant.
I've said it before, airlines are enormous nickel-and-dime IT shops with shiny planes in front of them. Without IT, your airline is grounded, there are many, many components to that IT and generally you can't just go to pilotjobs.com and hire in something different.
Or you use Teams. I won't spare you lot my diatribe about this piece of shut.
One thing at a time on a window (no pop-outs, no multiple windows).
Doesn't like VPN (uses a different sign-in protocol and an "am i alive" that involves phoning home to the mothership (I shut you not)).
No group chat without making a team.
Search is awful (though not as awful as Outlook search of shutting archived folders on Onedrive).
You can only speak US english on it and there's no way to turn off spell check so every name (unless it's Brad or LaShut, every acronym, every number with a shutting letter) shows up as misspelled.
The chat editor works differently to the 'full' editor.
This may be a different diatribe to the last list, this is just what the shutting shutter of a shut did to me today.
I'm equally impressed with the u-trun on drivers. It's not just printers, my aged laptop only works with a particularly aged version of an Nvidia driver. I had to hack around a bit to block the driver update. As an aside, disabling, removing, and reinstalling a display driver is the work of the devil.
This post has been deleted by a moderator
Your IP address is personal data if there is other corroborating data that can link you to it. If, for example, your email address is present in the device and captured, or if your personal data is in a packet that is captured during a crash event.
So Ubiquiti are sure they never catch anything that could be linked to the IP address to give personal identification??
Biting the hand that feeds IT © 1998–2020