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.
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…
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,…
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.
Wheels haven’t changed much since they were introduced. They are still round. The primary concept still holds true. Sure we dress them up, build them with different materials, for different terrains, for different uses, etc, etc, but the primary concept still holds true – they are round and they move forward. The same is true for many software development concepts where you do not need to go and reinvent the wheel, but rather just use…