What I Learned in 2017
Posted on
As I'm constantly learning new things, I have found that many of the things I have learned either don't merit a post on their own, another post has already been written and I don't have anything to add beyond what has already been said, or I just don't have time to write a whole post on a given subject. So it's nice to have a collection of ideas. So I came up with the idea to create a summary post that can serve as a bin of sorts. A year seems like a reasonable amount of time in which to bin things, at least for right now. Perhaps I'll modify the structure in the future.
Software Practices
- Various ways to ensure code quality
- All code written in a branch and submitted as a PR. Two peers review every PR.
- All code written in a branch and submitted as a PR. The code is reviewed by one peer and one tech lead.
Architecture
- Domain-Driven Design, I finally read the book!
Technologies
- Node.js
- mongoDB
Tools
Infrastructure
Design Patterns
Organizational Practices
- An agile organizational structure similar to Spotify. (Pluralsight also models this org structure, although I didn't read the source material behind the ideas while I was there.)
