JB Steadman (@jbsteadman) header
JB Steadman (@jbsteadman) profile picture

Immigrants belong here. Muslims belong here.

San Francisco
Joined March 2009
Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)Photo by JB Steadman (@jbsteadman)
Any theory of team-building that has a “no juniors” requirement is both wrong on the facts and wrong on the ethics
I've managed fully remote engineering teams for ~7 years, from small teams to rapidly growing orgs spanning 10+ countries. I've developed some pretty strong opinions about what makes remote work actually work: <rant> 1. YOU MUST GET "THE TEAM" TOGETHER ONCE A QUARTER, NO EXCEPTIONS. The faster the team/company is growing, the more critical this is. If you follow no other piece of advice follow this one. Remote work is built on a foundation of trust which for most humans can only be built in person. Think about a person you know well who has extremely dry humor. Would you be able to detect that characteristic if you met them for the first time over SMS or slack? Bonds are built over dinner, a beer, an in person hackathon. And those bonds carry forward to the rest of the time spent remote. **for some definition of "the team" - can be a mix of immediate team, org, company-wide, all are useful at different cadences. 2. Managers must be pros and must be highly technical. Many non-technical managers rely on lazy half-ass signals like "who left the office last". As a remote manager you literally have no option other than to inspect the concrete outputs to understand what is going on. This tip is also very useful to non-remote teams 🙂 3. No juniors except for exception cases. Exceptional cases are obviously exceptional. Gotta build the muscle before you play on hard mode - for mere mortals at least. Don't expect someone to learn "how to remote" and "how to engineer" simultaneously. It is too much. 4. Establish a physical center of gravity, ideally 20-30% of staff. Company can still be fully remote and have "an office" where company events are held, some fraction of local employees cowork once a week even if on different teams. 5. Regardless of critical mass, all meetings must be remote first. None of this conference room with 10 people dialing into a zoom meeting with 3 other people nonsense. 100ms latency of conversation is real and you are at a disadvantage if you are trying to interject remotely into a room of in person attendees. 6. Hire managers into the critical mass (or who are willing to travel a lot). There will be lots of good reasons for the manager to make their way in on occasion (once a week, twice a month) to the home of critical mass for one reason or another 7. Onboard senior hires and leaders in person. I have seen new leaders, ICs, managers, design/pm/marketing leaders crash and burn over lack of building good relationships in the first 3 months. If you're bringing on a new leader for god's sake make sure they spend a few days in person with the other leaders they have to collaborate with. 8. Hire within a deliberate, manageable timezone range!!! This becomes more important the more varied the experience level is within your team. Is it possible with absolute engineering pros and remote veterans? Yes! But you need to ask yourself if your team is ready to coordinate work across Australia, UK, NYC, SF, Japan, and India timezones. Think hard about this one. My team is US west coast through Czech Republic. Teammates spanning every part of the US, Brazil, UK, Portugal, Denmark, and more. 8.a. Have a clearly established schedule for "time the whole team must be online". For us this is 8:30 - 10:00am Pacific, but many Europeans choose to work shifted schedules to have more overlap with their peers. I advertise this upfront in every hiring manager screen. Make expectations clear and let people decide. We're all adults and we're more likely to commit and make things work when we make a decision with complete information. 9. Onsite time is precious. Don't waste it on ordinary meetings. Use it for strategic conversations, solving hard problems together, hackathons, and high-bandwidth planning. This is where you build the relationships that make the next three months of remote work successful. For fuck's sake please do not fill a week making people stare at a projector while you read powerpoints!!! Take the advice or don't. </rant>
33
Walking down a quiet neighborhood street, just found eight women in their 70s and 80s having a vigil for Renee Good and Alex Pretti. #resist
2
128
A surprising fact about San Francisco is you don’t have to tweet about it.
1
160
Nine inmates remain on the loose Friday afternoon after 11 escaped from a New Orleans jail in the morning, with the Orleans Parish sheriff warning that they should be considered “armed and dangerous.” wapo.st/3FbHlip
1
445
Me and my code after an evening with the Rust borrow checker
214
New blog post: How to Get the Parent of an Elixir Process #myelixirstatus saltycrackers.dev/posts/how-…
1
321
Just published ProtoMock, a library for mocking Elixir protocols. My first Hex package! hexdocs.pm/protomock/ProtoMo… #myelixirstatus
2
340
Fellow engineers: let’s all apply as a joke, take a couple recruiting calls, and DDOS Elon’s recruiting efforts.
“Meanwhile, Twitter recruiters have already started reaching out to outside engineers to see if they want to join “Twitter 2.0 - an Elon company,” according to a message sent to one recruit that was seen by The Verge.” theverge.com/2022/11/17/2346…
3
I thought all these assholes were moving to Miami.
If you actually waited for the CDC to give you permission to stop wearing a mask outdoors after you’ve been vaccinated, you have no shot of becoming an entrepreneur. Keep your day job.
5
The ACB White House event has become the final movie theater scene from Inglorious Basterds, with the ghost of RBG in the role of Shoshana.
2
1
7
Facebook employees are the Susan Collins of the tech world: increasing “concern”, asymptotically approaching any meaningful action.
Facebook employees are furious with CEO Mark Zuckerberg, who admitted during a company-wide meeting that the company made an “operational mistake” by failing to remove a self-proclaimed militia group’s “call to arms” ahead of the Kenosha protest trib.al/nh2vMjU
5
Something (ok fine it was laziness) led me to take the escalator, out the wrong exit, at the BART station, which I never ever do, and gosh just look what was out there:
6
Hey #GCFPsf attendees! This post from @sarahmei will help you get your talk accepted: sarahmei.com/blog/2014/04/07… Bottom line? You want to be in this category: "Wow, I want to see that talk!"
Avoided writing this post for a long time, because I hate gushing, but... This is such a rare example of a useful, works-straight-out-of-the-box coaching tool, I really have to share it. medium.com/@ElizAyer/empower… #agile #leadership #empoweredteam
4
5
Does anyone else want to speak at a conference this year? You're not too inexperienced to do it. You're knowledgeable and you have important things to say. Check out this piece by @nodunayo. buff.ly/2F1bGyS #juniorsintech #conferences #coder #designer #ai #ml #tech
6
5