Every team has them. The “Ism” – the CodeIsm, the EnterpriseIsm, the SupportIsm. They are the ideas, the culture, the vernacular that makes your team, your team and separates it from everyone else. They are the rallying cry for getting things done and delivering. They are a good thing to have as long as they project the good of your team and not the “that’s the way we have always done it”, “that’s how it…
What I admire most about video games, is their resiliency to consistency deliver updates. Maybe I’ve been lucky but when I look at the games I’ve played, and how they are updated I can’t help but think that this is where the time was spent first – on the Updates. The team figured out the problem they hoped they would have forever. Pushing out changes and ensuring they don’t impact their customers from using their…
Team Leads and Tech Leads are two critical roles in any software development team. But go from team to team and you’ll find the roles and what is required of them are drastically different. Here’s my take on the difference between a great Tech and Team Lead.
I can build you a tractor or a Cadillac (perhaps there are better terms to use today but I still like these). A Tractor will get you there, wherever you are going, without fail, it will be solid, it won’t breakdown and it will do the job (i.e., work hard). Tractors don’t mind getting dirty because it’s all part of what they do to get the job done. A Cadillac will get you there, but…
Using an API is a great way to save an immense amount of coding time and get your work out faster. As a distributor of an API, it’s a brilliant way to give access to functions of your product that allow additional uses for your work to propagate without you needing to build them. You build the interface, they consume it. You consume the interface, and someone else maintains it. The thing to always remember…