Skip to content
0:00 / 0:00

#richhickey#clojure#softwaredesign

"Design in Practice" by Rich Hickey

ClojureTV

111K subscribers • 135 videos on Hallway

YouTube
  • Recommended by 4 people: 2 on Hacker News, 1 on Lobsters and 1 curated list.
  • Presented by Rich Hickey, creator of Clojure
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

64K views3 years ago4 recommendations

Software designTools and practiceSoftware architectureDesign patternsSimplicity and complexity

Rich Hickey discusses the practical process of software design, focusing on problem statements, decision matrices, and choosing precise language.

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/presentations/DesignInPractice.pdf

Why it's here

4 people recommend this

What people say. Highly recommended for its practical insights on making decisions and defining problems in software design.

programming-talkscurated list on GitHubRecommends

Under “Software Development”

Design in Practice 01:00:45 by **Rich Hickey** (2023)

jauntywundrkindon Hacker News • Recommends

On “Holocron is an object storage based leader election library”

Rich Hickey has a section on using good words, on not using nicknames, in his (as ever wonderful) Clojure Conj 2023 talk Design in Practice, link to this video

erichoceanon Hacker News • Recommends

On “Focus on decisions, not tasks”

A good approach to making decisions in a team context (also works for personal use) is explained by Rich Hickey here: link to this video The talks is called "Design in Practice" but is really about making decisions.

DerGuteMoritzon Lobsters • Recommends

Design in Practice

u/ilja-fin r/Clojure • Mentions

Rich’s design talk Great talk, but kind of sad that the tool of choice for doing design work is a good old spreadsheet.. Shouldn’t the “Master of Clojure” use something else? Why hasn’t he built a tool that would facilitate the design process he’s been presenting? Do you think there is a room for a tool like this? Here’s the link to the talk in case you haven’t seen it: link to this video

nivertechon Hacker News • Mentions

On “Ask HN: What team tools do you use in your startup to organize information?”

…example input, output shapes in the form of tables, and the developers asking question while they arriving to common spec. Another is called Decision Matrix (almost as old as Periodic Table;), which was recently popularized by Rich Hickey in his talk Design in Practice1,2. Another valid usecase for shared spreadsheets is Use Cases table. --- 1 link to this video 2 slide #31 link…

jugjugon Hacker News • Mentions

On “Volkswagen Will Bring Back Physical Buttons in New Cars”

Reminds on Rich Hickey ranting about touch screens in cars 1 in Design in Practice: > We do not have feature X" is never a valid problem statement. If you need proof of this you only need to look at a modern car which has a touch screen where no one said, "I need to slide my finger on some random piece of glass to a precise point to set my blower in my car while I am driving." No one has ever said that, right? But somebody did say, "We need touch screens because young people will never buy our cars." This is what happens when you are not talking about the problem. 1: link to this video