Brian Lamar

Background

About Brian Lamar

Quick Thoughts- Write more code that is straightforward and testable rather than less code which is complex - Service boundaries are hard to draw, but immensely helpful - Explicit > Implicit - Velocity can be increased by having testable code. It's never too late to automate your testing- Composition over inheritance - Improvement can't exist without measurement - Customers are not test subjects (unless they want to be!) About Me: I'm a maker. I get joy from making things people want. However, programming is not just about making. It's about the process. It would be nice if programing was the same as woodworking. I'd make a program, sell it, then never have to touch it again! The reality is, good programming is about long term planning and foresight. Frameworks (and even languages) come and go. Libraries are updated. Exploits found. Systems patched. Vendors ebb and flow. Good code is merged. Bad code is merged. It's my job to try and mitigate the effects of time on the programs and services I'm responsible for.