Best way to prepare for a programming group?

Question

I have been working on my own in programming with the exception of stackoverflow.com and I was wondering is there a way to prepare for group programming if I want to go into a company or programming group?

Answer 1

Be good at programming.

Answer 2

You might try collaborating with others to help out on an open-source software project. Not only does it give you an easier way to practice working with other developers in a more "relaxed" environment, but you also get the side benefit of helping out with OSS. ;)

Answer 3

Humility would be a good trait to have. It is unlikely that you will always agree with the people around you all the time. Learning how to react to constructive (or even non-constructive) criticism in the correct way will reap big rewards.

Answer 4

Here are a few tips that should help you fit in with a group:

• Learn how to use source control (for example, SVN or GIT)
• Practice reading and understanding other people's code (take a look at some open source projects)
• Since you'll have to communicate with the group, it may be worth joining a local dev group that interests you to practice listening and sharing technical knowledge

Answer 5

In the most honest way possible, find a different nick. Hacklord in l33t is nearly at the bottom of nicks you can pick in terms of what it connotes about the person behind the screen.

In terms of group programming, I suggest finding a smaller open-source community to contribute to. Maybe find someone at your school who likes programming as well and work with them on a project.

edit: Just in case you didn't know(because there was a point I didn't know), 'hacklord' suggests a 16-year old guy in a basement who thinks he's all that and doesn't shower. "Script kiddie". Leet speak in a serious context(like a nick/handle/alias) suggests that you are not only the 16-year-old-in-a-basement, but that you are absurdly immature with aspirations of being a black-hat hacker breaking into things. Granted, some of the phone phreakers use those kind of nicks. However, most programming projects of worth are not populated by overt phone phreakers, and try to maintain a fairly professional(ish) and mature(ish) attitude. Stackoverflow in particular is notable because its culture uses the Real World name, and thus the major nastiness from anonymity is removed from the discussion(See the Penny Arcade comic stating it).

This isn't to encourage you to give out your real name(your profile says you're 15 and thus may not want to give it out), but to pick a name that connotes something professional programmers won't flee from.

Answer 6

• Shower. Daily!
• Be strict on output, forgiving on input (with people as well as with code).
• Always show up.
• Be humble so that you will learn easily
• Have fun so people will enjoy working with you.
• Never turn down an opportunity to help someone else.

Answer 7

lots of coffee for everyone!

Answer 8

Be aware of these facts:

1. You are not always the smartest person in the room
2. See #1
3. Good insight can come from even the dimmest bulb on occasion.
4. Pick your battles. Not every line of code has to be written the way you would have written it. See #1 and #3.
5. Seek others advice. This is crucial. You may be incredibly good, but keeping communication lines open and active is key to team survival.
6. SHOWER OFTEN
7. Write and speak professionally. In my world, 1337 speak is wonderful in that it lets me know immediately which voices should be ignored, despite #1,#3,#4,and #5. Good communication skills are a requirement for success in any field.
8. Have pride in your work, and do a good job! You're in this field for a reason. While we can't all pick and choose the apps we're working on, we can realize that every thing we do is an opportunity to build something great.

Answer 9

1. Source control, since you won't be writing all the code.
2. Good comments and pretty code, since others need to understand what the hell your code does.
3. Team player mentality, since programmers have huge egos.

Answer 10

Try to be proactive, always.

That's it.