Articles for category: Initiative

Writing Better Tests

There comes a time in every developer’s life when they realize they need to write better tests. Whether it’s a console, web, or unit test, they need to write better tests. If you’re at this point, here are some elements that are important to writing great tests; They should be objective – the result is the result is the result – there is no complex interpretation. They should be measurable – whether they do it or not and how fast or slow do they take. They should NOT require intervention – if someone has to flip 15 switches and jump

July 20, 2022

Greg Thomas

A Workable Space

All our spaces are changing. Where we work, where we live, what we do when we are there. They are changing into something different that enables us to define the area where we are at our best and most productive. And productivity is key to a workable space.  The bean bag chairs never did it for me unless I was using one app to do one thing where I could sit there and type. But if you want me to crank out work at a minimum of 100%, the bean bag/coffee table isn’t going to make me my most Productive.

What every bit of code you write should have

It should be testable. It should defend. It should be clear to understand. It should catch errors. If it is not the sole source of all the logging, it should provide valuable fragments that render what it logs usable. It should do what it is meant to do, not what we hope it to do

Cloud Hides the Bad Code

Yes, it does, there is bad code in the cloud, not all code, but a good amount. Because you can easily throw more “stuff” at it to make it more “elastic” and “spinning” up things makes it more performant. These tactics work in the short-term and get you out of a jam, but that’s all they are meant to be, if your code is performing badly, no amount of memory will ever make it run better. If you have a leaky roof, you don’t keep putting more and more shingles on it each time it leaks, eventually, you need to

Where your Debt Lies?

Every application has some level of Technical Debt. Some of it exists in our tracking systems, but most of it exists in our minds, slack channels, or forgotten conversations we have with each other, later to be forgotten when we start on something else. One of the hardest jobs of being a Software Manager is being able to enunciate where your team’s debt is and push the work that needs to be done, to get done, to make it better. It’s not a glamorous job and not everyone always wants to hear from you when you talk about it often