Video notes and comments on Dave Fariley's Youtube video on this subject.
When programming it is ideal to always optimize for faster iterations, but what about learning?
What are some questions every engineering department should try to answer?
I decided I wanted to write about flexible versus rigid systems because I observed a pattern emerge over and over in projects and open source libraries. While observing this pattern, I noticed how it impacted our perception of the codebase in the early and later days.
Intrinsic motivation is when you engage in a behavior because you find it rewarding. Do you understand how you can use this to make healthy software engineering teams?
How about a "Documentation Oriented Programming". You write a document as you work on the problem with the how/what/why. It could be: shared, referenced, and posted.
Code comprehension represents the largest amount of time spent with a codebase
For better developer experience always prefer an explicit pattern. Here is why.