Login
You're viewing the techdon.dev public feed.

Replies

  • Nov 11, 2026, 7:34 AM

    @luis_in_brief @tongpu @whack Bonus cite from the comments of that one. 1985! gwern.net/doc/cs/algorithm/198

    And then following some links brought me to margaretstorey.com/blog/2026/0

    > I saw this dynamic play out vividly in an entrepreneurship course I taught recently. Student teams were building software products over the semester, moving quickly to ship features and meet milestones. But by weeks 7 or 8, one team hit a wall. They could no longer make even simple changes without breaking something unexpected. When I met with them, the team initially blamed technical debt: messy code, poor architecture, hurried implementations. But as we dug deeper, the real problem emerged: no one on the team could explain *why* certain design decisions had been made or *how* different parts of the system were supposed to work together. The code might have been messy, but the bigger issue was that the theory of the system, their shared understanding, had fragmented or disappeared entirely. They had accumulated cognitive debt faster than technical debt, and it paralyzed them.

    💬 0🔄 0⭐ 0