I think that’s a bit of a shame because I personally have found LW-style thinking useful for programming. My debugging process has especially benefited from applying some combination of informal probabilistic reasoning and “making beliefs pay rent”, which enabled me to make more principled decisions about which hypotheses to falsify first when finding root causes.
As someone who landed on your comment specifically by searching for what LW has said about software engineering in particular, I’d love to read more about your methods, experiences, and thoughts on the subject. Have you written about this anywhere?
Sadly, not much. I wrote this one blog post a few years back about my take on why “reading code” isn’t a thing people should do in the same way they read literature but not much (publicly) other than that. I’ll think about whether there’s anything relevant to stuff I’ve been doing recently that I could write up.
As someone who landed on your comment specifically by searching for what LW has said about software engineering in particular, I’d love to read more about your methods, experiences, and thoughts on the subject. Have you written about this anywhere?
Sadly, not much. I wrote this one blog post a few years back about my take on why “reading code” isn’t a thing people should do in the same way they read literature but not much (publicly) other than that. I’ll think about whether there’s anything relevant to stuff I’ve been doing recently that I could write up.
I would recommend the other writers I linked though! They are much more insightful than I anyway!