programming-talkscurated list on GitHubRecommends
Under “On the Industry/Community”
Idée Fixe 00:39:36 by **David Nolen** (2017)
0:00 / 0:00
#clojure#simplicity#softwaredesign
Idée Fixe • David Nolen • GOTO 2017
GOTO Conferences
1M subscribers • 91 videos on Hallway • Conference channel
- Recommended by 2 people: 1 in engineering communities and 1 curated list.
- Presented by David Nolen
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
13K views9 years ago2 recommendations
Software designProgramming languagesSimplicity and complexityLisp and ClojureSoftware architecture
David Nolen discusses how fixed ideas obstruct reliable software development and uses Clojure as a case study for simplicity.
This presentation was recorded at GOTO Chicago 2017. #GOTOcon #GOTOchgo gotochgo.com David Nolen - Software Engineer at Cognitect ABSTRACT For an industry steeped in a mythos of innovation and invention, the path towards reliable software is often obstructed by a web of fixed ideas. Fixed ideas, by actively obscuring alternatives, lead us to inaccurately the weigh the risks and benefits associated with our choices whether they be of an engineering [...] Download slides and read the full abstract here: gotochgo.com/2017/sessions/67 twitter.com/GOTOcon linkedin.com/company/goto- facebook.com/GOTOConferences #IdeeFixe #Innovation Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket at gotopia.tech Sign up for updates and specials at gotopia.tech/newsletter SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily. youtube.com/user/GotoConferences/?sub_confirmation=1Why it's here
2 people recommend thisWhat people say. Recommended as a great talk on simplicity in software design and the community dynamics of Clojure.
u/edster3194in r/ProgrammingLanguages • Recommends
On “Worse is better”
I think it is interesting to use Clojure as a case study with respect to where it falls in this debate.
At a glance, I would say Clojure is a "the right thing" language. They famously agonize over seemly small changes due to the impact it will have on the interface, users, and (to an extent) implementation. Despite this, the maintainers of Clojure are adamant about simplicity above all else, and the language implementation complexity has not exploded over time.
It's tempting to attribute this to Clojure being a so-called "dead" language with too little activity to see this complexity growth. However, if you spend time in the (admittedly small) community it is clear that they continue to…