----- Original Message ----- 
  From: Delbert Legg 
  To: Git for human beings 
  Sent: Thursday, September 10, 2015 12:46 PM
  Subject: [git-users] New to Git (and programming in general)

  Hey all...recently embarking on a career change (from management in the 
energy sector to computer science, focusing on software development) and about 
six weeks away from my degree. I plan on diving back into the course material 
since I feel like much of it was skimmed over or I just didn't get what I 
needed out of the class at the time, but I want to concurrently start refining 
some coding skills and contributing meaningfully while building a portfolio. 
From what I've read (I don't have ready access to a group of like minded 
individuals), open source is a great way for a newbie to dive in, but I'm not 
sure how to become active or really what I can contribute at this point, as I'm 
certainly not an "experienced" programmer as of yet.

  Short question to the backstory: How can I get plugged in to the open source 
world and start contributing, even in a minimal way? I'm willing to do all the 
b*tch work necessary even for exposure to good coding practices. I'd appreciate 
any help, and would greatly appreciate working closely and exponentially with a 
singular group (for rapport and progression purposes).

Some personal thoughts...
First, select a few projects you might be interested in - if you aren't that 
interested in some allegedly new and exiting area, then it will become "work" 
(like going back to energy management ;-).
Having found a few potential projects, get on their mailing lists, and have a 
look at their archives. 
Some are said to be quite 'harsh' with a thick skin and lots of self confidence 
/ arrogance required. 
Others are 'firm but fair', which can also take time to adjust to.
Also checkout the size of the active team, the occasional team, and the lurkers 
- if it's too small it will eventually fold - it needs to feel like it's on a 
growth track, and isn't just a me too project just like many other similar 

Perhaps introduce yourself if it feels like the norm, or otherwise wait for a 
topic that you can comment upon, or comment on an area that tripped you up 
while using the code / product / project.

Helping with the documentation is always helpful, though you may need to select 
if the extra info goes in a blog, a wiki, a tutorial or a man page (along with 
arguing the right tone for the contribution).

In summary, make sure it's a project you'd enjoy, and that will feed you back.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to