I mean, it's there any genuine case you can cover with SO that you cannot with your favorite LLM?
Because where a LLM falls short is in the same topic SO fell short: highly technical questions about a particular technology or tool, where your best chance to get the answer you were looking for is asking in their GitHub repo or contacting the maintainers.
I wondered once about this, but it kind of make sense from the point of view of usability.
Unlike any webservice, you usually have very few attempts to make a successful login before getting locked out, so even if it's four digits, the odds of a successful brute force attack are very low
I'm in the process of considering a change, still not actively applying, but I do get several LinkedIn DMs every week from first party recruiters. I don't work with third party staffing agencies.
There is a common theme: they are looking for leadership roles with active contribution and with deep expertise in the tech stack used by the company.
So, where's the issue here? IMO, the market is saturated with generic software engineers, that is, people who can code, who are good at leetcode, but who really don't stand out of the crowd in any particular technology. That's your typical FAANG engineer. And don't get me wrong, there is a lot of talent in FAANG, but most engineers commit to the grinding to join and then just coast through.
And related to that, there is the unrealistic expectations game. As others have mentioned, people in FAANG were living in their own bubble of unreal financial compensations. Now that the bubble exploded, some have unrealistic expectations that decline even high offers just because it's not what they had before.
Tumbleweed was the last distro I used for a PC before I switched to macOS back in 2015.
Back then, it was already better than any other distro in terms of balance of stability, usability, and being up-to-date. Most similar was Debian Testing, but OpenSUSE's Tumbleweed was way ahead in providing a stable environment.
It's funny that you asked this, because just the other day I was thinking about starting a series of posts about it, but then I thought "what the hell, it's 2023, everybody should know about how to use Docker already" and diminished the idea.
I'm not sure why this is even on the front-page now, given that it's been released for many years already, but in any case, here's my two cents about this topic:
Containers are a misunderstood technology. People think about them as a privacy feature, but that's far from real. The only benefit of containers is the ability to have different sessions of the same service in the same windows/profile. That's it. A good use case is when you need to work with multiple AWS accounts.
Cross-site tracking is already enabled by default since... 2018? So, using containers as a way of dealing with cross-site tracking is utterly unnecessary.
I used to use dark mode every where because it was somewhat accepted that the lesser bright the better.
But then I read a science-based post years ago about why light mode is better for our eyes, especially for people with astigmatism, as our eyes are naturally used to focus on objects on bright scenarios (sunlight).
Switched back to light theme right away, except for coding, because actually syntax highlighting is better with dark background.
Have a look at physiological sight, explained by neuroscientist Andrew Huberman.
Basically, it consists on doing an inhale following by another quick inhale, and then a long exhale.
Theory says that you repeat that pattern 2-3 times, and your stress is drastically reduced for whatever reason I don't remember right now, but he explains it very well in his podcasts and as guest in other podcasts as well.
first you would need to define what are you want to focus on.
for offensive security, it boils down to discover (and get credited) vulnerabilities in other services, or to have certifications (which IMO are unworthy, but as you said "worthy of a mention on a resume"...).
for application security, you can follow the same example you already mentioned, but focus on security topics. Work on authentication and authorization, secure communications, etc.
for blue team, it's hard to have something worth of mention on a resume, unless you have some talks, a podcast, blogs, etc on this topic.
This guy randomly appeared on my Instagram feed, and since then, he has become a must follow for me, because his content about communication is just amazing.
I mean, it's there any genuine case you can cover with SO that you cannot with your favorite LLM?
Because where a LLM falls short is in the same topic SO fell short: highly technical questions about a particular technology or tool, where your best chance to get the answer you were looking for is asking in their GitHub repo or contacting the maintainers.