Joel Chippindale's recommended links

Links to recommended articles, books, podcasts, videos etc. on a variety of subjects.

Search links

.  .  .  .  .  .  .

B

• Building teams

C

• Career development
• Change
• Coaching
• Communication
• Culture

D

• Decision making
• Delegation and empowerment
• Diversity, equity and inclusion

E

• Engineering leadership

F

• Facilitation

G

• Generative AI
• Git
• Giving and receiving feedback

H

• Hiring and being hired

I

• Inspirational talks

L

• Learning

M

• Managing time
• Managing up
• Meetings
• Mergers and acquisitions
• Metrics

O

• One to ones
• Organisational structures

P

• Pairing
• Pay and compensation
• Product management

R

• Remote working
• Retrospectives

S

• Security and compliance
• Software development
• Speaking at conferences
• Strategy
• Stress

T

• Testing
• Trust

Recently added links

• Lack of trust kills organisational potential
  "People are far more likely to listen to you once they believe you have actually listened to them." — Emma van Dijkum
• Four dimensions of burnout: An anti-burnout framework for the AI era
  Dominka Rogala's talk is insightful and practical
• Tokens, hours, points, and other curious proxies
  John Cutler's thoughtful reflections on measuring return on investment when it comes to developing software
• Half-baked product
  Gerard Marquina Rubio's cautionary tale of start-up life
• Headed for the exit: the Great Engineering Leader Career Break [BEHIND A PAYWALL]
  Gerely Orosz on seeing more and more CTOs, VPEs and Heads of Engineering walking away from high status in-demand positions
• Landing the plane
  James Stanier and how the last 10% of a project is the hardest
• The subtraction instinct
  Mike Fisher on our propensity to solve by addition, and how we can miss better options that involve subtraction
• Anatomy of a frontier lab agent intrusion: A technical timeline of the July 2026 incident
  Hugging Face's team shares details about how their systems were hacked by an autonomous AI agent earlier this year
• Why is everyone in tech so sad
  Aaron Howarth on Workism and the impact of AI on the experience of work
• Let's not call it "tech debt," it's just "mess"
  Nat Bennett on the problems of "tech debt' as a metaphor
• Vibe coding personal apps in mid-2026
  Francis Irving shares his approach and experiences
• The case for hiring junior engineers 🌱
  Luca Rossi's welcome reminder of how hiring junior engineers benefits us and our teams and that this is still true in the age of AI
• Quiet quitting, rage quitting, and real quitting
  Kieran Snyder shares their survey of 200 people who quit their jobs and the timelines of their quitting
• Triggers
  We have triggers. The people who work for us have triggers. They can be surprising when you hit them. Rands reminds us to notice when we are hitting them
• How to successfully onboard remote engineering staff in four weeks
  James Stanier reflects on his experience of onboarding at Shopify and shares tips on how you can think about designing your onboarding experience
• Your junior engineers don’t need an office. They need you
  Kelli Korducki's welcome reminder to explicitly design for the support that your new employees need
• FelonyBench Style Points
  SE Gyges with a new set of benchmarks to rank LLMs
• What would make next week better?
  Cate Huston offers excellent advice for when you are feeling overwhelmed
• Performance engineering for everyone
  Elena Tanasoiu & Emma Gabriel offer great advice both on using flamegraphs to diagnose (rather than guess about) performance problems but also on getting insights from real users.
• The reality of being a CTO
  James Stanier shares his experiences of what is involved in being the CTO
• The pitfalls of unlimited time off
  Mathias Meyer shares his experiences of offering unlimited time off, what can go wrong and how to address it
• The Luddites – Rage against the machine
  Origin Story share the story of the Luddites and it is hard not to see the parallels in the dynamics of what is currently going on with LLMs
• Always go with a monorepo
  "Use one repository. Draw your boundaries inside it. Reach for a second repository only when you have a mechanical reason the filesystem genuinely cannot give you, and notice how rarely that turns out to be true." — Kore Nordman
• Berkana Two-Loop Model
  Margaret Wheatley and Deborah Frieze's map for creating change in systems
• Ways to think about token pricing
  Benedict Evans on possible futures on what would have to happen if they are not to become low-margin commodity infrastructure

Subscribe to an RSS feed for these links.