I'll see your janky corporate Chrome and raise you Bing in IE emulation mode...
578 publicly visible posts • joined 1 Apr 2014
Bear it in mind when next you're asked for feedback on the outsourcers. The teams I had were routinely exhausted, training and time off not planned in to sprints, all working US hours. Unsustainable madness that resulted in poor engagement and poor quality work.
Generally it means the box (empty) is not in the place the ULD tracking system says it is. Like another poster says, wetware has to follow the process. If they don't scan the ULD as arrived or loaded on a plane (a problem when they ad-hoc change them due to knackerage or size limits), they end up wrong and hard to correct.
WTF?! A system in a 24 hour operating environment that never stops that has to have everything down for maintenance at the same time? I've worked in the airline industry for mumble years; we've spent our lives removing downtime, working for 99.999% uptime and largely achieved it. Now all this new crapware comes along and it's not even designed for basic uptime?!
So it's a known issue? A known issue that wasn't tested?!
Every admission is a new scandal :)
IIRC a dodgy flight plan caused the last outage. How did they not learn the last time that the first rule of resilience is to get back operational? Find the error data, poke it out, restart quickly. They're not saying a restart takes 4 hours are they?
When I started, I was in Marketing Automation or Agency Automation (in the airline/travel industry). The idea was the existing paper processes were good and existed for a reason, and the IT challenge was to automate them. That was it. Not to reinvent them, not to put a one-size-fits-all solution in.
I pretended my only computer was a dumb terminal connected to an IBM mainframe. Then I suggested using my teletype console printer and sending a printout of the response.
Another time, I acted like he was a double-glazing salesman and whenever he mentioned windows, I would say I already bought new ones and describe them.
Mostly I ask them to hold on a minute and put the phone down by the radio/stereo and walk away.
"The lazy naïve way to "lift and shift" from on-prem to the cloud is to create a new EC2 for each existing VM. That never works out, cost-wise."
It depends. I was going to put a complex answer to back that up, but I'm already into pages of ifs and buts. Some short bits - if you are already in a managed DC (even if it is one you own), the cloud is probably cheaper than your current vendor. If you have strong DR requirements, the cloud is probably cheaper. If you are already clustering your workflows using Openshift or K8s, the cloud is probably cheaper).
The implementation details really, really matter though. As you say, life and shift is only step 1...
Podman to the rescue!
At work, this is where we are heading as the Docker license fee for Docker desktop becomes substantial.
You can use a Dockerfile to build a Podman image, or you should be able to just run the Docker image with the Podman daemon.
On windows, WSL2 is used which is not without foibles, so if you're running a production workload, I'm not sure I'd recommend it.
" Its just a Public School classics education doesn't give you the technical smarts to understand this sort of thing."
Well, a Public School education doesn't equip you for accepting you are wrong and cannot be right about a subject with a wrong/right answer. It's not about understanding, it's about the willingness to understand when it could change your view on the subject. The whole denigration of expertise is based on this "don't tell me what will change my mind".
Lastpass only encrypts username and passwords, all other data in your vault is in clear text (base64 encoded). That means they've lost all the information necessary to phish you, all the notes (e.g. your second factor pin that you stored in a note). Everything else is gone, almost certainly. They would be telling us if it was limited and they aren't.
They're probably running at least z15s. Program design of 1960s assembler bears a sharp resemblance to current vogue of microservices architecture and is possible to build error free and understandable to future generations - you don't have to endlessly refactor it to understand it. The documentation has not kept pace, but I currently work on java systems that are built with no documentation (not even comments in the code) other than a story.
This is what you get. You have to have all the customer facing systems yourself. The major GDS at the time of Covid had huge negative cashflow as they processed refunds for passengers booked through them (on behalf of the agencies they booked through). It is a normal, automated process using BSP (bank clearing between GDS and airlines) to debit the airlines. Southwest have started to use GDS ticketing, but only for limited fares. Prior to this, even GDS bookings were paid directly to the airline with refunds and exchanges directly to the airline.
The best customer service my aunt fanny...
The problem is not so much with the password manager, but with the rest of the crap around the cloud storage. Bitwarden has their manager code opensourced, but in Lastpass's case, shoddy code left hard-coded credentials to cloud storage bucket (it's really egregious, since all the major cloud providers have secret managers that you can build to only access at runtime, assuming you can be arsed to code it that way). A breach of the development environment (poorly secured in many companies it seems) left free access everywhere :(
I'm a bit pissed off with the drips of increasing badness coming from Lastpass. What next? Login emails also compromised, but don't worry, they can't be associated with vaults? Well, they can be associated with vaults, but not with the list of passwords, what, didn't we tell you all the master passwords got released too? Yeah, I know we weren't supposed to have them stored, but some random error captured them to diagnostic logs. Those were captured too.
Not only "yes, yes it is affected by most of those bugs", but long is not very long, and the longer you stay on LTS, the worse the experience using other products becomes. It seems all the other MS products are only tested well on the latest release, so bugfixes to other products break because of your LTS in unexpected ways. Locking everyone who rises early out of AD is my favourite.
The intermediate bluffers are part of the problem too. When I started as a junior programmer in 1990, there were 5 levels above me to the CEO. Now I am senior technical, Director equivalent level, and there are still 5 levels above me to CEO... for all the talk of agile, there's more admin work, more unproductive time grooming increasingly inane stories "as a developer, I just want to get some fucking work done, so I can get out of this fucking meeting".
It's unsettling that MS seem the most organised when it comes to mainframe offload. It's almost like they are listening to the specific problems mainframe migrations present and partnering with companies that can help solve them.
Still, let's have some more observability AAS, with no mainframe integrations shall we. Trebles all round for DC Service department!
They're not getting experience either, at least not in IT. The new workplace is an agile sweatshop run on a magic beans theory that tnsane amounts of single-issue work is what makes people productive. It might be short-term productive, but it does not spark joy. The grinding unhappiness of being a cog in a production line is killing the last remaining solace of programming - making a piece of code that does something. A piece large enough and complex enough that it takes some thought and some trial and error. A piece that is not a demoable story in an time-boxed horizon to the same poxy cadence as every other production-line worker in the sweat-shop.
It's a horror show. Pinned documents lose their pinning. Recently updated is a joke. Quicklinks seem to be deprecated because opening an open/save menu scrolls to the bottom of the tree, to where I don't want to be. New Whiteboard doesn't store recent Whiteboards locally, so they aren't in the previous file list.
I can find nothing. I know I wrote a document last friday, I thought I put it in Onedrive in the normal place, but it is gone. So I rewrite it, save it with the same name as I thought I used... would you like to replace? Would I ducking like you to remember what I did and where I did it?
And it's all soooooooooooooooooooooooooooo slow :(
Even in the 1980s, a TPF system (2.4 or 3.1, most likely 2.4) had at most 32 mb and on that supported thousands of terminals round the world. a 2.4 system was 31 bit, but only used 24 of them, meaning there was a byte available in every word that stored a core address that could be misused... the conversion from 24 bit to 31 bit was excruciatingly boring (check every core address use).
In addition transmission costs were hideous and you got very few bods. I remember a user coming to me, then a very junior programmer, wondering who UNA PROC was, or UNABLE TO PROCESS.
The glory days of every airline having their own TPF (or ALCS) system are pretty much gone, but I still make a living wrangling Teletype... the past is still the present. What's interesting with K8S is that it exhibits many of the characteristics of a mainframe cluster...