Chapter 5: Deal With Technical Debt and Slop Seeing legacy as tech debt that has been acquired Slop as source for sloppy code Chapter about understanding the difference between slop and technical debt. Many developers, if they are feeling pressured to complete their work, would call this an acceptable compromise, promise to fix it later, and ship it
(p. 70)
Technical Debt is […] used to explain compromises in implementation that save cost now, at a larger future cost (just like real debt).
Chapter 3: Fix bugs efficiently and cleanly In the beginning, you will be given tasks that require no in-depth domain knowledge
Process A process allows you to focus on the right thing at th right time (p. 14)
It will make your productivity and quality more predictable, which, in turn, will help you estimate and keep more of your promises about your work (paraphrased from p. 14)
TDD Explains some benefits about TDD:
Yesterday I attended an Agile Barcelona open space at Netmind
Format On arrival, attendees where welcomed by an Agile Coffee.
At 10:00, the introduction started: a warm welcome to everyone, including first-time attendees to an open space, explaining what it is, the few rules and laws and making sure everyone had fun. Some time later, the marketplace happened and everyone presented their sessions. A curious thing to see was the effect of a session that everyone wanted to attend (dubbed a ‘black hole’).
The real reason why the Spotify model is broken I’ve read this article by Sharky Laguana, comparing several royalty models for spotify
Tags: sharky-laguana, spotify, comparison, royalty
[Day 3 of 7] “Badass” developer gets a RUDE awakening I’ve read this email that John Sonmez sends, about being a programmer vs a language programmer. Some quotes:
Someone who could tear apart complex, confusing puzzles and engineer elegant, reliable solutions… whether those challenges were software, hardware or “wetware.
10 Myths About Docker That Stop Developers Cold I’ve read this listicle of docker myths. By Derick Bailey
Tags: derick-bailey, docker, myth
Bored People Quit I’ve read this article by Michael Lopp on what are some mechanisms why bored people quit.
Some interesting quotes:
My gig is the care and feeding of engineers, and their productivity is my productivity. If they all leave, I have exactly no job.
My job isn’t just building product; I also build people.
Books I’ve read this quarter1:
Books started, not yet finished (WIP):
Books I want to finish. Usually come from another quarter:
Functional Programming in Scala, by Chiusano and Bjarnason. Doing the exercises with the codurance team Gödel, Escher, Bach: An Eternal Golden Braid, Hofstadter Books that have entered the queue:
Non-technical that have entered the queue:
The ending date of the quarter is the same as the publication date ↩︎