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.


Archives

Tinned Fruit Missives | Regular emails

Tinned Fruit Missives archive


Regular email archive

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