It has been a challenge to keep my personal blog from becoming inundated with the rants and ravings of my technical and professional experiences so I have therefor decided to start a blog on my resume site. I have imported a few posts via the Programming category to put some content here so please pardon the duplication.
This last week I was promoted to Client Software Development Lead. I am excited to take on the role and cannot wait to see what I can accomplish. It seems, for now, that my goals are fairly cursory for a lead position:
- Establish a general culture of documentation. Whether it be a change list for certain libraries, classes, JavaDoc, or APIs us developers tend to have a hard time keeping track of the things we write and then keeping those things up to date as things change.
- Unit testing. At least for things in our libraries. Understandably, mobile software tends to have more user interaction code where this is not unit testable. However, there are several key library packages that handle data, network, databases, and other things which can be unit tested.
- Get the team communication flowing. This involves communication both internally and externally. Each team member can potentially disappear in a cave and then we may be unaware of what that member has been up to and conversely, that member may have no idea where things are headed. I think regularly discussing and sharing the trials and triumphs of the week encourages team cohesion although if you add donuts to the equation the effects are much more effective.
These are just some rough outlines of what I’d like to do. Obviously, I still have my work as a developer. There are quite a few other things to do and watch. Overall, I think things I listed here, again, are pretty normal to hear from things that teams can be doing better.
