Articles for category: Delivery

September 19, 2022

Greg Thomas

Keep it Simple

Complicating it, providing options, features, checkboxes, and radio buttons. We think it makes it better, but all it does is complicate it. Make it do what it was supposed to do, make it simple, and make it clean. That’s what your customers are here for.

September 16, 2022

Greg Thomas

Code like a Game Developer

I’ve always thought of Game Development Coding as the pinnacle of update distribution.  The next time you are using STEAM to install a new game or even the company’s own updating software (Battle.NET), watch how it handles updates, patch management, distribution of code, and pushing out updates to the community. Your first experience is in getting the application into your hands and using it.  They know this, they know the smoother, the easier, and the more reportable this feature is, the more receptive you’ll be when things go wrong in the application itself.

September 15, 2022

Greg Thomas

Establishing the Baseline

If you don’t have a baseline, you don’t know where you are starting from. If you don’t know where you are starting from, you can’t create a plan because whatever plan you come up with will be based on something that may or may not exist or may or may not be correct. Baselines set the foundation from where we start, they are ground zero and they are the point from which we move forward from. If the starting line of the 100 meter dash was constantly shifting, we would never know who the actual fastest person in the world

What Good Architects Do

Good Architects find the bad in a design that you might be in love with and perfectly aligns to your comfort design. They look at what you’ve done and show you where it could fail and point out gaps you might have missed. They are the second set of eyes that raises the game of your code and ensures you are learning new things all along the way. In short, they ensure quality is delivered, while leading the growth that is change in what you build.

September 7, 2022

Greg Thomas

Broken Automations

Automated code will break. It will break because something that it is supposed to work with broke, something that it expected to be there is no longer there and now it is broken. And now we fix it and re-automate it. Automations are not invulnerable, we just like to think they are because most of the time they run unattended.