featured in #495
An Engineering Leader’s Job Search Algorithm
- Kevin Conroy tl;dr: Word document written by Kevin, an Engineering Manager at Meta. “This outlines the algorithm I’ve used for my job searches. It’s not perfect. There’s no one right way to do this, and your mileage will vary. However, I’ve tried to capture the common elements and rules of thumb I’ve picked up over the years in the hopes that it will help someone else through what is all too often a very stressful process. I hope you, too, can overcome the imposter syndrome and anxiety you might have to get a job that you love and pays you what you are worth (or more)!”featured in #495
A Technology Leader's Non-Technical Reading List
tl;dr: “I’ll share my personal favorite reading materials that have helped me think about leadership, management, people and technology.” There were a few main themes that drove the authors interest notably books that display different examples of management, people working together and those that challenge the author’s current world view.featured in #495
Parkinson's Law: It's Real, So Use It
- James Stanier tl;dr: “When you are asking people to do something, lead with a recommendation of when it should be done by. Be explicit about this, but open to negotiation. It's such a simple technique, but when you compound its usage over a year at a big company, you will be amazed at the difference it makes.” Parkinson's Law states that "work expands so as to fill the time available for its completion" and, by setting aggressive deadlines, James discusses how leaders can leverage it.featured in #494
Why Passkeys Improve User Security & How To Implement Them
- Dan Moore tl;dr: When developing an API, safeguarding it is crucial. Consider the choice between employing a centralized API key verification system or opting for a decentralized approach. The centralized method necessitates ongoing communication among API key consumers, API-serving systems, and the central authority responsible for issuing API keys, all aimed at verifying the keys' validity.featured in #494
5 Lessons I Learned The Hard Way From 6 Years As A Software Engineer
- Jordan Cutler tl;dr: (1) Bring solutions, not problems. Focus on showing how you are there to support the team that needs the help. (2) Clean code isn’t the end goal. Collaborating effectively with your team is more important. (3) Team outcomes are greater than individual outcomes. What you spend your time on should be directly correlated with what will bring impact for the team. (4) Adapt to your manager. Understand how to adapt to your manager’s style and goals to see the best collective outcomes. (5) Influence isn’t about wording. Focus on building relationships with a foundation of trust.featured in #494
Productive Compliments: Giving, Receiving, Connecting
- Kent Beck tl;dr: “At it’s best, a compliment is a warm fuzzy. Receiving or giving a compliment blesses the day. At it’s worst, a compliment is a naked power play, an assertion of dominance. Giving and receiving compliments are not natural skills. This article summarizes what I’ve learned about giving and receiving compliments so far.” Kent provides specific and actionable advice around the semantics of human connection.featured in #493
How To Add An Onboarding Flow For Your Application
- Roy Anger tl;dr: Explore Clerk's method to revolutionize app onboarding in Next.js, enabling tailored user experiences from the start. Learn about session tokens and middleware for a flexible framework that meets business and user needs, simplifying setup and enhancing engagement and retention, key for digital product success.featured in #493
How I Build And Run Behavioral Interviews
- Ben Kuhn tl;dr: “I used to think that behavioral interviews were basically useless, because it was too easy for candidates to bullshit them and too hard for me to tell what was a good answer. I’d end up grading every candidate as an “okay, I guess” because I was never sure what bar I should hold them to. I still think most behavioral interviews are like that, but after grinding out way too many of them, I now think it’s possible to escape that trap. Here are my tips and tricks for doing so!”featured in #493
Guide To Leading Meetings For Software Engineers
- Jordan Cutler tl;dr: (1) Before the meeting: Figure out the outcome you want to achieve by the end of the meeting. Invite people based on that outcome. Send a message or tag in the channel about the meeting invite and the purpose. Add a meeting description so everyone knows what it’s about. Start the meeting description with, “The goal of this meeting is…” (2) During the meeting: Start the meeting off by reiterating the expected outcome and goal. Respectfully keep the meeting on track pointing to the goal. Make sure everyone feels heard throughout the discussion. (3) After the meeting: Document all important points. Post a summary of the points and action items along with dates and responsible individuals.featured in #492