There are some segments from a few episodes that show that Marco is demonstrably not a super great programmer. I suspect some of his server side code is horrible. But he doesn't matter because he is super strong at other stuff super focussed on solving his own problems at gets it done. You don't need to be super great at programming you just need to be tenacious.

It contains the K8's cluster and makes it easy to recreate things if (when) you screw up. You wont spend the majority of your time fixing the cluster instead of learning how to use the cluster itself.

Then you can pick any K8's tutorials or courses. As previous folk have said there are plenty of them about. Udemy, Coursera, Pluralsight, Oreilly all have really good resources. Or just use all of the free tutorials and resources out there. Search GitHub for some 'awesome lists' etc.

I can't give any detailed advice on courses having not done them myself! I have used books online and kind to figure stuff out though!

Good Luck! James

Cost is not the driving factor, and in any case, cost is often calculated wrong. Putting one set of prices 'for stuff' in one column and another set in another column and looking at the difference tells you almost nothing.

Forget about start-ups for a minute. There are certainly arguments to be made both ways there. Focus on big enterprises for a second. Infrastructure complexity isnt getting smaller over time and neither is demand. Delivering on demand and managing complexity with a bounded number of people requires a change in thinking when it comes to infrastucture writ-large. We cannot sustain the old on-premises, dinosaur pen style data centres and deliver and grow our core businesses. It just wont work... So you either go cloud or create something very cloud like and do it on-premises. Heck that is how AWS came about in the first place.

Anyone that thinks going cloud is a good way to reduce headcount is going to get a shock. Going to cloud (or lets say changing the way you do infrastructure) is a way to continue to do business with the headcount you have. It's not a question of carrying on with the 'old school' infrastructure you have, you just want keep up doing that. Do nothing and your headcout requirements are unbounded.

Anyone that thinks cloud infrastructure requires you to hire only a bunch of cloud experts is wrong. Chances are you have the bulk of the infra people you need right now. All those people that have been doing 'old school' infrastructure for years are still your most valuable resource. The mechanics of the infrastructure are fairly irrelevant (ok they are not, but in the grand scheme of things we can kind of cancel the mechanics out in the equations), oft missed value is the operational knowledge. The operational bit is what gets swept under the rug in the DevOps discussion. I believe the knowledge of how to translate existing infra into a 'new' model doesnt come from hiring DevOps people or cloud people, it comes from the infrastructure people that have been doing it for years. Leverage the intellectual capital you already have.

The flip side of that bargain is that 'old school' infrastructure people need to recognise we have to adapt. Those that dont are doomed to be cancelled out in the same equations that cancel out the mechnanics of the infrasturcture itself.

Enterprises that fail to recognise the shift are also doomed. Those start-ups we arent talking about? They can scale far more quickly and quickly get to a point where they can deliver at the level a much bigger organisation can. They can eclipse the slow movers. I assume this is why a lot of consolidation happens... The slow dudes only really have one move and that is to buy the little guys before they can get there (the Facebook defence). But thats like doubling your bet on red every time you lose at roulette. Eventually you go bust or the game moves quicker than your bankroll...

Thanks, James

1.) The grass is not necessarily greener on the other side of the fence. Have you got an idea of what you want to do? What you will accept? Even if you just want to leave, you need a plan. Otherwise you'll take something worse out of desparation down the line.

2.) Even if you find a "dream job" or even just a better job things always change. Especially in London. This might also be the case for the job you are in. Is it a temporary rut you are in? Like another commenter said, do you like the company but not the current position? If so the company might do a lot to retain you rather than see you walk.

3.) Exploit your network to explore options before leaving. Use the current situation as a chance to seriously look and to build a plan. Its easier to find a job when you already have one that to find one when you are desparate. I am sure you have but... If you have friends or connections at other places tap them up. You never know...

4.) This lockdown is doing funny things with all our heads. Take a deep breath, work out if its just the insanity of the situation that is clouding your vision. If you commute into London normally and now you are stuck at home, you might be suprised how much energy that city imparts when you are in there.

I have experienced this first hand. I mean... Its nice to have flexible working, to be at home and in the city because the opposite is also true, London can really bite you! But... London in the summer, especially after work in the City... One of the best places in the world.

If after all those questions your mind is still set on leaving, then you are making the right choice! Hell there is no wrong choice. We only live once!

Best of luck mate!

However... The Polish codebreakers are without doubt the first true heroes of the Enigma story during the war. Their genius, bravery and dedication opened up breaking enigma and saved a lot of time for the British codebreakers early on. As Welchman says, the Polish provided details of the machines that helped immensely in breaking into the military enigma. That said, the British were already working on it and had in parallel come up with some of the same methods as the Poles. The Turing-Welchman Bombe was designed from the ground up to attack the military enigma and used different principles than the Polish Bomba.

This is not to underplay the Polish role in all of this. They are without doubt in my mind as much the hero's in this as Welchman, Turing and the others at Bletchley. Without them the allies would have been way behind the game at the start of the war and therefore many additional lives would have been lost. The Polish codebreakers need more acknowledgement in this story. Glad to see the new Dermot Turing book out on this subject: https://www.amazon.co.uk/Real-Story-How-Enigma-Broken-ebook/...

Thanks, James

Donitz was one exception. He suspected the allies were breaking enigma and hence the security of the naval enigma's was increased. I believe he advocated for more changes but was stopped or ran out of time.

After the war the allies sent in teams of intelligence operatives to assess how much the Germans knew about allied codebreaking and intelligence efforts. What they found was that the secrecy of Ultra worked and held throughout the war.

James

Thanks, James

Thanks, James

The US Bombes were better and workloads moved over to them for that reason, mainly because the US could make them faster with a better (later) design. But they come online 3 years after the first British Bombes which were in effective use until the US Bombes were available. It was the 4 rotor naval enigma that slowed things down somewhat.

Thanks, James