Post AvozkhYuYYugYMKNdo by wolf480pl@mstdn.io
 (DIR) More posts by wolf480pl@mstdn.io
 (DIR) Post #AvozcZAhrs5GDL7vwO by wolf480pl@mstdn.io
       2025-07-05T11:18:33Z
       
       0 likes, 0 repeats
       
       I'm starting to think writing down design principles and design decisions, with rationale and the discussion that led to it as an attachment, is something more software projects should do.This should help avoid:- repeating the same arguments over and over again- accidentally breaking a design principle without noticing- running on a git-blame chase only to find a single-line commit message not explaining "why?" at all
       
 (DIR) Post #AvozkhYuYYugYMKNdo by wolf480pl@mstdn.io
       2025-07-05T11:20:01Z
       
       0 likes, 0 repeats
       
       I wonder if that's what @oxidecomputer's RFDs do....
       
 (DIR) Post #Avp7YDneBZ6UPBmRbE by ignaloidas@not.acu.lt
       2025-07-05T12:47:24.323Z
       
       0 likes, 0 repeats
       
       @wolf480pl@mstdn.io @oxidecomputer@hachyderm.io Seems like mostly yes, though what I've read it's sometimes a bit more than that.
       
 (DIR) Post #AvpGUBYdTkt7seuQca by p4@masto.ai
       2025-07-05T14:27:29Z
       
       0 likes, 0 repeats
       
       @wolf480pl looking at the ones that are public, that's one of their use cases.