Work smarter

This is my light-hearted attempt to help engineers get the most value out of a downtime incident.

If you "write code" for a living, chances are you have a one time described yourself as a "Software Engineer".  And chances are, you are not.Personally, I graduated with an Engineering (Software Systems) degree...

In the previous post, we examined the Why and When of testing in this post, we will build on that foundation and look at How much we should be testing.

This is my light-hearted attempt to help engineering managers get the most value out of a downtime incident. Introduction So you had an incident? Condolences.On...

Friends & fellow coders, I am overjoyed to share that part 2 has finally arrived. In this book, I share my secrets to writing high-quality Go code efficiently, effectively, and productively. It contains practical approaches to software engineering, software design, and code UX that will set you on the path to success. As you may know, in part 1, we focused on making our applications faster; part 2 focuses on making the programmer faster. As the DORA study has shown, writing high-quality code is key to delivering software quickly. For others, please pick up your copy of the book at your local Amazon website or your preferred bookstore.

Just dropping a quick update to let you know that Beyond Effective Go part two is finally going off for professional editing tomorrow! After the tremendous response to part one, I'm determined...

In the previous posts, we examined the Why, When, and How Much of testing. In this post, we will complete the thread with an examination of What we should be testing and What we should not be testing.