yosuke_furukawaã®ãƒ–ックマーク - ã¯ã¦ãªãƒ–ックマーク高å“質ãªãƒ—ãƒãƒ³ãƒ—トを書ããŸã‚ã®7ã¤ã®ãƒ™ã‚¹ãƒˆãƒ—ラクティスã¨ã„ã†è¨˜äº‹ã€‚タスクã§ã¯ãªãゴールをè¨å®šã™ã‚‹ã€‚æˆåŠŸåŸºæº–を定ã‚ã‚‹ã€ã‚³ãƒ³ãƒ†ã‚ストを渡ã™ã«ã¯ã‚·ãƒ³ãƒœãƒ«ã§ã€å·¨å¤§ãƒ—ãƒãƒ³ãƒ—トを作らãšã«ãƒ—ãƒãƒ³ãƒ—トを連鎖ã•ã›ã‚‹ç‰ As we see LLMs churn out scads of code, folks have increasingly turned to Cognitive Debt as a metaphor for capturing how a team can lose understanding of what a system does. Margaret-Anne Storey thinks a good way of thinking about these problems is to consider three layers of system health: Technica
{{#tags}}- {{label}}
{{/tags}}