[swyx]

oh wow nice to see this on HN! I wrote this blogpost - happy to answer any questions!

yes it works very well for Netlify; when i joined the frontend dev team i immediately saw the value of this idea and begged the eng and design team members (that came up with the idea) for permission to write it up

for those interested, I recently adapted this idea for project prioritization https://twitter.com/swyx/status/1366849232959807489?s=20 because I was searching for a better alternative to the nonsensical effort estimation vs impact backlog grooming systems prevalent in product management.

[wbc]

Thanks for the write up!

What are you thoughts on enforcing future action (pebbles)? One thing I try to push for is to never have TODOs in code, instead make a backlog ticket/issue and link it. Unfortunately those tend to stay de-prioritized.

How often do your pebbles get the desired follow-up?

[swyx]

yeah backlog issue or TODO in code. i personally dont mind the TODOs in code because they remain in context. also, you often get benefits from accumulating some todos of a similar nature, then solving them in one go in a tech debt cleanup sweep.

in my time there (i've since left the company) we didn't get a lot of pebbles. boulders and sand were more common. perhaps i shouldve communicated that distribution more clearly.