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