Joe learns of our harebrained idea, Michael learns of Eisenhower’s matrix, and Allen explains polyfills as we begin our dive into Uncle Bob’s latest book, Clean Architecture.
Prefer to read these show notes on something other than your podcast player? You can find the full show notes for this episode at https://www.codingblocks.net/episode68.
- Linode – Use code “CODINGBLOCKS17” for $20 towards hosting (up to four months free!)
Survey says …
This episode, we ask: How often should your employer replace your computer?
- Thank you to all of you that left us a review!
- iTunes: The Real Brian Choi, Attalus, PizzaHd88, scubasteve636, jdmerth, James Strugnell, AlFraken, Mikeydon
- Stitcher: theCoz, SVad, tvStevens, 85ustorm, Mik_Lik, fraben, Jerry4592
- Podchaser: GaProgMan, Dance2Die
- Veselin Vasilev calls us out on estimations – https://www.codingblocks.net/episode66
- Azure Red Shirt Tour – FREE!
- Allen and Michael attend another great Connect.Tech conference
- Allen’s shopping around for mesh networking and the candidates are:
About the book
- Part of the “Robert C Martin Series”, just came out – other books:
- Clean Code, Clean Coder, Clean Architecture, The Software Craftsman
- Billed for Architects, analysts, designers and managers
- We’ve heard it’s been selling out / hard to get
- Why the hype?
- “The rules of software architecture are independent of every other variable”
- And kinda…programming hasn’t really changed a whole lot
- Getting something work once isn’t hard…?
- Why does being “right” matter?
- Effort is minimized, functionality and flexibility are maximized
What is Design and Architecture?
- Difference between design and architecture? None!
- “The goal of software architecture is to minimize the human resources required to build and maintain the required system.”
- Is the goal to write yourself out of a job?
- To put another way, the measure of design quality is the measure of the effort required to meet the needs of the customer
- How do you know if your architecture is wobbly: Is the effort to make changes rising?
- Great graphs comparing number of programmers, program size, and cost / LOC
- “Later” is “never”…but what about focusing on an MVP
- Maybe clean architecture should be an intrinsic part of your MVP!
- The BIGGEST Lie: Writing messy code makes you go fast in the short term
- “Slow is Smooth, Smooth is Fast”
- “We can clean the code up later, we just have to get to market first!”
- Staying clean always takes less time than cleaning up messes…
- “The only way to go fast is to go well…”
- So, what’s the solution if you’ve found yourself in this mess?
- Rewrite? NO! That’s the hare talking again, the same hare that got you into this mess!
- What you should do, is to own your mistakes and start taking quality seriously
A Tale of Two Values
- Developers are responsible for structure and behavior
- BOTH should be high, and in balance
- Behavior (aka “features’) and Structure (aka Architecture)
- Software is supposed to be “soft” – meaning easy to change!!
- The difficulty in making a change _should_ be proportional to the SCOPE of the change, not the SHAPE of the change
- From the stakeholders perspective, they provide a stream of changes of roughly similar scope
- From the devs perspective, they are rearranging pieces of an ever-increasingly complex jigsaw puzzle
- Shape and Scope are out of sync!
- Would you rather have a system that works, and is difficult to change – or one that’s busted, but easy to change?
- Now, think about this problem at the extremes…
- Eisenhower’s matrix
- Behavior is urgent
- Architecture is important
- People tend to move urgent and not important to urgent and important
- Yeah, right – tell that to my manager! NO – it’s YOUR job to evaluate and express this to your manager
- It’s up to you to fight for the architecture, just like other departments in the business have to fight for what’s important to them
- YOU are a stakeholder!
- How do you fight? lunch ‘n’ learn, encouraging conferences, 20% projects, Unit Testing
- Devs need a seat at the PM table?
- Keep devs closer to the domain experts!
- How to push back?
Resources We Like
- Clean Architecture by Robert C. Martin (Amazon)
Tip of the Week
- Always explicitly select the column names for your views. If the underlying table is changed, the view is not updated if you created it with select *.
- Web APIs (MDN)
- Sketchnotes 101: The Basics of Visual Note-taking