Here we are, now going on the fourth straight month of headlines all about how a record number of people are quitting their jobs.
There's a lot of pain behind that statistic, but also a strident, activated edge to labor that feels unlike anything seen in my lifetime.
I am *all for* more people quitting their jobs. I am *all for* employers needing to compete for employees by treating them better, increasing their wages, and offering more flexibility and support.
Most people in our industry stay at jobs they don't love, far too long.
So here's a piece of advice that I find myself giving over and over again, to senior folks who are daunted by the prospect of having to go out and search for the right role, the right team, the right company ... it's like looking for a needle in a haystack, right? 😰
You're right, it's super hard and time consuming to sift through companies, research them, interview, backchannel, etc.
So don't do that! Instead of looking for the right company, make it easier for the right companies (and recruiters) to find ✨you✨.
Yes, it starts with LinkedIn -- you gotta go where the fish are. Make sure you use enough of the right keywords, emphasize the skills you want to build, make sure it represents you well (and is friendly to skimming). Solicit feedback on your profile from people you trust.
Next, write or speak about your areas of expertise. If you're a database person, write up the story of your most recent migration, or open source a tool and write a medium post about how it saved your team time
If you love containers, write an opinion or a tech piece about that.
If you're trying to move from onprem to cloud engineering, explore some tech and write a medium piece about it.
If you're a manager, write about your experience learning to manage teams where you aren't the expert, or write a review of one of the recent tech manager books.
Any decently sized medium post can then be turned into a good meetup talk. Give it a couple times, share the slides.
It doesn't have to consume your life. You just have to generate bread crumbs for the rest of the world to find you for what you're good at.
Any recruiter or interviewer who googles your name -- what are they going to find on the first page? Hopefully, it's evidence of your expertise in the areas you want them to hire you for!
External links are powerful social validation that you know your shit.
The more you share about your passions -- what you hate, what you love, the kind of work you love, the teams you love -- the easier it will be for recruiters and companies to find YOU.
That's their job, and they're pretty good at it. You just need to give them a little help. 💫
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I was just editing the o11y book chapter on build vs buy and ROI, and this sentence jumped out at me:
"High-performing organizations use great tools."
It's true, right? Behold all the FAANG engineers who leave their cushy perches and are shocked by the amount of tooling they had come to take for granted. It's almost like having to learn to engineer all over again
Big companies know how critical good tooling is, and pay for it.
I'm going to say two very contradictory things, both of which are true:
1) Tools are getting better and better, and you should try to keep up
2) Switching tooling is hard, and you should only do it when the gain is ~an order of magnitude better than what you've got.
You don't owe it to your employer to fix all the ways they are fucked up. Before going to battle, ask yourself:
* how much power do I have here?
* is the problem within my domain of responsibility or influence?
* who are my allies?
* do I have a reasonable chance of success?
and also: are they worth it? Is your employer fundamentally worth you staying and fighting? Is their product a net good for the world? Are your leaders decent, ethical people who care a lot?
If so, sure, pick some battles. See what happens. ☺️
Ah! This is a very good point. Good recruiters are outnumbered by bad ones, which are indistinguishable from spam. And yes, the more you put out the more you'll get.
This is 100% true. What always jumps out at me is that there's always "the tracing expert(s)" that everybody goes to for help on the rare occasions when they need a trace. Fluency rarely transcends the few to reach the many.
I don't think it's this so much as it is that ... tracing is *inherently* a niche use case. A tracing-first approach to observability turns the world on its head for no good reason.
What most people want is the ability to slice and dice their requests,
Ostrich effect: ignoring an obvious (negative) situation
IKEA effect: The tendency for people to place a disproportionately high value on objects that they partially assembled themselves, such as furniture from IKEA, regardless of the quality of the end product
and some delightful ones that I failed to work in:
Zeigarnik effect: That uncompleted or interrupted tasks are remembered better than completed ones.
Tachypsychia: When time perceived by the individual either lengthens, making events appear to slow down, or contracts
the answer is no, we can't; there were no off the shelf columnar dbs, let alone any with flexible schemas or the rest of our wishlist.
if we had shoved it in an existing data store we would have looked and felt just like every other monitoring tool. same perf, same tradeoffs.
the VC's were right too, though; we did almost doom ourselves. 🙃 it took us nearly a year before we could even really start signing up users or BEGIN working on the product. it was 2.5-3 years til we found PMF.
meanwhile our seed investors gave up on us long before that.