29K views · Feb 20, 2017 · 37:15 · 4 HN recommenders · 4 mentions · discussed 2018–2021
Stuart Halloway's satirical talk describes how to protect yourself from industry change by spreading complexity through systems while following idiomatic practice. It uses this inversion to catalog software design anti-patterns.
Why Hacker News points people here: HN commenters love it as a witty and insightful tour of design anti-patterns, applicable to DSLs, OOP and API design.
“a great talk by Stuart Halloway called Narcissistic Design.”HN comment, 2018
“I love Stuart Halloway's talk on Narcissistic Design”
Talk on anti-patterns in system design.
Along a similar line, I love Stuart Halloway's talk on Narcissistic Design - this video Prefer APIs over data. Start with DSLs. Always connect (and never enqueue). Create abstractions for information. Use static typing across subsystem boundaries. Put language semantics on the wire. Write lots of unit tests. Leverage context. Update information in place.
“a great talk by Stuart Halloway called Narcissistic Design.”
Reading some of the comments here reminded me of a great talk by Stuart Halloway called Narcissistic Design.[1] [1] this video
“Has some great insights and quips.”
Insights and quips about DSLs and design.
Nobody seems to have posted Stuart Halloway's Narcissistic Design yet, so I'll just leave this here. this video Has some great insights and quips. "Nothing says 'screw you' like a DSL"
“This talk goes into many anti-patterns”
Covers anti-patterns including why SQL is only a DSL.
this video This talk goes into many anti-patterns, but he gets to the real problem with SQL, that it is ONLY a DSL and lacks either an API or a fundamental information model to program against. Composability when working with a DSL is a nightmare. I also have been moving away from ORM to directly writing SQL, but lets be honest about the reasons that programmers are wary of working directly with SQL as they are legitimate issues.
