gaggle_dk

5 ms·

1. 1.▲
   by gaggle_dk 3mo ago

   That reads like the same pain from higher up, yeah. It's the org forgetting instead of the person, but same essence. I've seen hints of this myself, and I have found no tractable solutions other than packing up and leaving when th
2. 2.▲
   by gaggle_dk 3mo ago

   I'm with you on the usage half: it's planning's job, and analytics/A-B play an important part there. But I think we're talking past the point that a lot of what you learn building something never show up in any dash
3. 3.▲
   by gaggle_dk 3mo ago

   I like the "check it into the tree" instinct. I've tried tracking observations and lessons in README files across a monorepo, but I felt they went stale almost immediately. Maybe your more focused files would work better. But
4. 4.▲
   by gaggle_dk 3mo ago

   The framing of preconditions that dissolve a class of mistakes is intriguing. I keep re-reading it, trying to picture how it actually exists day to day: is it something you run in your head when you're in the code, or is it structured
5. 5.▲
   Ask HN: After you ship a feature, what happens to what you learned?

   11 points by gaggle_dk 3mo ago|13 comments