Let's talk... about raw events, logs, aggregates and data structures. The meat and potatoes of computering.
What *is* an event? For the purposes of this thread, let's define an event as one hop in the lifecycle of a request. (Oodles of details here: https://t.co/wjTTlljGeV)
So if a request hits your edge, then API service, then calls out to 4 other internal services and makes 5 db queries, that request generated 10 events.
(If it made 20 cache lookups and 10 http calls to services we don't control and can't observe, those don't count as events...
... because this is all about *perspective*, observing from inside of the code. You can flip to the perspective of your internal services but not the external ones. And it probably isn't useful or efficient to instrument your memcache lookups. So those aren't "events")
Let's talk about influence. As an engineer, how do you get it, earn it, wield it, or lose it?
(The answer is NOT "become a manager.". In a well-functioning org, managers have mostly separate sphere of influence. If this is not true of yours, change it or leave.)
The way I think about this is by thinking of supremely influential engineers I have worked with, and how they amassed and used their power.
All of us have a place of authority we feel most comfortable leaning on. These can be loosely grouped into archetypes.
(I am going to avoid discussing the overlapping and interconnected issues of power linked to gender, race, and class, unless I get *super* ambitious towards the end. For now let's just allow that it's structurally much harder for some than others, ok?)
people often ask me for links where they can learn about observability. i often link to @copyconstruct pieces, the honeycomb ebook, my own stuff. but now i have a new favorite, because these slides from @dotpem's talk at @QConSF .. are.. 💣💥. https://t.co/sLTKrlbKVc
it's a rare set of slides that is funny yet informative, that tells a dense story visually without narration. @dotpem covers the origin story, the business case, metrics/logs/traces, sampling, even an intro to @honeycombio .. all without losing the plot. https://t.co/sLTKrlbKVc
it's so freaking gratifying and awesome to see somebody tell the story better than i do. i get way too down in the weeds sometimes. brb sprucing up my own slides with screenshots of nathan's ...
I've been saying jokingly for years that being CEO is a one way train to sociopathy. I'm not joking anymore: if you do it long enough and are even moderately successful, it's not *whether* you will manifest sociopathic tendencies but when.
I never, ever wanted this gig. I always wanted to be *CTO*. I knew CEO was a shit gig all along. Everybody shits on you and it's your job to sit and take it, and if you complain it sounds like gross, privileged self pity.
And consider the incentives:
You have to learn to be extremely stingy and selective with your emotional mirroring and empathy. You *have* to. Or you'll blow your budget for the week by Monday noon.
hey friends, forwarding on this 100% remote devops lead/manager role from @philfreo.
(caveat: I don't know him or them personally, but roles like this can be scarce and I applaud folks who are all in on distributed.) https://t.co/5tMQQNzTd1
this also gives me an opening to weigh in on something that has come up recently: are hybrid tech lead/manager roles like this one unreasonable, even impossible? or totally ok?
In brief: reasonable, with asterisks.
Jenessa Petersen @JPinTech
Let's Encrypt is looking for a Director of SRE! Remote as well. :) https://t.co/RaiRrRWK1n
what if ... you couldn't use the words "the best" to describe someone or something unless you also clarify ... the best at *what*, exactly?
what if ... for every word of advice you gave, you had to give at least ten words describing the context in which your advice was relevant?
the best thought experiments always start with my exasperated inner dictator. but i do have a point, back in a sec.