That's not a factual statement over reality, but more of a normative judgement to justify resignation. Yes, professionals that know how to actually do these things are not abundantly available, but available enough to achieve the transition. The talent exists and is absolutely passionate about software freedom and hence highly intrinsically motivated to work on it. The only thing that is lacking so far is the demand and the talent available will skyrocket, when the market starts demanding it.
They actually are abundantly available and many are looking for work. The volume of "enterprise IT" sysadmin labor dwarfs that of the population of "big tech" employees and cloud architects.
I've worked with many "enterprise IT" sysadmins (in healthcare, specifically). Some are very proficient generalists, but most (in my experience) are fluent in only their specific platforms, no different than the typical AWS engineer.
Perhaps we need bootcamps for on prem stacks if we are concerned about a skills gap. This is no different imho from the trades skills shortage many developed countries face. The muscle must be flexed. Otherwise, you will be held captive by a provider "who does it all for you".
"Today, we are going to calculate the power requirements for this rack, rack the equipment, wire power and network up, and learn how to use PXE and iLO to get from zero to operational."
This might be my own ego talking (I see myself as a generalist), but IMHO what we need are people that are comfortable jumping into unfamiliar systems and learning on-the-fly, applying their existing knowledge to new domains (while recognizing the assumptions their existing knowledge is causing them to make). That seems much harder to teach, especially in a boot camp format.
As a very curious autodidact, I strongly agree, but this talent is rare and can punch it's own ticket (broadly speaking). These people innovate and build systems for others to maintain, in my experience. But, to your point, we should figure out the sorting hat for folks who want to radically own these on prem systems [1] if they are needed.
I don't really think so. That was a ship that sailed ten years ago and nearly every sysadmin who is still proficient with managing on-prem stacks has adapted to also learn how to manage VPCs in an arbitrary cloud. It's not like this is a recent change.
> and the talent available will skyrocket, when the market starts demanding it.
Part of what clouds are selling is experience. A "cloud admin" bootcamp graduate can be a useful "cloud engineer", but it takes some serious years of experience to become a talented on prem sre. So it becomes an ouroboros: moving towards clouds makes it easier to move to the clouds.
> A "cloud admin" bootcamp graduate can be a useful "cloud engineer",
If by useful you mean "useful at generating revenue for AWS or GCP" then sure, I agree.
These certificates and bootcamps are roughly equivalent to the Cisco CCNA certificate and training courses back in the 90's. That certificate existed to sell more Cisco gear - and Cisco outright admitted this at the time.
In part - yes. Useful as in capable of spinning up services without opening glaring security holes or bringing half of the infra down. Like with any tech, it takes experience and guardrails to use it efficiently and effectively.
> A "cloud admin" bootcamp graduate can be a useful "cloud engineer"
That is not true. It takes a lot more than a bootcamp to be useful in this space, unless your definition is to copy-paste some CDK without knowing what it does.
Only time will tell. It depends on when someone with a MBA starts asking questions about cloud spending and runs the real numbers. People promoting self hosting often are not counting all the cost of self hosting (AWS has people working 24x7 so that if something fails someone is there to take action)
> AWS has people working 24x7 so that if something fails someone is there to take action..
The number of things that these 24x7 people from AWS will cover for you is small. If your application craps out for any number of reasons that doesn't have anything to do with AWS, that is on you. If your app needs to run 24x7 and it is critical, then you need your own 24x7 person anyway.
All the hardware and network issues are on them. I agree that you still need your own people to support you applications, but that is only part of the problem.
I've got thousands of devices over hundreds of sites in dozens of countries. The number of hardware failures are a tiny number, and certainly don't need 24/7 response
From what I've seen, if you're depending on AWS, if something fails you too need someone 24x7 so that you can take action as well. Sometimes magic happens and systems recover after aws restarts their DNS, but usually the combination of event causes the application to get into an unrecoverable state that you need manual action. It doesn't always happen but you need someone to be there if it ever happens. Or bare minimum you need to evaluate if the underlying issue is really caused by AWS or something else has to be done on top of waiting for them to fix.
I've only had one outage I could attribute to running on-prem, meanwhile it's a bit of a joke with the non-IT staff in the office that when "The Internet" (i.e. Cloudflare, Amazon) goes down with news reports etc our own services are all running fine.
Distributed systems can partly fail in many subtly different ways, and you almost never notice it because there are people on-call taking care of them.
I can't turn it off on my Samsung Galaxy S23 which I originally bought, because it was not marketed with AI. The patched it in later and ever since it just randomly starts as if it was listening all the time.
I was also baffled how the author completely fails to realize, that the US didn't just abandon Europe, but is actively exploiting and working on undermining it.
I find this topic of link aggregation, feeds and readlists highly interesting and believe that herein lies the solution for a new web similar to like reddit basically imagined it, before going full commercial.
Both presented ways in looking at an RSS feed make sense and come with their own set of pros and cons. But to me it looks like it is entirely possible and the best solution to treat it as both at the same time: the feed is a stream, but you treat it as an inbox not for the items that are streamed themselves (e.g. blog entries), but as the notification that they exist. So, I will try out in the future to keep three lanes: a readlis, where you store the things you want to read, a read-it where you store the things you actually read already and the RSS-feed aggregor "inbox" where you marked things as read if you decided to either put it on the readlist or not. So the read-marker of the RSS-feed aggregor becomes a "noted-it" button.
A fourth lane that forwards interesting reads or notifications could be the building brick of a new internet, where you aggregate things from people you like or trust and index them as your personalised search engine.
Yeah, everything you've said makes good sense. At the end of the day RSS is just a decent protocol for these purposes, even if more modern alternatives exist. But I think these modern alternatives are better for your purposes.
I had looked into JSON Feed or WebSub as a layer on feeds. I'm not sure it's possible but the federated thingies like ActivityPub might also give the same result, especially since Ghost supports it natively in the dashboard.
wdym? We are in Edward Snowden times. The timeline where Edward Snowden gave up on an awesome life to inform us, the global public, of the greatest scandal of all times and nothing happened, to be precise.
Your refusal of 996 is relatable for senior or mid level workers. But that's something less experienced people can not afford and in this market even unlucky seniors are forced to accept things they wouldn't have to 2 or 3 years ago.
reply