Print Story Professional development
Diary
By sven (Fri Oct 29, 2004 at 10:36:25 PM EST) (all tags)
I had my professional development discussion at work on Friday, focussing on taking on the responsibilites of our soon-to-depart tech lead. Overall I'm very happy with the outcome.


Professional development discussion

I am now the tech lead for our team of four. Unlike our outgoing tech lead, I'm only going to be responsible for the technical aspects of the job. The managerial aspects will be handled by someone else. This is a pretty good outcome for me, because I'll be able to focus on enhancing my technical skills while broadening my role to include new aspects such as requirements analysis.

Another outcome of my professional development discussion is that I'll be able to focus specifically on improving my C++ skills. Since there isn't a lot of new development work left on our project, I'll be somewhat limited in opportunities to apply these skills directly. There may be some opportunity to work on various utilities for testing and performance metrics, but I'll also be allowed to spend time just learning without any immediate benefit to the project. I'm going to join the ACCU (my employer will probably pay for it). Later in the year I might look at developing some sort of C++ best practice guide.

As the development effort of our project ramps down, I'll also be given the opportunity to use my domain knowledge to assist with safety analysis. I'm not sure exactly what's involved but it will probably be identifying and analysing potential hazards. I don't expect there will be much coding involved, but it should be interesting.

I'm hungry now

I think I'll cook up some pasta. I'll use a tomato, onion and mushroom sauce in a jar, and add ham, mushroom, onion, olives, capsicum, and spices. Should be good...

< Critical Mass | BBC White season: 'Rivers of Blood' >
Professional development | 4 comments (4 topical, 0 hidden) | Trackback
Sounds like it worked out ok by cam (3.00 / 0) #1 Sat Oct 30, 2004 at 01:10:33 AM EST
Personally, I enjoy writing technical documentation on things like software development, quality control practices etc.

cam
Freedom, liberty, equity and an Australian Republic


We have professional development plans by Rogerborg (3.00 / 0) #2 Sat Oct 30, 2004 at 08:39:51 AM EST
Indian coders just write code.

Hmmm.

-
Metus amatores matrum compescit, non clementia.


coding guides by Sesh (3.00 / 0) #3 Mon Nov 01, 2004 at 04:38:51 PM EST
Congratulations on the new position... hopefully you'll be able to exert some influence.

I've found that the greatest danger in writing a coding standard is to put too much information in. A coding standard shouldn't try to resolve star-wars, document good bracketing style or provide a how-to guide on coding. These go against some people's grain and if they ignore one part, they'll inevitably tend to ignore the rest. And I'll never understand where that bullshit 'don't put #include directives in header files' thing came from, but it alone pretty much made a joke of the whole C coding standard at that particular unnamed workplace.

Instead they should probably outline good, or even essential practices that apply in your workplace that help with the tools you use, (Razor, obfuscated make system, logging system, whatever). And it probably helps to take into account whether you are coding in C++ (with exceptions, polymorphism, etc) or in C using a C++ compiler with classes and inline comments. Overall, it's easy to write a coding practice's guide (I've written two so far), but very difficult to write a good one that actually proves useful (I've yet to write one.)

Sutter and Andrescu have just written a book called C++ Coding Standards that purportedly has a bunch of practical suggestions in it. I've found Sutter's opinion on writing coding standards pretty helpful in the past.

Also, when you start reading about good C++ practice it becomes tempting to start applying the latest bit of knowledge in every situation you come across. I've written heaps of code that shouldn't have ever existed because of my starry-eyed wonder after reading the wonderful Gang Of Four Design Patterns book, or Andrescu's Modern C++ Design. Stroustrup's book is good for practical suggestions - no beefcake design patterns, but simple utilities (see RAII)



Tech. lead position by jarvo (2.00 / 0) #4 Wed Dec 01, 2004 at 04:09:08 PM EST
I said that I wanted to get some tech. lead experience two years after I started work at ADI. I was turned down because management thought I was more of a technical person.

They were right in one respect; I would have hated the spreadsheets, meetings, etc.

Congratulations anyway Steve. Maybe now you can try and stop some crap design decisions... You'll have your work cut out - Luke's been trying that for years.




Professional development | 4 comments (4 topical, 0 hidden) | Trackback