After one release that goes well, you’re perfect. If your second and third ones go just as well, you’ll maintain that perfection. But eventually, the more you do, the greater you open yourself up to the chance that something will go wrong, that you won’t have the perfect release. That your code might blow up. That a bug might get missed. What factors outside of your control will cause you to slip? Because presumably, you…
If you’re in a room and everyone is staring back at you blankly, you’re not all on the same page. If you’ve just had a call and discussed half a dozen ideas with no confirmation as to who is doing what, you’re not all on the same page. You can tell the teams that are on the same page from afar, they are all working together, each person knowing their part and role that is…
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…
Maybe make a plan (I do this from time to time). Writing it down helps (I heard and have tried). Committing to a schedule (yes this is definitely great). Get a support group (this never helped me too much). Break it into smaller tasks and when you’ve mastered one task, move on to the next (this helps greatly). Always keep challenging yourself with variations on what you are doing (prevents falling into a mold). But…