Mailing list

Sign up for my writing on front-end engineering leadership.

I don't write about the latest hot JavaScript framework or nifty CSS animation techniques.

Instead, I focus on big challenges for front-end engineering leaders: development practices, growing teams, and long-term technical strategy.

You'll get short weekly lessons and insights, and my monthly link newsletter, Tinned Fruit Missives.

Join my daily mailing list

Sign up now and get my Front-End Engineering Responsibilities Laundry List PDF for free.

You'll get regular emails about front-end development. Unsubscribe at any time.


Tinned Fruit Missives | Regular emails

Tinned Fruit Missives archive

Regular email archive

  1. Don't use story points for prioritisation
  2. Redesign along strata, not down boreholes
  3. Jevons paradox of client resource consumption
  4. Pure and applied expertise
  5. Individual expertise and team balance
  6. Celebrating impact
  7. Progression frameworks for smaller companies
  8. How to read a progression framework
  9. Global CFP Diversity Day
  10. Code crit?
  11. Truth to materials
  12. Fancy a game of Spot the Fallacy?
  13. Tsundoku and professional development
  14. Recognising and rewarding glue work
  15. How much time should I spend writing code?
  16. Just-in-time collaboration trumps documentation
  17. Practices for communicating and upholding code standards
  18. Setting standards from scratch
  19. Determining and communicating development standards
  20. Work according to your scope of influence
  21. Balancing feature development with stewardship
  22. Coffee club or committee meeting?
  23. Do you have a 'Front-End Chapter'?
  24. The important part of the Spotify Model
  25. Are browser support policies dead?
  26. Support browser support by supporting your browser
  27. Grabbing the lead
  28. Why I no longer believe in the web
  29. Dealing with the arriviste problem
  30. Behold! An arriviste appears
  31. Stop it with the handoffs
  32. My preciousss code
  33. Which mode are you in?
  34. My employer's principles aren't my values
  35. Principle background checks
  36. Web software design principles: The Principle of Least Power
  37. Dialogue or monologue?
  38. Design principles before fancy patterns
  39. Collective capabilities over individual expertise
  40. Netflix's low-hanging fruit
  41. Take the foot off the pedal to go faster
  42. Ninja rockstar bottlenecks
  43. Conway's Law goes deeper than your org chart
  44. Conway's Law is no joke
  45. Side project gardening
  46. The side project shuffle
  47. Front end devs are now big borrowers
  48. The build, borrow or buy fractal
  49. What should a full-stack developer focus on?
  50. Frustration-driven development
  51. Webworker
  52. A maturity model for front end development?
  53. Are little rewrites better than refactoring?
  54. Why discovery testing helps component-based UI development
  55. Are you Detroit- or London-school?
  56. Pyramids, ice cream cones, crumbs, pancakes and trophies
  57. TDD: ugh, right?
  58. Drifting into a test-averse culture
  59. Do you need a second brain?
  60. T-shaped knowledge is hokum
  61. Slicing and dicing the curate's egg
  62. Front-end channel on Rands Slack
  63. My own brush with the 'Spotify Model'
  64. Peter is out of the squad on principle
  65. Lean delegation
  66. Robotic front-end web jockeys
  67. You wouldn't let a marketing contractor fly an airliner
  68. Awkward stacks
  69. Managing long-term, part-time migrations
  70. A chance to be vulnerable
  71. A question for front-end engineering leaders
  72. Peering in through the window
  73. Hot takes! Any hot takes?
  74. A misty-eyed journey into the boring old days
  75. PWA super starters
  76. Marvin Minsky's opinions about CSS-in-JS
  77. Get some Webhint in your toolchain
  78. What's the web really good at?
  79. MVPs are not (always) Mini Versions of the Product
  80. The prototype gamut
  81. Walking skeletons and tracer bullets
  82. The runaway proof of concept
  83. Prototypes, proofs of concept, walking skeletons and MVPs, oh my!
  84. Chesterton's fence is not yours to remove
  85. Failing safely
  86. Sometimes, you *are* Google (maybe)
  87. Other words for 'rewrite'
  88. When refactoring isn't
  89. How GitHub switched from jQuery to, well, nothing
  90. Tog's Law of Commuting and you
  91. Tesler's Law
  92. Fundamentals schmundamentals
  93. 20,000 enemies
  94. Mindful code reviews
  95. E pluribus unum
  96. Video: How to Survive the Single Page App-ocalypse
  97. Embrace the experiment
  98. Product and agency work isn't so different
  99. Who has your back?
  100. Start with yourself
  101. Dealing with negative product feedback
  102. Small and big discomforts
  103. Rational technology choice doesn't exist
  104. Did we back the wrong horse?
  105. Movements and complications
  106. Reluctant scrum mastery
  107. A product manager stepped on my toe
  108. Over to you. Got a question about front end leadership?
  109. Are static sites the new static site?
  110. Wilful educated ignorance
  111. Hey, where's all the front-end stuff?
  112. How to create a lead time ladder
  113. Spot waste with value stream mapping
  114. Trimming your 無駄
  115. 1000 ways of testing
  116. Constructive snark?
  117. Clean me
  118. What 'make the business case' really means
  119. Software NIMBYs
  120. Developer happiness considered harmful (sometimes)
  121. How to win every argument
  122. Software archaeology and anthropology
  123. Hidden foundations
  124. Hollow artifacts
  125. UI foundations on a shoestring
  126. Platform and Foundation
  127. Ceci n'est pas un job
  128. Full stack developer? Software engineer? Rockstar Ninja Hacker?
  129. Full Yack Shaver
  130. Full-stack jacket
  131. How many full-stack developers does it take to change a light bulb?
  132. You really do have to get out of the building
  133. The trust multiplier
  134. Your role as an amigo
  135. The accidental lead
  136. Starting with why...
  137. Positioning for front-end developers
  138. Everybody wants to be (internet) famous