Microservices

Good developers follow the principle of Don’t Repeat Yourself (DRY) when writing code. When faced with duplication, they refactor it to be shared—increasing the code quality and maintainability. I have found that in the microservices world, the simplest way to reuse code is in the form of an external library.  Use of such a library, however, is contradictory to the aim in microservices development to maintain autonomy (and development/deployment independence).  Read More…

Pragmatic Thinking

A few weeks back, we finished a book club session on Andy Hunt’s ‘Pragmatic Thinking and Learning: Refactor Your Wetware’. I really enjoyed the read, it was filled with tips and tricks on how to use your brain more effectively, brought together visually with a Mind Map at the very beginning of the book.
Read More…

Several years ago, I joined a team in their early days of developing a claims product. When I came onboard, the team was small but was expected to grow significantly. While the analysts and business leads were busy identifying the product scope, the technical members of our team focused on the platform. Read More…

Doc Norton opened the conference with a keynote session introducing the topic of Host Leadership and drawing parallels to this style of leadership. He used personal experience of hosting a Euchre party for his community with the intent of bringing everyone together, incorporating a nice mix of traditional and servant based leadership principles. Read More…

Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite. Objects make the cost of this transaction tolerable. The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt. Read More…