This is a silly article really. If a company looks for a specific skill set like Docker or Kubernetes, I think the company is hiring people who would become irrelevant after 5 years because you never know what newfangled orchestration tools would be the "right way to do it" then. Fortunately, companies do not hire in a silly way like this. Sure they write "Kubernetes" as one of the many things in their job descriptions but all companies I have interviewed with would be equally okay to hire someone who demonstrates strong Docker skills or strong sysadmin skills or even strong OS skills.
These skills are transferrable from one implementation to another. It makes no sense in this age to put all our eggs in one Kubernetes basket to be hireable. Expertise of the underlying computer science and engineering is far more important.
> Many websites and services require two-factor authentication (2FA) or multi-factor authentication (MFA) where the user is required to present two or more pieces of evidence: • Something only the user knows, e.g., password, passphrase, etc. • Something only the user has, e.g., hardware token, mobile phone, etc. • Something only the user is, e.g., biometrics.
Apart from mobile phones using fingerprints to unlock, are biometrics used in any mainstream MFA? Are there any websites, services or companies that accept passwords and OTPs also accept biometrics for authentication?
And transmit it!
Biometrics are useless for remote 2fa. They only even make a little sense when used for immediate local hardware interaction. From a remote perspective you can't authenticate biometrics versus a replay attack. Hardware does it by literally being hardware and thus has high confidence it is talking to the real sensor and you will note all the phones require harder authentication on boot before enabling biometric authentication.
Right from my school days I've been involved in all layers of developing apps - assembler, C, Java, HTML, PHP, Django, databases, HTML/CSS/JS. Many years before this "full stack developer" popped up, I never thought being involved in all the layers of developing apps needs a name of its own. For me it was just being able to do both frontend and backend.
So when "full stack developer" roles first begin to pop up in the industry, it left me very confused. Why a whole new name for it? How exactly is it defined? Am I a full stack developer or am I not?
IBM's comp isn't very good at any level, but they also don't hire much in super-high cost-of-living areas. Here in the Boston area I've only started making more than any of those entry-level salaries in the last few years (I'm 32) but don't live somewhere where buying a house is a pipe dream.
The real reason IBM has trouble attracting talent is that they have no idea what they want to actually be doing, from a technical perspective. They are a sales organization, and that's all that they are to anyone in a position to make decisions about anything. I took a bit of a pay cut to go to IBM--I needed to get out of consulting because it was impossible to get a bank to verify income for a mortgage--but it wasn't drastic. Even setting that aside, though, IBM was the worst mistake of my career. I left in five months because the job was so stressfully do-nothing (if that makes sense?) that I could literally feel myself becoming a worse person, not in a "technologist" sense but that of a human being, by being ground down by that culture.
That’s a pretty big difference, but it would also be interesting to know where these positions are located. The cost of living differences between SV and outside of the Bay Area is pretty substantial, making these absolute number comparisons a bit harder to interpret.
Quickly putting Apple's (assuming Bay Area) $161K into a cost of living calculator says that's equivalent to $82K in Cincinnati, OH. (You'd need to make $82K in Cincinnati to maintain your standard of living.)
So yeah, I'd say that adding locations is required. I'm not sure where the majority of the IBM software engineer jobs are?
IBM is all over the US (much much more locations than others mentioned here) and it's also split into two: product and consulting. Consulting get paid less and bring down the average but people choose it for location and project variety
Yeah, a significant chunk of IBM's workforce works remotely. So they don't have to pay cost of living for Seattle or SF. Much of their American workforce that does report to an office is in much lower COL areas like North Carolina or upstate New York.
IBM has a legacy of a more diverse approach to developing technology. They also employ more folks who are applying software solutions vs. developing technology. When I worked with IBM stuff alot, the onshore developers were in Austin, Minnesota, Florida, Toronto, New York (including ex-NYC NY) and other places.
When I had IBM folks working for me in ye olden days (not subcontractors), they weren't working in the valley, and were perfectly good at what they did. They made about 30% more than the full time employees did, in exchange for living in Hilton.
Big tech is the way it is because right now they have access to unlimited money. The good times will roll until they don't! As things mature, the era of $160k college grads and $500k+bonus staff engineers will end.
Without reference to cost of living where that salary is applied is rather meaningless. 160 in the South Bay is not very good. 95 in Minnesota might be a lot more.
160 in the South Bay is significantly better than 95 in Minneapolis, at least. Unless you want to buy a house. I lived in Minneapolis not long ago and the major cost differences were really only housing, gas, and electricity.
Presumably Google's "entry level software engineer" at least on paper is a more advanced position than equivalent titles at other companies. We all probably know "experienced" programmers who wouldn't even make the cut.
> You mean like that crufty thing called homebrew?
What kind of problems have you faced with Homebrew? Can you please elaborate?
I use Homebrew all the time and it just works for me out of the box without any issues. I never had to edit configuration files or customize anything to make it do the right thing. It just works.
These skills are transferrable from one implementation to another. It makes no sense in this age to put all our eggs in one Kubernetes basket to be hireable. Expertise of the underlying computer science and engineering is far more important.