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.

48:48 : evaluation 51:05

I 100% agree. The biggest problem with Clojure and ClojureScript is that it is not advertised or marketed like other languages. Most developers don't even know it is an option until they go researching functional programming (Usually because they are like me and are 1000% done with broken JS and bloat). I think that Clojure is the most beautiful language so far, it is absolutely brilliant and I wish other front end devs knew about it and ClojureScript. ❤

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?

Very complicated model, however well done presentation.

00:30 🤯 Simplicity is a prerequisite for reliability in software development, and we need to focus more on building simple systems. 02:34 📚 "Simple" means one fold or one twist, while "complex" means braided or folded together. Understanding this distinction is crucial in software development. 07:20 🤖 Easy can refer to being physically near, familiar, or within our capabilities. It's essential to recognize these different aspects of "easy" when discussing software. 11:54 🏃 Focusing solely on ease (fast development) at the expense of simplicity (understandable and maintainable code) will eventually slow down software development. 19:50 💡 Some constructs that seem easy can lead to complex and incidental complexity in software. Prioritizing simplicity in output is critical for software quality and reliability. 21:51 🧩 Simplicity leads to increased flexibility, independence of decisions, and easier policy changes in software development. 23:23 🧠 To deal with complexity, rather than trying to become smarter, simplify by reducing incidental complexity in your software. 27:18 🧶 "Complect" means intertwining or braiding, and it's a source of complexity in software. 30:19 🔄 Simple components allow for horizontal separation and vertical stratification, leading to robust software design. 39:31 🕸 Various software elements like state, objects, methods, inheritance, syntax, and more can contribute to complexity by intertwining different concerns. 42:38 🧩 The talk emphasizes the importance of distinguishing between "simple" and "easy" in software development. 43:07 🛠 Developing software can be simplified by choosing simpler tools and focusing on the essence of the problem, rather than complex constructs. 44:09 📦 Use values and persistent collections for simplicity, and avoid unnecessary complexity in data manipulation. 45:38 🌐 Simplify communication by using data instead of arbitrary command strings, and aim for polymorphism ala carte. 47:02 🔀 Simplify complex systems by using declarative rule systems and focus on consistency, transactions, and values. Made with HARPA AI

nice talk!

One thing I wonder about regarding maven central being immutable is: if a package is found to straight up malware, is it removed, making maven not immutable after all? More commonly a package is found to be insecure, and it seems like we keep providing it for backwards compatibility, maybe with a big warning. Then again nothing is perfectly secure I suppose.

great talk. Thank for share .😁

TLDR: Do not try this at home.

As best I can tell, this is the only way for someone like me to build something Datomic-based, full-stack, and production-ready. I just don't have 20 years of dev experience. I _do_ have a desperate need to get a system up and running. Thanks Chris - and Rich, Alex, Stu, Jaret, Marshall, the rest of Cognitect/Nubank, and the whole Clojure community.

This is a great talk

“Zero projecty overhead” - I need an easy install path for clj tools on windows for this to happen, please help.

Amazing.

This is an underrated talk!

Textfield in bottomsheet is covered by keyboard. How to fix it?

There was a reference to a white paper, is that or any artifact related to this library available?

Wow, this is the cleanest way I've seen to write flutter code. Super minimal. No boilerplate!

That slide about the disappearing atom struck me. Is that what dark matter is? Atoms that are "polarized" such that we can't see them?

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)

As a web developer of almost 30 years, who has never seen a line of Clojure, I've probably watched this talk 5 times over the last 9 years and recommended it dozens of times. Ewald perfectly captures a philosophy of software development that has been lost in the age of massive tooling stacks and complex frameworks. Most developers I've hired or worked with over the last 15 years have never worked without a framework. More than that, they don't even realize that working without a framework is an option. They don't apply for web development jobs, they apply for [insert tech stack and framework here] jobs and they have no idea that they can work faster, build better products, save money, and actually understand what they are shipping if they go back to programming with hand tools. As a side note, I also built myself a great workbench, bought some wire holdfasts (don't waste money on cast ones), and started buying up planes, chisels, and dividers and other layout/marking tools at antique shops and garage sales. I also absolutely love my table saw (and band saw, thickness planer, cnc router, 60w laser, etc) , but knowing when and how to use hand tools changes everything. I no longer measure anything when I have a geometric/mechanical solution.

This is such an impressive demo! Will definitely check this project out

29:47 Am I stupid for being completely blown away by this implementation or is the audience for NOT erupting into applause?

One of the most impressive talks I’ve seen in a while. Beautiful implementation

Why would anyone choose clojurescript over react ?

Janet Car or Cdr?

Ничего не понял, но очень интересно!

Very promising ! Thanks for the presentation !

"we can all expect our AWS bills will keep climbing" 😥

That was the most impressive live demo I've seen in a very long time.

A great talk, I'd love to see a deeper talk on the applicability of the onion architecture to Clojure codebases. Thanks Janet.

This is a great response to “AI is going to take our coding jobs”

Really enjoyed this one 🙂