Getting this background requires a non trivial amount of time. It's easy to take our ability to generalize different computer based tools when you already understand digital computer architecture and know a few programming languages. The vast majority of people do not start from such a broad base of knowledge when choosing some software tool to learn.
Or this could be the right time to check one of the self hosted alternatives (Matomo, Snowplow, etc), apply what she learned about Google Analytics, learn how to do it on those systems and sell her skills on two different classes of customers: the ones that will keep using Google Analytics, the ones that will try alternatives, at least not to be fined if not out of genuine compliance with the local laws.
> However now we're in a situation where at least a few thousand people depend on this precise tool existing, and will be economically useless if it is banned.
Not really, there is no GoogleAnalytics-industrial complex yet, but yes apparently they have quite a lot of lock-in on nonprofits. I see this story as a privacy regulatory story driven by the EU and GDPR. They will order GoogleAnalytics to fix violations, and then Google roll another version of GA. Customers who want to take a stronger stance on privacy would migrate off GA.
I doubt there is anyone whose entire livelihood depends on GoogleAnalytics (I don't think your relative's "entire value" does, for example) and even if there was, they could reskill in the medium-term, but anyway you could make the same comments about certification, lock-in and perverse incentives about AWS, or plenty of other companies in previous decades.
there are privacy-compliant products in that sense, unless you've been literally told "click here and click there" you should be able to employ old concepts with new tools.
> Personally I find this astonishingly foolish of the people who train exclusively on these tools instead of first principles and primitives.
I wouldn't be surprised for this to be a "click here and click here" kind of training. I've seen a painful amount of those. And then, when the inevitable "new and improved ui" comes along, these people are lost and require a new training.
Not all, but there's many.
This is how corporations and the will to profit undermines first principal knowledge and leaves a wake of fake education that ultimately needs to be unlearned or unwisely held as a fragment of useful adrift in an island of potential non-logical nonsense
Your run-of-the-mill business drone will be trained on Word/Excel/Outlook and be hard to impossible to retrain on anything else (either because of actual stupidity or resistance to change). This already starts at school where "Informatik" is often just learning where to click in Microsoft products.
Similarly, tradespeople often specialize in certain tools and products. Your average car repair guy will often be forced to specialize in one brand of car. Your home appliance guy will preferrably sell and repair one brand of washing machine, dryer, dishwasher.
Not because of skill issues, but maybe forced because they work for a dealership that sells a particular make exclusively or, less often, a specialty shop; most “car repair guys” outside of those environments have to be generalists.
> Your home appliance guy will preferrably sell and repair one brand of washing machine, dryer, dishwasher.
IME, the sales are done by shops that carry many brands, and delivery, installation, repair donw by firms that often have relations with the retailers and handle whatever you get from them, including multiple unita of different brands that come together with the same team. They may also have relations with the manufacturers, but those don’t seem usually to be exclusive.
Yes, I'd expect any car guy to be able to change your tires. Or change your oil. But even resetting the oil-change alarm or tire-pressure sensor can be a hurdle here:
Manufacturers also use skill issues to their advantage to bind tradespeople. Modern cars do need manufacturer-specific diagnostic devices that used to be unobtainable for independent shops. Since that practice has been largely forbidden by the authorities, now the software, cabling, and diagnostic output are made intentionally hard to understand without having taken the corresponding lessons that the manufacturer provides for a modest fee.
If a seasoned mechanic is unable to figure out how to reset the Maintenance Reminder or look up how to sync Tire Pressure sensors, run away.
In the same way that one can use knowledge of one programming language as a means to leapfrog into other languages, other skilled trades are similar. Perhaps there's something that could be said about an ICE mechanic trying to dabble on Electric but that's not the point you're making. So yeah. I know you're trying to make a point about lock in, but when I think of people I want to hire for tasks who might say "Oh, sorry, you have a Volkswagen and I only know how to work on GMC" I wouldn't take my GMC to them either. It shows a fundamental lack of skill in that they don't understand the broader concepts and their universal applications. If I, a programmer, can figure out my Volkswagen, my GMC, my Mazda, my Nissan, certainly a mechanic can. If my appliance repair specialist can only do Whirlpool when I ask for help on a Bosch that's red flags.
One might specialize. Sure. But to refuse? Weird. But I fear I might be getting lost in the weeds here because its all about the approach. "Sorry, too busy to take on work on things that aren't my specialty": yep, understood. "Sorry, I don't know <model> I only know <other model>" bad.
It is not impossible but if you try to go to a random shop you found on Google and fix your Citroen or Renault you might be surprised.
I guess some mechanics will prefer to work with a smaller number of models, because they're much faster if they're familiar with the model, but new models come out every year, and they need to learn how to fix those. If a mechanic can learn to fix the newest VW, they can learn to fix the newest Renault, it just might not be worth their time if they have enough work to do.
I believe person learning GA could learn any other analytics tool. It is just not worth their time.
Any mechanic can fix a Citroen, but is it worth the floor time it'd take to get the parts and figure out french quirks vs working on something they know that they'd make the same money in a third the time.
Having done shade tree work on various cars, I'd totally turn down any Subaru engine bay work if I was already close to swamped.
Most specialty equipment costs less than a mechanic can earn in a day. You even order the parts from the same company no matter if the bumper is for a Mazda, VW, or an Alfa. Or a Kawasaki motorcycle for that matter. This lock-in behavior is, luckily, mostly illegal.
In the US, for a very long time, you had to find an "import specialist" mechanic, even long past the point where Japanese brands had gone mainstream. Part of this might have been because of the availability of metric tools at the time; my family had a set of metric wrenches specifically because they had to do occasional light maintenance on their early Datsuns and Toyotas.
I can recall that the mechanic in my neighbourhood was decidedly unwilling to service a new Hyundai in the late '90s. He complained they were 'disposable'.
Specialized items require specialized tools. Specialized tools, like all other tools, require maintenance and they change.
A shop dealing with domestic produced automobiles can significantly reduce profit-bleed by not servicing vehicles that require special tools, special diagnostics, special machines, etc.
It's simply a math equation. Do I serve enough of these vehicles daily/quarterly/yearly to make these expenditures profitable for me? The shops you're referring to answered no to that question.
Yeah, I work at a corporate office and have made it a mission to see what kind of work they do, and majority of the time...it's pointless meetings and meetings that involve pointing to IT workers and saying "do this". I check many of their daily schedules, and see what kind of stuff they talk about in meetings...just wow. Am I an "asshole"? Sure you can call me that, but I can call them useless in turn because I wonder how many more qualified people out there who can replace these workers.
Have you ever dealt with an average IT department in a non-tech company? This attitude doesn't help anyone and I really want to believe that only a small minority of tech people think of any other worker anywhere as an "asshole".
I get they have to deal with a bunch of technical inepts constantly falling for phishing attacks and occasionally teams will make outrageous requests to them that simply can't be done, but their attitude is terrible.
If you ask for something simple but "scary", like a firewall or internal network change, they will immediately assume you are just some idiot and speak dismissively to you in a very obvious manner. It's extremely frustrating because they won't even bother to read your emails that justify the change and will just invent some unrelated excuses about why they can't or say they will get back to you later (they don't).
Ironically the only way to get anything done through them is to have my team members create a bunch of duplicate tickets (1 per person), and schedule multiple pointless meetings with them that essentially just consist of me reading my emails to them out loud.
Non-technical teams in the company get the same treatment but lack the technical background to counter them. Frequently I've had team leaders come to me to get a second opinions on the stuff IT tells them and it bothers me how much they seem to clearly exaggerate the difficulty of things. To the point where I can't help but wonder if they are just pretending to know what they are doing, and use their better-than-you attitude to mask their own ineptitude.
So overall I feel the negative reputation of IT departments is earned.
Scotty Engineering principle at work. I'm no stranger to that, it's often enough the only strategy keeping higher management from completely swamping you with work.
Most people in america are incapable of taking a burger order properly, let alone writing a polite email to a vendor detailing a problem.
Now, I don't know what is this percent, but let's give it a name: the ChatGPT percentile cut line.
My intuition says this line sits to the left of the median, so in a sense you are right, meaning that fewer than 50% of people have a measurable intelligence lower than this line.
However, it can also be higher than 5%, and this means many millions of people can be easily replaced by an automation tool, without any bad consequence.
Please include all the steps that chatgpt would independently take, like deciding what meetings to schedule, attending them, and presenting at them for example, and specify who would verify chatgpt’s correctness.
What an ironic comment.
Sorry, any early-career worker looking down their nose at anyone else (or pretending to have any idea what their job entails, especially because they “looked at a calendar”) might as well go back to middle school. They definitely need to grow up.
I say this with the perspective of someone who has slowly had to have many more of these meetings added to his calendar over the years.
Some are very important, some are reasonable but often bloated, but so many are a waste of time.
At the very least: they’re 5-10 mins of work spread over an hour. It’s occasionally maddening.
When I was really junior, I'd go to meetings and think that the vast majority of the time was wasted. As I became more senior, I realized that a lot of that wasted time is for providing context, relationship building, and alignment. You may not need those things for your current task, but your leadership and partner teams may need these things.
Yes, a lot of meetings could be emails, and a lot of meetings could be better run (agendas and objectives in the invite, action items assigned at the end), but unless you're working somewhere awful, most meetings probably have a reasonable purpose and aren't all filler. Lots of jobs require way more meetings, and probably aren't filled with context relevant to you.
Looking down on non-engineering positions is a personality trait I associate with inexperience. It's absolutely something I'd consider when denying a promo.
My entire point was that there is a major difference between the two & that while the instinct to look down on others for this organizational symptom is immature, it’s not unfounded or without basis to highlight the issue: they’re blaming the wrong thing however.
And I often find that in those types of meeting communication & relationship building is the absolute last thing that is happening. Most of these meetings are CYA, checklist, type meetings.
Meetings that literally only exist to allow someone to demonstrate they had a meeting about something.
Worse, the actual communication that is happening is usually in side channels.
Having good meeting culture requires everyone involved to improve it. If you want meetings to be better, set them up, add an agenda and objectives, and run the meeting so that it's effective. If you can't run the meeting, if it doesn't have an agenda or objectives, ask the person who created it for them. Ask for action items at the end of the meeting, if no one is calling for them. If it's mostly status meetings, propose a better process to track and communicate status.
If you're working through side channels, you're part of the problem.
Calling people assholes, rather than improving the situation, is an indicator of inexperience.
I’m actually impressed.
Call me in 20 years, maybe you’ll have learned something.
Assuming people are assholes, and blaming them for situations is just run of the mill toxic. Working through side-channels rather than addressing a problem is also run of the mill toxic.
Just because Joe or Judy "feels" a certain way doesn't mean it should actually have bearing on anything. Really...
Enough placating those with the least logic and self control.
People's feeling matter in the long term, because it's the difference between them wanting to work with you, and them being forced to work with you. If I had to pick between a genius coder with awful people skills, and an average coder with exceptional skills, I'd essentially always pick the average one.
Do you not see the difference?
Well that's absolutely not the place for it.
If your little fee fees get hurt you keep it to yourself and focus on the task at hand. Then after the task is complete you either pull the offender aside to address the problem or you bring it to a superior to be addressed. It in no way should have any bearing on the work at hand.
This is basics of work place decorum, right?
A lot of that seems to be about office politics, which historically been something which engineers and office workers in general has disliked. It is a generally unhappy fact that relationship building and office alignments is what dictate who get promoted, who get raises, who get the desired assignments and who don't.
It might be true that those who refuse playing that game is associated with inexperience. In my experience, employees who get tired of it generally leave large companies, which leaves behind only inexperience employees or those who enjoy the game.
100% agree. In early or IC roles, it's easy to think "just let me go do X" (or worse, "talking about X or Y is a waste of time when X is the obvious answer") without seeing the bigger picture that there's tremendous value in making sure other teams are aware of what X is, why it's important, and having a chance to weigh in or ask questions. Certainly there are valid complaints about some people's meetings, but those shouldn't overshadow the alignment/communication value meetings can have.
Its always us vs them.
Seriously, some looking down the nose comments
Is it better or worse to assume they're being a problem on purpose?
I won't say 'average' but I will say 'common enough to make changing software a huge issue'.
The person trying to make things better and seeks out knowledge at great cost
Or
The person who is willfully ignorant and actively refuses knowledge handed on a platter?
Because one of those is the typical IT pro and the other is the worker drone....
Show me a product that provides so much more value for my team than Excel that it would be worth a retrain.
LibreOffice, free open source software. Just as good as Excel and... free.
But yeah, for some things there are not yet complete free software alternatives, but the gap is really getting small these days. I think for most common use cases for most people, LibreOffice is more than enough. If you need more advanced features that are only available in the propietary variant, try to find ways to not be dependent on that feature, or find an alternative way to do it with free software. If you are creative, there are usually many ways how you can do your work using free software.
But yeah it does take some dedication to this idea. But what you get back is probably, on the long run, gonna be of more benefit to you for the future than if you would invest it in learning the propietary software. Unless you really have a special love for the propietary software company, and you are sure you want to grow more and more into their ecosystem and have no need to have any personal freedom over the software you use.
Here's the thing, for 90% of use cases, those are all effectively equivalent. You really shouldn't need any retraining whatsoever. A spreadsheet's a spreadsheet, and a word processor is a word processor. You type the text in the box and then hit print or whatever. Nothing new to learn.
Now admittedly, there are some power user features which are different, which is why I said they're only 90% equivalent. But most people don't use those anyway. Yet they will intensely oppose using a different but 90% equivalent thing because they haven't spent years being trained to use it - even though it's almost exactly the same thing they're using.
It's just a weird and bizarre mental hangup that seems to be natural to many humans.
If you're in tech, you will see the same thing with programming languages, frameworks, applications, etc. And it's on both sides, not just the users, but also the people hiring them too. "Oh, you've only worked with WordPress, you haven't been trained in Drupal?" "Oh, that's PHP, I only work in Python." "Well we're looking for a Ruby developer, not a C# developer." "That's React, I only know Vue.js"
It's mostly all general-purpose programming languages, libraries, and frameworks. Sure some details are different. There's a bit of a learning curve. But if you are actually capable with one, then picking up another nearly equivalent alternative should not be viewed as some impossibly complex thing that will take years of retraining.
There is a thing called "intelligence". There are several definitions of it, the one I'd like to use here is "the ability to infer general principles and common workings from small isolated samples and apply those principles and workings".
So if you are sufficiently intelligent, you can infer, from observing a few (or even one) doorhandle being pushed, that his is the general way to open doors. You can then apply this principle maybe even to different doors, windows, rotating knobs, etc. The fewer samples you need to learn and the broader your application range after learning, the more intelligent you are. In the stupidest case, one only learns to open one specific kind of door in one specific way, like a cat might.
You are writing from the point of view of someone sufficiently intelligent to derive the working principles of software and apply it to other software packages that generally serve the same purpose. However, there are people who are not intelligent enough to do that. Those people do get by by just following instructions, learning by rote which buttons to click for which purpose. Those people are the "door opening cats" of the office application world.
Less intelligent people like those do exist (50% do have an IQ<100 after all...), they do get jobs and they can be successful within limits. Just as Stackoverflow/ChatGPT-copy&paste-programmers do get by somehow.
Which is why I'm also a fan of intelligence-test-type job application processes. The ability to learn, for higher-level jobs, is far more important than preexisting knowledge. And intelligence is the best known predictor for the ability to learn.
Change purely for the sake of change is bad and people are right to resist it.
The vast majority of businesses have no compelling reason to switch off Microsoft Office. Would the world be a better place if there were more feasible options? Maybe. But that's not the concern of either a random business or its employees.
Home appliance repair is knowing the general layout of each major appliance, a bit of specialized knowledge on how to dismantle them without braking them, and which modules are responsible for which function, and finally knowing how to source the replacement parts and knowing which common items are best kept on hand for convenience.
Very few people are doing board level repair for appliances, especially when the replacemeent boards are typically very inexpensive for any modern machine (save for main boards and for induction plates in induction stoves, which are typically so expensive that it is smarter to replace the entire appliance rather than repair the broken module).
As long as you don't depend too much on highly vendor-specific stuff, most of the stuff a "cloud engineer" uses day-to-day is just the same fundamentally - EC2/Azure VM/GCE, ECS/Azure Container Apps/Cloud Run, Security Group/Azure Network Security Group/Google Firewall, whatever. Different names, same or very similar stuff.
There are certainly some cases where that breaks down, but it’s usually in specialized areas that I’d have to do some upskilling on in my preferred cloud anyway.
The benefit of the cloud is its service and resource (i.e. building block) oriented nature. There’s a level of transparency to cloud-based services that just didn’t really exist before.
I work here:
https://aws.amazon.com/professional-services/
I think I have a decent perspective….
Well, Lambda has a multitude of competitors (although to my knowledge they are only competing on the principle of serverless computing, so you'll still have to re-write scripts using these), and same for IoT integration.
The rest I'd say is pretty exotic stuff... and thanks for mentioning AWS Connect, that looks like something I'll have a deeper look into - do I get it correct that this is something like a combination of JIRA Service Desk/OTRS, some form of SIP telephony service plus a webchat and AI assistant?
It’s the standard type of software you use when calling into a call center with a mixture of automated help and operators.
Like I said above, if you know your specialty well, it’s not hard to map your expertise to AWS services. It took me two years from never opening the AWS console but having literally decades of software development/architecture experience to working at AWS in consulting. I worked at a 60 person startup before.
I’m more challenging the notion that all any of the cloud providers offer is a bunch of VMs and the surrounding networking infrastructure.
Granted, I'm biased because I work at a development-focused shop so my experience is the development/infra side of AWS and Azure as well as a healthy load of legacy on-prem servers (I leave my fingers off of GCP though, heard too many horror stories). We follow KISS - so just from a quick grep through our Terraform files it's almost all EC2, S3, Cloudfront, ELB, ACM, RDS, EFS, Beanstalk, ECS and EKS plus Cloudwatch for logging/monitoring, well wrapped in modules. That's stuff one can find pretty much everywhere, especially as most of our workloads are shifting to EKS.
The things you use are IMHO more targeted for specialist use cases, and I can clearly see the value-add... I'd pay good money to never have to see JIRA again in my life.
It seems very inappropriate to allow a data collecting tool to dictate what information is relevant for a specific company.
However, most young businesses will waste tons of time and money reinventing the wheel of these systems and trying to customize them to their business’ unique needs, but the much more effective path is to really (re)think through your business process and figure out how to align it with the grain of the tool instead. This option is only obvious to those with experience in failing to execute on the former option, unfortunately.
To your point, an effective analyst doesn’t just present data, they have to understand the entire world around that data - tooling, people, processes.
Lets say for example that you somehow make $120,000 a year over expenses with instagram (don't ask how, it's just an example). This is far more than you previously made in your last job by double. The problem is it takes nearly 100% of your working time to make this income on that single platform. Any less amount of effort and your income drops significantly. Now, you are in a trap where you cannot split your efforts between platforms, you have to go full in on one.
Your solution would be to make far less money... um, safely? Whereas a far more realistic solution would be to ensure that you don't live to close to the edge of your means and put 1/3rd of your income back in savings in case the day the platform fails/kicks you occurs.
So you could think about not operating as an individual who can be picked off, but operating in a collective way - either through friends, insurance, or unions.
ie what's your support network if you are dropped through no fault of your own.
When people are banned, it's the platform deciding the reputational risk of association isn't worth the money you bring in. Given reputation impacts can be huge - it's hard to see how you'd ever be the right side of that equation.
Even worse, the platform may decide it's not even economic to make sure each banning is fair....
Ultimately I suspect the only way to rebalance the balance of power is to use collective power.
So having large number of friends on the platform that will campaign on your behalf, taking out insurance ( another pooled method ), or even having formal Unions.
In essence that puts some of the economic cost of getting the decisions right onto the platform users ( as the friends/union does the work, and makes the case ). Pooled insurance has a similar economic basis ( platform users bear the cost of the insurance ).
As an example imagine learning programming - without some real world practice. And if you do some real world practice you have to choose which tool to use.
I take your broader point - but I think it's inevitable that most courses of this type are based around a particular tool chain.
Most Data Science courses use Python for example.
But I don't agree with the python comparison. Python is only a language and even Numpy/Pandas still need you to know the concepts and knowledge attained using them are definitely transferable.
All I'm saying, the fact that a course uses a particular tool chain isn't the determinant factor to whether a course is good or not.
totally agree here
>All I'm saying, the fact that a course uses a particular tool chain isn't the determinant factor to whether a course is good or not.
I totally agree! My comment was related to the commented mentioned that the whole 6 month training is worthless if GA get's blocked
I guess we aren't that far apart :)
Well before I even started my first development job, I had used BASIC, Turbo Pascal, Assembler, C, Euphoria, Java, C++, Javascript, and Visual Basic.
My first dev job didn't use any of those, however. I had to ramp up on PHP, SQL, Perl, Python, and a little Ruby. Took two weeks to become productive, albeit not a master.
Over the years since then, I've used a wide variety of other tools (languages, frameworks, compilers, editors and IDEs, etc.) I can't imagine where I would be if I still insisted on using BASIC and writing code like
10 PRINT "Hello!"
20 GOTO 10
In the end, they're all just tools to do the job. You don't refuse to use a screwdriver just because you learned to use a hammer first.
Imagine being a 'frontend developer' who can only use squarespace.
More likely: Imagine being a 'frontend developer' who can only use React.
We all need a door into this stuff, a place to be dropped in to start putting it together. Maybe the OP’s sister in law is totally out of luck, or maybe she’s now got a few of the hundreds of tools she’s going to need to build out a career. Luckily she has a brother in law in the industry, hopefully he’s the helpful type.
So sadly these things don't tend to go away, they just evolve.
Economically set back, maybe. "Useless" (with its implication of permanence) is way OTT.
I don't think it's permanent, but it does make them economically useless until such a time as they retrain.
Consider transitioning from Excel to LibreOffice or Google Sheets. On the surface it's the same, but doing advanced things requires considerable time investment and is very uncomfortable.
Silly hypothetical. I can't imagine a scenario where a company heavily utilizes advanced Excel, and then decides they want to use Google Sheets instead.
Besides, we're programmers, and learning new tools all the time. Things are deemed obsolete regularly.
I can't imagine a company that has built it's foundations on AWS migrating off of AWS. Such an endeavour would be more painful than transitioning spreadsheet tool by at least multiple orders of magnitude on basically every metric you can come up with.
That's also a broad definition of programmer. Most people (even programmers) come in a few categories:
1) People just solving a problem, tinkerers and explorers, people who are not really programmers first but it solves a need to get further work done.
2) People who just want a job that pays; lots of these, bootcamp folks mostly though I don't mean to make it sound negative -- nothing wrong with people that just want a decent paying job.
3) People who learned enough skills as teenagers to be well paid and are coasting or specialising in that area. I know lots of people like this, I believe on some level that even I am like this, though generally curious I tend to mainly focus on my area and only expand slighty around it and slowly. If you swapped out Linux for VAX I would be terribly displeased. See also: SystemD
4) People who love to learn about computers and how they work. This is probably the rarest person, and I was this person in my teenage years. It doesn't matter to this kind of person the economic viability of a project: the only thing that matters is that they do something. This is the people who make GameBoy Colour games in 2023. Or the people writing console emulators or doing DemoScene.
The majority of people don't keep learning, they learn their area and improve upon it.
I firmly believe that an AWS Cloud Engineer (or AWS programmer) would strongly prefer to move to another AWS shop.
Having used both I’d say that the differences between Unix and VMS are much greater than the differences between Excel and Google Sheets.
A better comparison might be between Linux and BSD.
Comparing something as vast and broadly reaching as "Cloud" is a disengenous comparison to something as specific as a tool like Google Analytics, kind of a wierd comparison IMO. The entire pattern of tech is towards the "cloud" - even if you refuse to use the big ones like Amazon, Microsoft, or Google, it's still technically "cloud" if it's managed servers (wherever they may be).
To be honest I never got into the hype behind Google Analytics and I'm glad that I never spent more than 5 minutes at a time dropping the occasional tag on sites I built. (I've also never worked for anyone big enough where the analytics ultimately proved useful or valuable anyway). These tags are now easy to remove by deleting a few lines of code. I really wonder if the larger orgs really should have spent the extra few hours / weeks of development to develop an in house solution all along...
Is it? Tons of cloud people I know are very narrowly specialized and certified on AWS or Azure. They certainly don't ever apply for jobs using the other...
I'm sure they could retrain. But I'm also sure they don't want to.
Heck plenty of people come into ProServe with no AWS experience. But they know their areas of specialty well and it only takes a couple of months to use AWS specific services.
I wouldn't blanket block a resume that said "cloud engineer", I'd just make sure to probe that they aren't just an "AWS engineer" or "Azure engineer".
A title I have frequently worked under is “Cloud Engineer”.
I’m strongest in AWS, secondly Azure. But I also am extensively using Linode’s platform and Kubernetes too.
My best friend’s title has also been “Cloud Engineer” and he is exclusively in AWS. He doesn’t really know more about Azure than he needs to get things connected to AAD.
How anyone could know that without asking eludes me. If you’re hiring for a position, you have a responsibility to know.
They use different jargon, they love to market themselves on their differences (because why compete on price?), but the fundamentals are really very similar and the skills transfer.
Anyone who’s telling you that Cloud X is vastly different from Cloud Y is either trying to sell you something, or has gotten their knowledge from someone who was selling them something.
Thank you for this. No more second thoughts about pointing cloud.example.com at our local HPE rack.
Off the grid Homesteaders aren't more profitable than people who engage in the compromise of society.
Data analytics has some statistics in it, these days probably a pinch of training ML models and using them and understanding them in the basics as well. Source: I did some work for a company specializing in creating courses for actually learning data analyst skills, as a preparation for switching careers towards data analyst jobs. I myself helped creating course content. The course is officially certified for job-seeking people as a means of learning a new job.
It's interesting to observe how the existence of a mediocre course in Sweden is leveraged to make the popularity of Google Analytics a major concern.
And maybe the course is not even that Google-dominated. Looking at the content here https://medieinstitutet.se/utbildningar/digital-analytics-di..., they use both Google Analytics and Adobe Analytics and mention other tools like Hotjar.
Just taking Google employees alone, a few *tens* of thousands of people depend on this tool. Millions of non-Googlers depend on the tool.
All that said, there are other analytics systems out there mixpanel, amplitude, roll your own, etc. they might not be quite as full-featured but 95% if the value comes from a few features everyone has
The argument for Universities right here.
I always find the opinion that Universities should make students job ready to be naive, even if well intentioned. There's a place for certifications that focus on job readiness, and there needs to remain a place that focuses on first principles and primitives.
I went to University about a decade into my career as a programmer to fill in the pot holes and absorb the first principles and primitives. I advocate that route every time I can. It's great if people can get a certification and start working with GA right away, and they have a place to level up their career with the money they make if they want to.
Those skills are very transferable to new products and very little of the worth I bring is from my certs
I also have a sysadmin background and my journey to the cloud has been "I can learn new things or go back to linux VMs at any time".
Most new entrants to cloud learn the following:
* a storage system (GCS, S3)
* A functions as a service (Cloud functions, Lambda) -- if you are lucky, cloud run.
* Maybe an orchestrator (GKE, ECS)
* Message systems (Pub/Sub, SQS)
* Some very minor information on how to create and access VMs; but it's clumsy, since you have to also learn Linux, this is unused.
For me, I can always fall back to my foundational knowledge of DNS, Networking, Linux and the systems I used to run, like databases, app services, mail systems, queue systems etc;
For people who are trained only on FaaS and SQS they do not have foundational knowledge to fall back on. That's not to say they can't get it, but it's not helping them make money and it's usually not taught, and worse: it's not something you ever reach for- and people typically learn through failure or by doing.
For me: Cloud just makes my life easier.
But I can also use an iPad as a consumption device; if I was only ever given iPads I would not be able to write C++ or Perl. That's just the nature of exclusively using simplified tools and abstractions.
Most people who are “devops” with <8 YoE are unlikely to have touched non-cloud systems. Worse still, whether you want yo admit it or not: some people are DevOps with no prior developer or sysadmin experience.
There are so many bootcamps for this too, and they mainly focus on AWS skills
You don't need certain skills today; instead you can use higher order systems instead. That doesn't mean there's no value in understanding (to use a programmer example) a linked list.
Equally knowing how a queue system works from the OS to bytes on a wire can make a world of difference in some contexts.
You can live in the higher order world and use the tools that make life simple (google analytics, in the case of this thread) but you are jailed to not understanding the systems that they are made from and while you are exposed to some concepts not everything transfers cleanly. "What is the PostgreSQL equivalent of a ML.PREDICT in Google Spanner!".
To give another contrived example; a huge reason people learn Latin or complete computer science courses is not because they will be speaking Latin or using Comp Sci concepts; it is because it sets a foundation for learning other systems, a sort of proto-field that permits you to see the relationship building blocks on which other systems exist.
Even if we would train them on first principle primitives, recruiters don't view it that way. That's even true in the software dev world. If you don't have 3 years of experience in Java, then it doesn't matter that you're a 5 years experienced software engineer in all kinds of languages.
That's an elitist perspective that doesn't include the average worker making a living by knowing their tools and not much else.
My personal situation is possibly the least background elite possible and even I know that first principles are important in a field that is shifting -- which happens to be most fields, just tech is a bit faster at churning.
Not quite the same, the core concepts and skills of a Cloud Engineer should be easily transfereable between providers and even to on-prem infra.
Data engineering could be another path to explore.
I'd view your sister-in-law's certification course as more of a first step than an end. It could open doors but still have to stay relevant with broader skills.
Completely agree. So it is their personal decision. It has been forever.
People getting Macromedia Dreamweaver certifications instead of web development, and so on.
The side effect is that for each of those tools, there's an army of people that spent years studying them, and will push them at every opportunity they can.
And interestingly, those tools keep being pushed at places even when perfectly fine alternatives exist that won't give you almost any of those problems and don't require any specialization.
Skills are very seldom tied to a specific product these days, so she will be good.
I don't bill myself as such, but I am basically a "Cloud Engineer". My expertise is in no way dependent on a particular cloud, and I've done work in GCP, AWS, Azure, Rackspace, and even a private cloud or two. A VM is a VM, Postgres is still (more or less) PG regardless of who is hosting it. Sure, there are specifics, but even cloud-specific stuff really doesn't differ too much, and it's pretty easy to find the common memes between the two. I can assign a role to VM in AWS, an IAM service account to a VM in GCP, and an "identity" in Azure. All 3 then permit the VM to make API calls to the respective cloud. All 3 fetch their access token in basically the same (but incompatible, of course) ways: HTTP request to a magic link-local IP.
A lot of the concerns I deal with, such as "can we survive an outage? what types?" depend on concepts like failure domains that apply equally to a cloud or to a datacenter.
But at some point, I had to dip my toe into a new cloud. I started a new job, and they used this thing called "Azure", and at that point, I'd never heard of it before. But you approach it with an open mind and the right balance of "some of my old knowledge might be relevant, but this new thing might also work differently and I should be prepared to build a separate mental model around it if the old knowledge is leading me astray."
… and I'd expect the same from someone doing "data analytics"; I'd expect something like "math is math, how I collect the data might change, what APIs I use to process it might change but the math is the same."
If a 6-12 month training has no skill transferable to another analytics tool, I strongly suspect the training was useless to begin with. Other analytics tools are not so dramatically different from GA that you'd lose all methodology on what to monitor, how to conduct a study, etc.
To make an analogy, you don't suddenly become useless if you move from Java to C#.
Going from Haskell or Scheme to Rust or even Python is going to take some time before you're completely comfortable with all the built-in's the standard libraries, the "pythonic" or "rustic" way of writing, tools and so on.
It's a lot of hidden things, you're not completely useless of course, but it's not like you write "production quality" code and have the ability to work completely independently or be an SME (like you probably were) within 1 month or even 2. It's a lot of little work to get back to where you were professionally.
Because it's not just a training course that is lost, it's all the incidental knowledge that was picked up on the job too.
(Also Haskell to Rust is pretty straightforward, the typesystem knowledge you learn in Haskell usually means the harder parts of learning rust are made easy. Having done that transition, 1 month is reasonable to be productive in Rust)
It's not hard at all, it's just that we have become too lazy and mentally dependent on big tech companies!
If all you want is user tracking, a few lines of JavaScript is all you need on the frontend. A popular WordPress plugin named jetpack gives you almost all data needed for site analytics, for example.
There are other tools too like tableau and python based tools like pandas and numpy which help you with all kinds of analysis.
Humble techies are everywhere with their tools, you just have to trust them a little bit, that's all! It's almost like trusting your Uncle Joe's pizza dude next door instead of the familiar Domino's or McDonald's. It takes a while but you'll eventually discover there's no difference.
Compared to something like a Cisco networking certification: The CCNA will cover practical use of their products, sure, but they're also going to teach you subnetting, both standard and Cisco proprietary routing protocols and how they work, in theory, as well as how to employ them in practice. I've mostly moved on from using Cisco products day to day, but all of the understanding was directly translatable to any other platform I've worked with.
On one level it's an important observation, on another it's mundane: DBAs will fight one another over Oracle vs DB2 vs SQL Server. Traditional bare-metal DBAs will fight RDS. C programmers are upset by Rust. People who invested a lot of effort in shell scripting for SysV init dislike systemd or s6.
The entire course (located on here: https://medieinstitutet.se) is based on Google Analytics.
Now her entire value is tied to the use of Google Analytics, she will almost certainly fight very hard to ensure that these skills remain relevant, nobody would want to retrain for 6-12mo on new analytics systems (or, god forbid, not be an analyst at all!).
I think we don't really assess the amount of lock-in we allow when we learn something that supposedly makes our lives simpler. Google Analytics was sold as a solution to you making your own analytics, because that's hard! and the cost is that google gets your information too- which most webmasters don't care about individually.
However now we're in a situation where at least a few thousand people depend on this precise tool existing, and will be economically useless if it is banned.
Personally I find this astonishingly foolish of the people who train exclusively on these tools instead of first principles and primitives.
That said; we also have "Cloud Engineer" as a job title, so I'm not sure we will learn this lesson.