Adam Jacob Profile picture
28 Apr, 12 tweets, 2 min read
if you’re a leader, and you aren’t analyzing how you would act, and why, in the situation at basecamp, you’re missing a golden opportunity. Every step offers a gold mine of introspection.
How not to roll out policy changes? Check. Why you never bundle things together? Check. Public airing of dirty laundry? Check.
I like to believe I would’ve killed the names list the moment I saw it. In 2009 it wouldn’t have been because I thought it was racist (tho I see that it is now), but because you cannot have disdain for the people you serve.
One other observation - sometimes the job of a leader is to shut the fuck up and eat it. It doesn’t always matter what you think. Why run off about escalating? Why not just recognize that the list caused problems, acknowledge it, acknowledge the obvious complicity, and move on?
The answer is because some times it’s easy to forget that being the leader (sometimes) means suffering for the good of the organization. Basecamp has always been clear that it’s about the founders happiness.
It’s what they want, the way they want it. He didn’t need to poke that employee in the eye. He just needed to shut up, close a door, and talk to a therapist about his feelings. So everyone could heal.
He didn’t need to be right. He didn’t need them to agree. He needed everyone to put down the toxic rod. That starts with *him*, because he’s the only one with positional power.
By writing that reply to the employee, he prolonged the suffering. To no fruitful end! The list was going to be gone either way! All he had to do in that moment was not care about being right, and not need to be understood. He just needed to do the right thing in the moment.
So take it from me and from DHH - if you’re in leadership, and shits toxic, you have to drop the toxic thing, and then make space for people to heal - which probably means suffering yourself in private a little. It’s a small price to pay.
So I’m not misunderstood - “drop the toxic thing” - means acknowledging its toxicity, acknowledging your role in it, addressing what will happen next, following through consistently, and allowing people to vent and grieve. Except the leaders: they need to grieve in private!
Because pouring their own grief out, combined with their positional authority, only makes less space for the people who work for you to do the same. I’m not advocating total silence, or false appeasement.
But if you know it’s bad, and I know it’s bad, and we’re dropping the bad thing, that’s it for leadership. You *never* get to kick that shit down, or ask your employees to eat it for your comfort. Your job is to sit in the discomfort, and lead your people through their grief.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Adam Jacob

Adam Jacob Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @adamhjk

26 Apr
If I had to pick one thing I learned at Chef, it is this, even if you’re the founder. I had to turn it into a job, that I happened to love, with people I loved, but that ultimately was about the work. Not about my self worth. Just about doing good work, day after day.
Before I did that, everything was multi layered and fraught. I was harder to work with, much more volatile, and sometimes capricious. I’m a little that way by nature - but when my life is all tied up like that, it was so much worse.
Once I realized it could be work - everything got easier. My decisions, my feelings, my friendships. listen to Emily and Jill. Make your work be about your work. Free yourself to find pride in it, but have it be a part of your self worth and life, instead of the opposite.
Read 4 tweets
15 Feb
The more time I spend in software development, the more I feel like everything hinges on architecture that is flexible in the face of new understanding about the domain. Too much architecture too soon means discovery slows down. Too little later on and the system can’t evolve.
Trying to do TDD without a firm grasp of architecture patterns is like building your own straight jacket. But then later, under testing the architecture means you’ll never be truly stable.
It’s a constant balancing act between over architecting and under architecting. The answers change with the code base, and with the teams, and ultimately ideally with the richness of our understanding of the domain were operating in.
Read 9 tweets
6 Dec 20
This misses the point wildly. There aren’t different understandings of what open source means. There are people who want what they want. If they still can get it, they’re usually fine with whatever.
That’s why we buy software, use Twitter, whatever. Most of us aren’t open source zealots. We’re just people with a job to do.
So it’s not surprise to me that a bulk of @graylog2 users, especially customers, are fine with this. They’re not in the class of user who is affected!
Read 14 tweets
6 Dec 20
When you think you get to define what an important software term means, because you want to retain an advantage - I don’t care what you believe. Just because you say the sky is purple doesn’t make it so. Gross. Do better, @graylog2.
To be clear - like it or not, open source is defined by OSI. As a community we rely on it. We need it, so we can trust what liberties it grants. I’m on the side of there being a more open discussion - but just saying “we think it’s okay” is some bullshit.
You know it’s not. You wanted the non-compete part of the license more than you cared about it being open source. Own that shit. Stand up for your principles.
Read 5 tweets
3 Dec 20
@webframp Ok! Basics first. F1 is a constructors sport. Each team must build its own car, from scratch. They can use listed parts, outsource some, but the design and build has to be done in house by the team.
@webframp That means the team often can build the car around the driver. They give feedback on how it feels and behaves, and the teams change and adapt over time. It also means each teams car is unique to the team.
@webframp The cars themselves have no driver aides allowed. No power steering. No traction control. If you’ve ever driven a rear wheel drive sports car with no assists, I’ll tell you: it’s difficult. You have to pay maximum attention all the time. They’re absolute monster cars.
Read 25 tweets
2 Dec 20
There is a market opportunity for an alternative to k8s. You won’t “beat” it, but you don’t have to. You just have to decide to compete. Right now nobody even tries. Nomad is closest, and even their marketing is complimentary at heart.
To be clear - I’m not building one
Also, it’s not because k8s is bad. It’s because it’s such a success, the groundwork for the market is laid. People don’t question its place in the stack. They do question the implementation complexity. Operability.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!