|
Our department consists of a dozen programmers, at least from an org chart perspective. By product, it varies from half an engineer (a part-time thing) to five or six. None of us are full time on just a single product.
I work on four current products plus The Big New Thing™, along with being Departmental Sh!t-Job Boy. As the DSJB, I get to write all of our internal documentation, maintain our department server, console our SourceSafe data base when it's feeling emo, and in general do all the crap jobs nobody else wants to do properly.
The context switching can be murder; in a given day I've switched back and forth between three or four projects multiple times.
Software Zen: delete this;
|
|
|
|
|
Then I would say it's twelve, but that's just me.
|
|
|
|
|
That's why I selected the 10-15 option.
Software Zen: delete this;
|
|
|
|
|
Same here. There are 5 of us in the room, we each have our own segement of the "Big HR project". Sometimes we work together on the same sub segment and sometimes we don't. We double up for support too so we can know more then one segement of the project. Plus I have one older project in VB.net.
|
|
|
|
|
It's pretty tangled. We have two major products under maintenance, one new product about to be released, and The Big New Thing™ under development. The maintenance products have anywhere from two to four branches that are actively being worked on. The new product will acquire a maintenance branch at the release date.
The fact that there is a lot of commonality between the products means that, if we fix a bug in the common code, we may have more than one branch to fix it in. I've occasionally had to make the same source change to over a dozen branches  .
The one thing that helps is that each of our roles are pretty sharply delineated, so that regardless of the product or branch, we usually know who to go to when there's a problem.
Software Zen: delete this;
|
|
|
|
|
It may not matter, but what about dedicated programmers versus parttime? We work for a school district. There is the "team leader" who spordically programs nowdays (administrative work), the "network specialist" who has recently begun pitching in the programming and moi, the "programmer". So to be technical, we have 1 full-time programmer.
THANKS for all the insight and laughter on the posting!!
|
|
|
|
|
Kinda the same thing in our company, the only difference being it's less people on one project. There are only two of us that are working on the system full-time, with three others working on components off and on as they get time. This, of course, leads to much griping about the quality of the code being checked in, as well as some grumbling about whether or not said people should even be working on the system. The two of us usually spend our days putting out fires across the whole project.
And to think we're under a hiring freeze...
“Acer, Gateway, and eMachines are the same company now. Great! Now we just need a really big toilet, and we can get rid of all three at once.”
|
|
|
|
|
Team size seems to vary now-a-days where I'm at. Before, we were 20+ strong but now things have changed and are hovering around 15 or so.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
