They’re referring to this thread, which has been going around in coding circles. It’s highly entertaining. These kinds of technology “war stories” usually are. But we do have to ask if it was at all necessary.
I hesitate to share these kinds of stories these days. Because I realized that while they are interesting to hear, they are not fun to live through. It’s actually a story of a bunch of people being damn near run into the ground for the benefit of their employer.
I have a story like this of my own. But I don’t look back on it fondly. It was one of the worst experiences of my life. What I remember is sleeping on a couch at work for about 3 hours before waking up and getting back to work. And this was days before Christmas.
The next day I delivered an ultimatum to my boss. I said once we shipped this version, that was it. If it didn’t work, someone else was gonna take over. Either we went back to normal work hours or I would quit. I was ready to get “resignated” as it were.
That didn’t happen in this case. The version we shipped worked for the most part. But you know what me and my team got for all of this hard work? I don’t remember. I won’t say we got “nothing”. But clearly it wasn’t enough to remember. While the trauma is still sharp in my mind.
I tell this story for all those folks who are gearing up to argue. “But Uber went public. Those engineers are probably rich now!” That may actually be true for some of them. But this happens at *every* software company. And they definitely don’t all turn out like Uber.
I’m not gonna tell anybody not to make a big bet on startup equity. It has paid off for me in the past. And I’m still doing it. But you won’t catch me breaking my back for it. Our goal should be to make smarter decisions and not dig holes for ourselves.
Whew, y’all gotta read this thread. It describes one of the common dysfunctions in tech startups perfectly.
Specifically this. A lot of people in tech think what we do is about code. They treat code as synonymous with value. But in most cases, more code is a *liability*. If you can get to the intended value with less code, you are winning.
The challenge is making sure people don’t underestimate the value you created just because it doesn’t *look* difficult enough to them. @mekkaokereke has a great thread that is related to this.
Economics just isn't this simple. I wish that people who wanted to use this simple definition would admit that they're incentivized to do so because it benefits them in their current situation. It's okay. Just call it what it is.
Many employers are absolutely selling a lifestyle. Why does it make sense for an employer to upgrade their healthcare plan when the actual work hasn't changed? Because it's something their employees value and raises their standard of living. It makes the company more competitive.
Why does it make sense for a company to move to open a new office in a different location or even relocate the whole company. Part of the calculus is always that folks in that area will accept less money because they can still achieve a similar lifestyle there.
"...even with artificial intelligence and third-party moderators, the company was 'deleting less than 5% of all of the hate speech posted to Facebook.'" buzzfeednews.com/amphtml/ryanma…
"The implicit vision guiding most of our integrity work today is one where all human discourse is overseen by perfect, fair, omniscient robots owned by Mark Zuckerberg."
That's a hell of a sentence.
I was debating this with @operaqueenie. She says facebook is a big problem, but not the only problem. And I found myself making a very passionate case that, yes, Facebook is the *whole* problem. Not the tool per se, but the power it wields and how it wields that power.
Having a place to post this is seriously the only reason I spun up a new blog. If I could have one single idea take hold in tech management it's to stop talking about project updates in 1:1s.
Let me be clear though. You need to talk about project updates. In fact, you probably need to talk about them more often. I see a lot of places where they are locked up in short 1:1 conversations. Change your process so you are hearing them all the time in other venues.
Get project updates out of 1:1s and you'll have room for much more important conversations with your individual direct reports. If your org is stuck in update mode, it will take some time to make this shift. But you will be glad you did.
I hear you Jon. But we're not gonna pretend like this is a Trump thing. This is white America and has always been. You're just taking this opportunity because it's particularly bad right now and you wanna use it to punish Trump. I get it. But you can do better.
Please do use whatever rhetorical tactics you can to blast Trump. But be careful that you're not just describing how America has always worked and only pretending it's bad today. And more importantly, make sure you're gonna still be mad about it after Trump is gone.
These things Jon describes, where powerful people profit off the harm of others while giving themselves advantages, is at the very core of how America works. We have accepted that way of life for centuries. Trump does it with glee and forgets to pretend at decorum. That's all.
You can learn a lot by really examining what is happening with Timnit Gebru. Both how she was used to bolster Google's brand and credibility and how she was ultimately sacrificed when she wouldn't fall in line.
I'm really interested in hearing from Jeff Dean. The Google exec who Gebru says is responsible for backstabbing her. Because here's the thing. He could be a villain. Or he could just be an example of spineless white men who follow orders to destroy PoC when we don't behave.
I'm only talking about this explicitly because Gebru has decided to share her story openly. Keep in mind that what she's doing can and probably will be incredibly damaging to her. But we have to start standing our ground against this kind of villainy. This is how things go bad.