Career Chats with Swyx and Randall

Swyx and Randall

Short, focused chats about developer careers. 1 topic each, selected from the best of our writing and thinking.

  1. 01/14/2021

    Season 0 Retro: Thank You Listeners!

    We're taking a short break to focus on solo projects! Randall is launching CrowdFox.io soon and Swyx is launching his personal podcast. General formatSheldon Hull "I rarely listen to podcasts because of how much wasted time there is. I've been listening through all you and Randall do and it's super useful and interesting. absolutely incredible job. Cheers and thank you"Michael Gee "I have gained a ton of value from your informative and concise podcast Career Chats so thank you & keep up the good work"John Raptis "I really like this short format with links. I don't know if I'm able to squeeze yet another one hour long podcast in my day."Episode 5: Twitter for DevelopersCharlie You: "LOVED this episode, extremely helpful for me as a Twitter noob. Just bought the course Randall mentioned"Episode 10: Big L NotationHassan El Mghari: "FWIW this is the only podcast I listen to regularly bc of the high signal to noise ratio. Almost every episode makes me stop and reflect on what I'm doing (love the action item at the end)"Episode 12: Staff EngineerBarry Kern "just stumbled on Staff Engineer episode and its 🔥 thank you🙌👏 picking up so much from this one."Episode 15: Goals vs Processes Debra-Kaye Elliott "Great tips in this episode!" Godswill Umukoro "Awesome podcast on setting achievable goals""People over estimate how much they can get done in ONE YEAR, and under estimate how much they can get done in 12 WEEKS" - @RandallKannaGot questions and requests for future episodes? Shout us out on Twitter or email an audio question to swyx@hey.com! Speaker Links - Randall (@randallkanna): CrowdFox.io, The Standout Developer, The Standout Career- Swyx (@swyx): Learn in Podcast, The Coding Career Handbook- Discuss this episode on Circle

    6 min
  2. Getting into Cloud (ft. Forrest Brazeal)

    12/11/2020

    Getting into Cloud (ft. Forrest Brazeal)

    This week we have another guest interview with the multi-talented Forrest Brazeal (site, twitter, newsletter) who is one of the most passionate cloud advocates in the world. Definitely check out A Cloud Guru's Cloud Resume Challenge if you or someone you know is interested in getting into the cloud, and stay for his hot takes on mid-century children's literature! 0:00 - Intro & Background 1:55 - Cloud Resume Challenge - a child of the pandemic- https://twitter.com/forrestbrazeal/status/1254822417203113986?s=20- https://cloudresumechallenge.dev/- https://acloudguru.com/blog/news/introducing-the-cloudguruchallenge 5:57 - Success Stories - Hall of fame https://cloudresumechallenge.dev/halloffame/- Pay-as-you-go cloud made this much more affordable 9:17 - Community & Cohorts - Join the Discord https://discord.gg/2PTwAth 10:09 - Employers -  Most people don't even need Forrest's network- You learn real knowledge going through the projects- Being able to grow inhouse talent is a competitive advantage- We need more internships and rotations in the industry 14:23 - Cloud Specializations - Monthly challenges are themed- Kesha Williams Machine Learning Challenge https://acloudguru.com/blog/engineering/cloudguruchallenge-machine-learning-on-aws 15:20 - Career Advice -  Be careful about general advice  - we all start from different places- What DOES work is sharing your network and privilege 16:58 - The Value of Networks - Don't play Resume Roulette - spray & pray- Networking is not beneath you- This is you evaluating the industry as much as the other way around- Giving the gift of your network and referrals does way more than advice 19:15 - The Right Way to Get Referrals - always see if you can get a referral when applying- "How do you know this person" - Cold DMs for referrals don't work- engage in the community, write blogposts, try stuff out, tag the creator- Pick Up What They Put Down 22:16 - Why Own Your Content - Its fine to start on Dev.to or Medium- But eventually it's important to own your domain/mailing list 23:45 - Specialization vs Megatrends - Didn't choose the Serverless life, Severless chose me- Can't forecast 10 yrs ahead - just listen to megatrends- Generational trends - Lindy effect- Hypergrowth trends - capturing big % of population every year- Text Editor wars -> VS Code 26:41 - Mid-century Children's Literature - Perceptions of reality- Virginia writing alternate history of the Civil War- Japanese WW2 equivalent- Subjective vs Objective Reality 29:05 - The Read-Aloud Cloud - https://www.goodreads.com/book/show/51645863-the-read-aloud-cloud- explain Cloud to non-technical people- people don't have an intuitive model for why Cloud exists- helps them ask the right questions ---- Speaker Links - Forrest Brazeal (@forrestbrazeal): Site, Twitter, Newsletter, The Read Aloud Cloud- Randall (@randallkanna): The Standout Developer- Swyx (@swyx): The Coding Career Handbook- Discuss this episode on Circle

    32 min
  3. Staff Engineering (ft. Will Larson, CTO of Calm)

    12/02/2020

    Staff Engineering (ft. Will Larson, CTO of Calm)

    What happens after you go past Senior? Will Larson, CTO of Calm, has been interviewing Staff-plus engineers across the industry for his new book, Staff Engineering.  This is our first full-length interview podcast episode! If you enjoyed it, please help us share with a friend and let us know your feedback! (Links at bottom) ---- 1:00 Why research Staff Engineering? Most bigcos make up their ladders as they go along, or cargo cult from FB/Google.We have to separate management from leadership.4:31 Who are Will's role models? Lara Hogan - the Voltron ManagerJulia Evans' Wizard ZinesTanya Reilly - Being GlueDan Na - Pushing Through FrictionJulia Grace, Director of Eng at Apple: "Don't play team sports alone, you'll lose."The Staff level is a leadership role, you don't get promoted on the basis of your work alone.11:08 How do you find someone to help you grow? 3 types: Role Models, Mentors, and SponsorsSponsors: Lara Hogan on SponsorshipThe key question: "Do I need to develop myself" or "Is the company evaluating my work fairly"?Mentors: Some mentors give generic answers, others know your specific context. The second one is harder.Role Models: Helps you know someone with your background can accomplish something. Lighthouse hires are important as proof.Retention is most important hereLook externally on Twitter and on StaffEng.comDuretti Hirpa at MailchimpRas Kasa Williams at MailchimpMichelle Bu at StripeThe best people may not be writing online16:30  Being Visible Books are bought, not soldIf you aren't visible, your work won't be valued.18:12 Career Management Most people don't manage their careers at allMost companies are set up to assume Fungible Developers which is exactly what you don't want to beBut also blaming your manager is a self limiting belief. You personally have to be managing your own career.Write your own promotion packets on an ongoing basis.Julia Evans on Brag DocumentsTip: Make your own achievements channel in Slack and log all that info for later20:39 Architects - How do you lead without authority? Silvia Botros at TwilioKatie Sylor-Miller at EtsySpend a huge amount of time soaking up contextReduce communication and coordination costsWe rarely understand the problems we are solving when we design the solutionOne directional communication doesn't work - gathering context and providing a common interface helps solves thisArchitects are powerful bc they are aligned with their engineers, Managers have to align with their orgsSimilar to a Product Manager role - all of the responsibility, none of the authority24:37 Solvers and Matching Archetypes to Company Stage Opposite of Architects? It depends on the company's approach - do they plan and then ship, or do they ship and learn. Architects cannot function in the second type.4 archetypes: Team Leads, Architects, Solvers, and Right Hands.Calm is all Team Leads - the majority of the value is not in operating or creating infrastructure - it is in creating productIt's pointless to bias too much to Architect or Right Hand early onYou don't see Right Hands except at much bigger companies - for scaling out29:10 What should Senior Engineers know about Systems Thinking? Will Larson's Intro to Systems Thinkinghttps://github.com/lethain/systemsThinking in Systems by Donella MeadowsEngineers should have both an abstract Systems Thinker and a practical Solver toolkitIncident programs overfocus on compliance rather than remediationIncidents -> Response -> Review -> Management (catalog, tag) -> RemediationDon't focus on moving from stage to stage32:33 Metrics: The subtle art of Measuring Engineer Productivity Accelerate: Building and Scaling High-Performing Technology Organizations1. Delivery lead time2. Deployment frequency3. Change fail rate (defect rate)4. Time to restore serviceHow they dynamically run tests to improve productivity at Stripe36:30 Career Advice Will Larson's Career AdviceThink about the teams you've worked with with the highest density of people you want to be working withYahoo storyDigg v4 story - your network will outlast your jobYour manager and team matters more than the companyThanks for listening! Speaker Links - Will Larson (@lethain): Blog, An Elegant Puzzle, StaffEng.com - Randall (@randallkanna): The Standout Developer- Swyx (@swyx): The Coding Career Handbook- Podcast Episode discussion on Circle

    41 min
5
out of 5
4 Ratings

About

Short, focused chats about developer careers. 1 topic each, selected from the best of our writing and thinking.