I recently made a career transition from SWE to DevOps/SRE role. The big difference is tooling - IaC tools like terraform/ansible/chef is a must because automation is key. Those are also like scripting languages (declarative/procedural) instead of OO.
Generally requires a different thinking too - when you develop code on localhost you can ignore all the networking constraints, monitoring, logging etc.
In a production system those components are critical, so the focus becomes more on understanding how the full system functions, rather than just the business logic of the code.
A lot depends on experience but I think in general it's better to move from Dev -> DevOps than from Ops -> DevOps. Especially now that IaC is the primary tool that you would use.
Markets are highly volatile and largely driven by emotions. The impact is not yet fully seen and will manifest in the next 6-12 months. In the short-term, cash is the most valuable asset. In the long-term, it doesn't matter as much.
That's basically what every white-boarding coding exercise is - pattern recognition based on computer science trivia. It's not illegal - every tech company does it.
Strict IQ tests will select for a certain subset of the population, that's usually divided by socio-economic lines which highly correlate with race. That's not to say that certain races have intelligence correlations, but that IQ tests test for knowledge that is diffused along socio-economic lines.
You can look at white boarding as proxy IQ tests or aptitude tests, the latter of which are customized for the role in question. I'm on the fence when it comes to deciding which bucket white boarding falls into.
I see the parallel you’re drawing but in this instance it’s important not to. IQ is divisive precisely by being made synonymous to performance in every other task requiring abstraction.
Either option seems pretty good. But it may be that option 2 is the best, if you can still find time on the weekends/evenings to work on the open-source projects
``Strong opinions that are often wrong. This coworker is senior and has worked for some high-profile SV companies so the words carry weight.``
That may be your opinion. What defines a wrong opinion? If he is senior and has worked for high-profiles companies then he probably has experience, and has produced some results. The fact that someone has a different opinion from you doesn't mean the opinion is wrong.
Point taken. However, saying "X app connects to Y app, that's for sure" when that is NOT the case is wrong. Period. Facts are facts.
"We should do X because things are like Y" when things are like Z, you just have to check the code and show it, that's a hard fact.
Maybe I should have said "remembers facts incorrectly" instead of "opinion". Sorry.
Re: having worked in a famous SV company doesn't mean everybody should get a free pass to say B.S., right? I'm sure your FAANG company isn't made of perfect human beings (or has a perfect hiring process).
> mean everybody should get a free pass to say B.S., right?
yes, but you should accept that this is not a purposeful action and it is because of a mental state condition.
There are a few things to consider:
One is - the point of diminishing returns.
From my personal experience (which would depend on the geographical location and one's spending habits), that point is at about $100,000. In my 9-year career path I went from $40,000 -> $60,000 -> $85,000 -> $90,000 -> $100,000 -> $120,000 -> $120,000+.
The change in general appreciation of the raise that happened below $100,000 felt substantial, it almost felt like it made me happier.
But once you reach the level where you can comfortably spend and save large portion of your paycheck, additional $n,000 starts to matter less and less. Sure, it's a good feeling to earn more money, but it doesn't define your happiness anymore. It's become a norm. So going from $150,000 to $200,000 feels so unfulfilling compared to going from $50,000 to $100,000.
The other thing to consider is comparing yourself to others. We all do that to some extent. But if it's an obsession then one will always be unhappy.
The thing to realize is there will always be someone who makes more money and lives a wealthier life.
Here's how it goes - if you make $60k and live in an apartment complex there's some neighbor that makes $80k, and drives a newer BMW than you, has a bigger apartment and newer grill.
Then you get a raise and make $100k, you buy a small house in a different neighborhood. Once you settle in you will start to notice that there are neighbors that have bigger house/drive Tesla model S, have bigger backyard.
You get another raise and start making $200k, you buy a 2500 sqft house in a different neighborhood. There, a few neighbor(s) make $500k, and drive Lambos.
Then you work hard, and you start your own business and it becomes successful, and you start pocketing in $500k, and buy a Lambo yourself, and also move to a beachfront house.
Then there're beachfront houses that are bigger than yours, and some neighbors have 5 supercars.
Then your business grows, and you start making $2M a year, and you upgrade your beachfront house to a bigger beachfront house, and buy 5 supercars.
Now there's a neighbor that has a few luxurious villas in different states and internationally, then there's another neighbor that has a private yacht, and another one that has a private jet. There's another one that has 3 private jets, then there's another one that owns a football team, and so on...you get the point.
Chasing specific amount of money that would make you happy will ultimately leave you unfulfilled because in comparison to other people there will always be someone who makes more.
Of course, there are exceptions to that like - Zuckerberg, Gates, other billionaires - but being a realist how likely is one to become a billionaire in a lifetime. I mean, if that's your ultimate goal - good luck. But something tells me most billionaires didn't have a goal in mind to become a billionaire, it wasn't their primary focus but rather a byproduct of their success and passion.
Generally requires a different thinking too - when you develop code on localhost you can ignore all the networking constraints, monitoring, logging etc.
In a production system those components are critical, so the focus becomes more on understanding how the full system functions, rather than just the business logic of the code.
A lot depends on experience but I think in general it's better to move from Dev -> DevOps than from Ops -> DevOps. Especially now that IaC is the primary tool that you would use.