One Rule to Rule Them All • Pragmatic Dave Thomas • GOTO 2023

This presentation was recorded at GOTO Amsterdam 2023. #GOTOcon #GOTOams
gotoams.nl
Dave Thomas - Author of The Pragmatic Programmer ‪@pragdave‬
RESOURCES
pragdave.me
/ pragdave
github.com/pragdave
/ dave-thomas-53aa1057
ABSTRACT
As developers, we live under a constant barrage of helpful advice, often in the form of rules with cute names. We're told how to design, how to code, how to deploy, how to monitor: there are systems and rules for everything. How can we keep up? How can we know what's good advice, and what's bad?
Over time I've come to realize that just about every good piece of advice is actually a special case of something both more general and simpler. So, let me introduce you to the "one rule to rule them all." [...]
TIMECODES
00:00 Intro
02:28 Back to the 1990s
03:57 Classic waterfall
06:14 Theorem proving
06:58 100% test coverage
08:17 "Correct code"
12:05 Dave's postulate No. 1
13:50 Change
16:18 Manifesto for Agile Software Development
19:58 Agile is Dead • Agile is Dead • Pragma...
23:23 Easy to change
24:20 How?
32:41 Dave's postulate No. 2
35:07 Building intuition
37:37 Conscious & subconscious
43:31 Experience
46:37 Handwrite on paper
50:27 Make it easier to change
50:48 Outro
Read the full abstract here:
gotoams.nl/2023/sessions/2481
RECOMMENDED BOOKS
Dave Thomas & Andy Hunt • The Pragmatic Programmer • bookshop.org/a/9452/978013595...
Dave Thomas & Andy Hunt • The Pragmatic Programmer • amzn.to/3N3i0GP
Dave Thomas • Programming Elixir • amzn.to/3Dl6fY7
Dave Thomas & Sam Ruby • Agile Web Development with Rails 7 • amzn.to/3TuWuxj
Daniel Kahneman • Thinking, Fast and Slow • amzn.to/2XmJEtf
W. Timothy Gallwey • The Inner Game of Tennis • amzn.to/3pjol9M
/ gotocon
/ goto-
/ goto_con
/ gotoconferences
#Agility #AgileIsDead #TypeSystems #Intuition #Programming #PragmaticProgrammer #SoftwareEngineering #SoftwareDevelopment #DaveThomas #PragmaticDave
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.
czcams.com/users/GotoConf...

[@InfectedTofu]

Always a pleasure to listen to Pragmatic Dave

[@ManfredWisniewski]

I'm so happy I kept on watching after the somewhat long winded start. Such a treat with astonishing depth. Thank you Dave! You made me happy today and I will do my best to pass on the fun

[@johanngerell]

Exceptional! 👏

[@chrishabgood8900]

ruby Dave since 2007!!

[@Nellak2011]

Writing good code is more than correctness and code that anticipates change, it is actually multi-faceted.
- Correctness (Pursuit of)
- Change
- Maintainability
- Performance
- Security
- Re-usability
- ... etc
So to focus solely on one of these things at the expense of others is foolish.
The best solution is to analyze your problem domain and determine which subset of these you want to prioritize, and then lazer focus on those.
For example:
If you are writing a school project, you may prioritize correctness and re-usability over performance or security.
If you are writing code in a startup, you may instead prioritize change, maintainability, reusability, and performance.
It just depends on what domain and problem you have at hand. You can't focus on all aspects, so must make sacrifices somewhere to optimally balance them for the problem at hand.
However, you should also at least attempt to incorporate at least a little bit of all of them to ensure that your code quality is as high as you can feasibly implement.

[@justwanderin847]

I was programming in the 1990's and we used waterfall and Structured Analysis and Design and Programming and we DID go back are re-evaluate