I installed this via mise. `mise use ubi:seeyebe/gmap --global`.
I noticed I had to run `gmap heat` to generate a cache folder and db locally before running `gmap heat tui`, otherwise nothing shows up.
It's scary to have the cache folder locally because I could accidently check that in if I don't place it in a .gitignore; is there a better way to handle something like that?
That might've been the case, but it can't be the excuse.
They were spending €100mil a year on maintaining the current infrastructure. The team's incentive is to save a large portion of that through the migration, and somebody higher up should've given them unlimited access to do so.
Enterprise tend to favor big bang migrations on a specific date because somebody higher on up set a particular date and everything falls into place with a Gantt chart running waterfall. The reality is that it falls onto a few technical folks to triage a large amount of teams, including the ones from the company they're trying to break away from (which introduces friction). This includes significant risk to the project.
"TSB chose April 22 for the migration because it was a quiet Sunday evening in mid-spring."
This might've gone better if TSB chose months prior to April 22nd for the long duration migration and testing to be completed, and a period of weeks or months for going live post migration. The F5 load balancer (hardware commodity) could've slowly cut over the traffic 10% at a time to the new migration site to get a feel for user experience. Coordination with the TSB network team would be necessary to accomplish that.
It is a tough spot though, I hope the team learned something from that.
I installed this via mise. `mise use ubi:seeyebe/gmap --global`. I noticed I had to run `gmap heat` to generate a cache folder and db locally before running `gmap heat tui`, otherwise nothing shows up.
It's scary to have the cache folder locally because I could accidently check that in if I don't place it in a .gitignore; is there a better way to handle something like that?