0:00 / 0:00
#abstraction#clojure#softwaredesign
On Abstraction – Zach Tellman
Metosin
9K subscribers • 22 videos on Hallway
- Recommended by 2 people: 1 in engineering communities and 1 curated list.
- Presented by Zach Tellman
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
23K views9 years ago2 recommendations
Software designProgramming languagesSoftware architectureSimplicity and complexityFunctional programming
Zach Tellman explores the boundaries of common software design rules of thumb and provides a framework for thinking about abstraction.
The software industry is awash in folk wisdom. The "rule of three" tells us that we should only create a generic implementation once we've solved a problem three times. The Knuth quote about "premature optimization" either tells us that optimization is always bad, or bad 97% of the time, depending on how much of the quote we bothered to read. None of these prescriptions describe a context in which they might not apply. Taken literally, most are wildly misleading. To use them properly, we must already have a nuanced understanding of software. This talk presents a framework to intuit these same insights, but also their boundaries. It provides concepts and vocabulary that enable the viewer to not only explain how a problem should be solved, but why.Why it's here
2 people recommend thisWhat people say. Recommended as a thought-provoking talk on software design principles and the limits of common industry rules of thumb.
programming-talkscurated list on GitHubRecommends
Under “On the Industry/Community”
On Abstraction 01:00:02 by **Zach Tellman** (2017)
u/fjolnein r/Clojure • Mentions
On “Elements of clojure”
Here’s a talk by the author about the book: link to this video
Zach’s one of the most prominent Clojure community contributors and he put a lot of effort into it (like years of thought). More about architecture in general than about the language, which makes it even more of a must read.
u/zerg000000in r/Clojure • Mentions
On “Data-Driven Development is a Lie”
…ally like this kind of clickbait article, I could share some hints on this topic.
1. XML is not bad, so don't try to make it an argument
2. DSL doesn't necessarily go to either the bad or good side.
3. Don't create more terms, it did not help on make thing clearer
First, let's talk about the benefits, we had a very good talk about it with Zach
[video
When we can describe our concept using data
* last binding, we can change at the very last moment. a.k.a Max Composition
* free from different programming concepts like sync/async/stream/reactive/pipeline/multithread/pull/push
* queryable/inspectable/explainable
* one set of generic tools to rule them all ( Clojure core library )
* the ch…