For whatever reason, this big picture knowledge about how to bring everything together to make effective software is rarely taught explicitly. Rather we mostly see guides to the latest syntax or features of the framework du jour. Having been in this game for over a decade, I know full well this sort of surface knowledge has the shortest shelf-life.
If you've got more of a taste for the slower-changing, thoroughly unsexy principles behind writing stable and maintainable software, I'm devoting myself to exploring these ideas with my screencasts - topics like data integrity, building instrumentation for knowing what's happening in your code (esp. in production), non-brittle tests, leaning on unix tools and the OS to debug things, the timeless editor vim, etc.
The first 12 videos are available over at https://www.semicolonandsons.com/ -- it's a new side-project of mine that I hope will bring some value.
If you've got more of a taste for the slower-changing, thoroughly unsexy principles behind writing stable and maintainable software, I'm devoting myself to exploring these ideas with my screencasts - topics like data integrity, building instrumentation for knowing what's happening in your code (esp. in production), non-brittle tests, leaning on unix tools and the OS to debug things, the timeless editor vim, etc.
The first 12 videos are available over at https://www.semicolonandsons.com/ -- it's a new side-project of mine that I hope will bring some value.