I realize this take is white hot (I anonymized the OP to minimize my blast zone), but if this is you, the vast majority of the time, you probably shouldn't have gone CEO.
Lemme explain why (and it's possible the OP is NOT one of the people I'm talking about).
When you're an eng-gone-CEO who feels this way, a lot of things have happened to you.
1. You probably got rewarded for being good at coding by being promoted out of it. Then you were in a job you were LESS good at. This doesn't feel great.
2. Turns out CEO isn't the same as monarch or president-for-a-day at most companies. It's a lot of delegating decisions you'd like to make yourself, and when you fail to do the delegating step it tends to blow up in your face.
Both these things suck and as a result...
For these people, it takes IMMENSE willpower to NOT hop back into code.
Most of the people I've seen in this position, real talk, don't have that willpower.
Which is a shame because when they hop back into the code, here's what happens.
First of all, they never pick that one bug no one wants to touch and apply their experience and tenacity to making all our lives easier.
They usually pick some giant-ass pet refactor of theirs.
Then, one of two things happens.
1. (most common) the refactor gets halfway done and/or they get stuck. Why? Because they're out of practice and decided that what they needed to do was come in here and take on one of the hardest engineering challenges there is...WITHOUT BUY-IN.
Now, it's some poor eng's job...
...to remove themselves from the priority ticket they SHOULD be doing and fix a poorly-executed, half-done science experiment because someone way up the power gradient wanted to have some fun.
2. LESS commonly, the CEO succeeds at getting the code working with the change in place.
However, they still never established buy-in or transferred context. So they set shared context on fire directly in front of the professional software engineers who need it to do their jobs.
And then they want praise for this.
If you want to trade jobs with your engineers this badly, either:
1. Find a side project, work on that AFTER you've done a good job being CEO, DO NOT F**K WITH IT on work hours, do not try to use it for cool points with your team
OR
2. Step down. Get hired as an eng ELSEWHERE (you can't undo this power gradient). Find a therapist to address the issues you have with the idea of abdicating the aforementioned power gradient.
Spend your work days doing the thing you're good at and want to do.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So my FIRST hot take is that, in the 6 days I spent on blind, I saw some of the most insufferable, elitist drivel I have ever seen techies say behind closed doors, and that bar is not low
LOLOL at this Blind rant where the person signs off "TC: 400" like it's fucken "Esq"
Lotta devs are convinced that their total comp means something about their intelligence, skill, value, or impact
When really it's mostly execs' success convincing VCs that they'll make money someday
Leading w your TC is the "peeling out in a muscle car" of engineering
This take responds to a tweet re: the CDC's reduction of the time guideline from positive test to return to work, with more cuts foreshadowed "[to address] staff shortages."
I've heard this clarion call before. There's something that I think the people who make it are missing.
So, I'm not saying that the take is wrong or bad.
I WILL say this: I have answered this clarion call before. I have showed up to DS meetings for 3 different orgs. I have showed up to trainings and movement-building meetings in this vein of various kinds.
In them...
...my experience at socialist organization meetings has been that they are universally, consistently, and by a wide margin some of the most uppity, sneering, un-empathetic, yell-over-each-other-y spaces I have ever visited.
For me and my low caucus score, it's an immediate nah.
Tech books exhibit a strange cost bell curve relative to quality.
Expense-it-to-prodev priced books are consistently fair-to-middlin'. Accessibly priced books, a standard deviation above or below that. Free books, either TRULY shite, or the best tech writing I've ever read.
My hypotheses on why come from my experiences:
- planning books with big publishers
- hearing from published author colleagues
- getting pitched on self-publishing
- self-publishing for reasons totally unlike the pitches
Here they are, in all their half-baked glory:
1. Books from big publishers
I won't name names, but if you've been around tech, you know who this is. These are the places with the highest price point. It's that high because they expect people to expense it to their employers. These places have a lot of name recognition, and
I am 9 minutes into S6E3 of Lucifer. Why is there a new angel? Shouldn't we have met all the angels by/in the S5 finale?
Anyway, I guarantee you this one's a lesbian. I am 110% certain.
And BY THE WAY, I was already 75% certain based on that two-second shot of her feet in S6E1.
I'm also just gonna repeat what I said eons ago about how obvious it is that all the heaven-dwelling celestials in this show are het and all the queer celestials are hell-dwellers. Like, I get that it's cable TV but that's still f'd up, it's 2021 people
So a Worldcon guest tweeted that U.S. defense companies can be ethically "grey" despite, uh, getting paid to orchestrate killing people.
The evidence: the OP's partner works at one; the OP used to work at one that helped w the moon landing.
I'm not here to drag. Let's talk.
/1
FIRST THING FIRST: I'm not sharing the screenshot because I believe it is unfair to share people's de-anonymized hot takes without notifying them or linking to where they might amend. That's closer to lashon hara than accountability and that bothers me.
On to the take.
/2
I've watched something like this play out pretty often in tech: a person thinks of themselves as a good person, or they are dating an ostensibly good person, and that person works for a company that does bad things.
So now they have to back-justify what's happening.
/3