Rich Hickey, the author of Clojure and designer of Datomic, is a software developer with over 35 years of experience in various domains. Slides: download.clojure.org/presenta...
I've used this technique to good success. Some good tip is to have the variants be represented (sometimes when applicable) by the pseudo code or API, to make it easier for readers to recognize what the column represents. Overall, this combines well with his hierarchy of problems. With the hierarchy of problems, we need to put most of our energies on hard/significant problems, which we pay more for or more often. This decision matrix technique has the focus aspect by keeping the most important items front and center. Problem solvers can better use their analysis/mental resources on what's important.
Etymonline is a great resource for unpacking our language and getting back to the essence of our words. Fun fact: "complect" is in there (from the "simple made easy" talk)
@think myelin maybe because design is an inherently consensus-building and shared-meaning/definition activity that wouldn't make sense to delegate to AI. implementation can in various aspects be delegated to machines/automaton.
@@thinkmyelin I can't talk for the OP, but I agree with them because this talk shows that good software is more about _thinking_ than _coding_. AI like co-pilot currently is just a predictive model of code out there. It doesn't do high-level thinking. Though admittedly, many human programmers don't either!
I am not sure of the distinction between describing situation） and diagnosing （problem). Sounds like describing situation focuses on describing the symptoms, while diagnosing (problems) finds the root causes of the symptoms?
I’m a Clojure advocate at a windows/Java shop. I want to try the latest stuff, and lein fell apart when I tried to point it at a newer JVM. Tools.deps seems like the way to go, but on a managed PC, “just run this beta(?) PowerShell script” is a hard sell to start with.
