Talk with David Gregg:
Learning how to write quality, maintainable code has been a question left to intuition, personal reinvention (after repeated failure), and the memorization of maxims such as "Tell Don't Ask", "Feature Envy", SOLID, et al.
But can we compare these maxims – these learned lessons – across paradigms, and arrive at a generalization which serves as a sort of guiding "Grand Unified Theory of Software Development" (Jim Weirich)?
Some of this work has been done, and the resulting concept and vocabulary is not only simple to explain (and immediately applicable) to early learners, but can serve as a metric for quantifying maintainability and refactoring opportunities at all levels of software architecture.
Talk with Matt Swanson:
Who is David Gregg?
David has been fiddling with code for more than 20 years and is a founding Instructor of Kenzie Academy. Between his time with Kenzie and previous experience as an instructor with The Iron Yard, David has taught software engineering to ~200 students and trained dozens of coaches.
Who is Matt Swanson?
Matt Swanson leads teams and build products for customers at SEP, a software product design and development agency in Carmel. He’s been using Ruby in some capacity since 2010. His favorite Ruby method is Array#compact.