Home » Posts » One Rule to Rule Them All • Pragmatic Dave Thomas • YOW! 2022 Provided By www.bobanddougmckenzie.com
One Rule to Rule Them All • Pragmatic Dave Thomas • YOW! 2022
Witness the vid “One Rule to Rule Them All • Pragmatic Dave Thomas • YOW! 2022” and tons other videos which include the famed hysterical characters of Bob and Doug McKenzie.
Bob and Doug McKenzie in One Rule to Rule Them All • Pragmatic Dave Thomas • YOW! 2022
In the video One Rule to Rule Them All • Pragmatic Dave Thomas • YOW! 2022, Bob and Doug McKenzie are a couple of hilarious Canadian comedians who are responsible for “Great White North”, a skit which was streamed on second city television for the show’s third season when it got sold to the Canadian Broadcasting Channel in in the early 80s. Bob’s part is brought to life by hilarious comedian Rick Moranis and Doug’s part is played by Dave Thomas. The bit was born originally as an idea to both satisfy and laugh about dumb Canadian content guidelines, the characters transformed into a pop culture hit in both Canada and the States. The brothers became the focus of a an amazing comedy album, The Great White North, in 1981.
This presentation was recorded at YOW! 2022. #GOTOcon #YOW
Dave Thomas – Author of The Pragmatic Programmer @pragdave
RESOURCES
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
00:57
01:40 Agile software development
03:47 Classic waterfall
05:26 Theorem proving
06:24 “Correct code”
09:01 Dave’s postulate No. 1
10:28 Change
13:21 Easy to change
14:40 How?
20:57 Dave’s postulate No. 2
26:35 Building intuition
30:10 Experience
34:22 Handwrite on paper
37:36 Make it easier to change
38:33 Make it fun
38:38 Outro
39:00 Q&A
Read the full abstract here:
RECOMMENDED BOOKS
Dave Thomas & Andy Hunt • The Pragmatic Programmer •
Dave Thomas & Andy Hunt • The Pragmatic Programmer •
Dave Thomas • Programming Elixir •
Dave Thomas & Sam Ruby • Agile Web Development with Rails 7 •
W. Timothy Gallwey • The Inner Game of Tennis •
#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
Sign up for updates and specials at
SUBSCRIBE TO OUR CHANNEL – new videos posted almost daily.
Other Videos Related to One Rule to Rule Them All • Pragmatic Dave Thomas • YOW! 2022
[random_line] – [random_line] – [random_line] – [random_line] – [random_line] – [random_line] – [random_line] – [random_line]Popular Search Terms For This Page
– bob and doug mckenzie christmas
– bob and doug mckenzie movie
– bob and doug mckenzie the great white north
– bob and doug mckenzie 12 days of christmas hq
– bob and doug mckenzie rush
– bob and doug mckenzie great white north geddy lee
– actors
– beauty eh
– donuts
– movie
– two four anniversary
source
dave thomas go to GOTO,GOTOcon,GOTO Conference,GOTO (Software Conference),Videos for Developers,Computer Science,Programming,Software Engineering,GOTOpia,Tech,Software Development,Tech Channel,YOW!,YOWcon,Dave Thomas,Pragmatic Programmer,Pragmatic Dave Thomas,Agile is Dead,Intuition,Agility,Agile Software Develpment #Rule #Rule #Pragmatic #Dave #Thomas #YOW
Great talk as ever. I would just add one more thing to the one rule so it reads "Make it easy to change with confidence". The with confidence is important because it covers automated testing and security.
Automated tests and TDD are a good example of supporting the “with confidence” suffix. You could argue that a dogmatic approach to tests and TDD can actually make it more difficult to change — but, at least a pragmatic approach to TDD is required for the confidence piece of the equation.
Another good example is security. Security controls do not make it easier to change, just like having to take your shoes off does not make it easier to fly. However, security controls and practices certainly fit into the “with confidence” suffix.
"requirements used to change at the rate of about 20 percent per annum and it's feeling to me that that's dropping down to about every 20 every maybe two months at the moment". Are they any real source for said claim? What does Heisenberg's uncertainty principle, which applies to quantum mechanics, have to do with software projects? Even if it did why what is position and momentum of software? Why do you need to know those with absolute precision to ship business value? "Code that is hard to change will never be correct"? Huh? Those are two different things that you need to make an argument are linked. That requirements change is rather implicit… we know a code base change uniformly, right? Just before you said no non-trivial code was correct. No qualms with the message that it's important to make code easy to change.
Great talk and as a personal bonus some of my favorite people all bundled together. Dave Thomas (my favorite presenter), Leonard Cohen (quote at the end), and Peter Drucker (not quoted directly, but the same ideas on estimating and documenting work to gain intuition).
My new favorite quote
"Write Rails from scratch" – Dave Thomas
« Compositionality allows a small change in requirements to translate into a small change in code.
Compositionality is the single most important factor in determining the cost of code maintenance. » John A De Goes
« I teach in functional design that orthogonality is an essential component of 'good' compositionality, one that aids the modularity requires to minimize maintenance costs. » John A De Goes
Another nerd who has never seen anything beyond his own desk.
There's not much new in this presentation. Robert C. Martin told us in 2012: "The primary value of software is that it is soft." But the secondary value is still there, that it is does what the customer asked for. And a customer won't be happy with a buggy software, so we should not downplay its importance. These 2 values balance each other out perfectly because if you make software too easy to change, you also make it too easy to introduce the wrong kind of changes, i.e., bugs. Code with zero dependencies leads to too much repetition, and the code smell of fragility. This presentation thinks in extremes when in fact extremes don't work. It's the right balance between sides that works.
We don't use magic numbers because they might change, we use them because it's not always obvious what the number means. Eg ints in a switch.
Zero dependencies is the guiding principle of Words and Buttons Online. Not only third parties, not even inner dependencies. 5 years in production, over 50 interactive pages, and, since there is no dependency hell, each page is less than 64 KB along with JS and CSS. Ridiculously easy to maintain, and fun to work on. It started as an experiment, now I don't want to do things in any other way.
Not a fan of Agile. We call it, mini-waterfalls