I would do the first or second one. As the team gets larger you will be given a more reduced roll. If you are working with only a few other devs you will probab

I would do the first or second one. As the team gets larger you will be given a more reduced roll. If you are working with only a few other devs you will probably have the chance to make decisions that influence the product, and if you stay long enough you'll be able to see the consequences of those decisions. Number 3 sounds cheesy. Pair programming sucks, and the description you gave sounds like its straight out of a marketing flyer.