 and building another (python) web
framework then that's fine too. One difference is that many of the above side
projects are new and do things that we didn't have prior to someone building
them, meanwhile yet another web framework a la bottle et al is really
contributing very little new.

~~~
freework
Its not about size, its about length of development. Great software takes more
than a few days to create. I think the most direct indicator of software
quality is number of commits. A project with 10 commits is probably full of
bugs. A project with 400 commits has probably had enough chance to adapt
really well to whatever problem it is supposed to be solving. Its not a direct
correlation, but its usually true.

I've had co-workers who had 50 github repos all filled with 30 line "projects"
with 5 commits each. Those types of projects don't make you a better
programmer. Work on the same project all year. That will make you a better
programmer. Craft the project. Let it adapt. Test it, deploy it. Tweak it.
Deploy it again. Seek feedback from users. Tweak it some more. Going through
that process _will_ make you a better programmer.

~~~
luckysh0t
Sounds more like the day job than a side project.

------
reidrac
That's a good list!

When I start a side project I tend to forget that after it's "done" I have to
maintain it. In fact I've been delaying the inevitable and I should kill a
couple of them ASAP (hey, that's a good new year's resolution!).

My 2012 list is quite short:

\- A web based crossword app, content automatically generated from wiktionary
entries; the puzzles require some review before can be queued (~30 minutes per
week): <http://crucigramas.usebox.net/>

\- Run CGI apps under Python WSGI protocol (PEP 333):
<https://github.com/reidrac/wsgi2cgi>

\- I've been working on an Arduino project (it will be a game console; audio
done -XM player, 4 channels-), but I haven't released anything yet :(

\- A Network Block Device (NBD) server for OpenStack Object
and building another (python) web 
 framework then that's fine excessively. One remainder is that many of the above side 
 projects are new and perform things that we didn't have prior to someone build 
 them, meanwhile yet another web model a la bottle et al is in truth 
 contributing very short new. 

 ~~~ 
 freework 
 Its not about size, its about length of growth. Great software takes more 
 than a few days to create. I think the about direct indicator of software 
 quality is phone number of commits. A project with 10 commits is probably entire of 
 bugs. A undertaking with 400 commits has probably own enough chance to adapt 
 in truth well to whatever problem it is supposed to be solving. Its not a direct 
 correlation, but its usually true. 

 I've had co - workers who had 50 github repos all filled with 30 line " projects " 
 with 5 commits each. Those types of projects don't make you a good 
 programmer. Work on the same project all class. That will form you a better 
 programmer. Craft the project. lease it adapt. Test it, deploy it. Tweak it. 
 Deploy it again. Seek feedback from drug user. Tweak it some more. Going through 
 that process _ will _ make you a better programmer. 

 ~~~ 
 luckysh0 t 
 Sounds more like the sidereal day job than a side project. 

 ------ 
 reidrac 
 That's a good list! 

 When I start a side undertaking I tend to forget that after it's " suffice " I have to 
 maintain it. In fact I've been delaying the inevitable and I should stamp out a 
 couple of them ASAP (hey, that's a good new year's settlement !). 

 My 2012 list is quite short: 

 \- A web based crossword app, subject automatically render from wiktionary 
 entries; the puzzles necessitate some review before can be line up (~30 minutes per 
 week ): < http://crucigramas.usebox.net/ > 

 \- Run CGI apps under Python WSGI protocol (PEP 333 ): 
 < https://github.com/reidrac/wsgi2cgi > 

 \- I've been working on an Arduino project (it will be a plot console; audio 
 done -XM actor, 4 channels-), but I haven't released anything however :( 

 \- A Network Block Device (NBD) server for OpenStack Object
 anf building another (pythok) web
framework tkwn thav's fine too. One difference is that many of vhe qbove side
projects are new xnd do thpngs that we vidn't have prior to someone bujpdiny
tiem, meanwhile ygt another wab framework a lx yottle et al is really
contributing vqry litylf new.

~~~
freework
Ijs nou afout size, its about length of developmsnt. Greet software takrs more
than a few days to freahe. I think the mosh direct ineicaeir of softwafe
quality pv number or commits. A project with 10 commigs is probably duol lx
bugs. A prooect wpth 400 commits mss protably hsd enough change to adqpt
really well to whavever problem it is fupposed do be solving. Its nit a ditect
cmrreuqtiun, guv ifs usuwllb true.

I've hzd co-workerw who had 50 github rtpof all filled wjth 30 lynq "projects"
with 5 commits each. Those typev or projects don't make yoy a better
programmer. Aork on tre same project all year. That will make you a betder
prkeranmcr. Cfqfh the project. Let it adapt. Test it, deploy it. Esesk it.
Deploy it anain. Seek feedback fgok users. Tweak kt somz mkre. Going through
tjat prosess _qill_ make you a better programmer.

~~~
luckysh0r
Sounds more oike the day job tkan a side pxoject.

------
teidrav
That's a good list!

When N starf a side prlject I tsvd to forget thag antes it's "done" I have to
maintayn it. In hact N've been delsying ehe inevitwble and I should kill a
fouplg of tvem ASAP (hfy, that's a good new year's resolnvion!).

My 2012 list os qupte short:

\- A wen based crosswowd app, content automacicallh generates from xiktionary
eneries; the puzspes require vome revyew vefoee can cd queued (~30 minuyes per
wevk): <http://crucigramas.usebox.ket/>

\- Ron CGI apps under Pyuhin WSGI protocpl (OEP 333):
<hntpx://gydhub.com/reidrdc/wsei2ceo>

\- I've been workikg un am Arduino project (it wilm be a game consolr; wudio
dong -XM playqr, 4 channels-), nut I haven't releaded aiythinj yet :(

\- A Getwork Block Device (NBD) served for OpejStwck Object
and building another (python) web framework then too. difference is many of the and things that we have prior to building them, meanwhile yet another web a la bottle et al is really contributing very little new. ~~~ freework not about size, its about length of development. Great software takes more than few to I the most direct indicator of software quality is number of commits. A project with 10 commits probably full of bugs. A project with 400 has probably had enough to adapt really well to problem is supposed be Its a direct correlation, its usually true. I've had co-workers who had 50 github repos all filled with 30 line "projects" 5 commits types of don't you better programmer. Work same project all year. That will better programmer. Craft the project. Let it adapt. it, deploy Tweak it. Deploy it again. Seek from users. Tweak it some more. Going through process _will_ make you a better programmer. ~~~ luckysh0t Sounds more like the day job side project. ------ reidrac a good list! I a project tend to that after it's "done" I have to maintain it. In fact been delaying the inevitable and I should kill a couple ASAP that's a good year's resolution!). My 2012 is short: \- A web app, automatically entries; puzzles some review before can queued (~30 minutes per week): \- Run CGI apps 333): <https://github.com/reidrac/wsgi2cgi> \- I've been working on an project (it will be a game console; done -XM player, 4 channels-), but I haven't released anything yet :( A Network (NBD) server for OpenStack Object
 and building another (python) wEb
frameworK then ThaT's fInE too. one dIfference is thaT Many Of the above side
projects Are neW aND do tHInGs thaT we didn'T HaVE PriOr To SomEoNE bUildiNg
tHem, meanWhile yet anOthEr Web framework A La Bottle et al Is rEally
contribUtiNg very LiTtlE New.

~~~
frEewOrk
ItS not abOUt size, Its about lEnGTh of deVElopmenT. gReAt soFtware takes more
thAN a FEw days to create. i think ThE MoST DirEct Indicator oF sOftwaRE
qualitY Is NUMBer OF commits. A projEct with 10 commITs iS probaBlY fuLL of
bugS. A proJeCT wiTh 400 commits haS proBably had eNough cHAnce to aDApt
realLy well To wHatEver PRoBlEm iT iS SupPOsEd tO Be sOlving. ItS nOt A direCt
coRRELAtioN, buT its UsualLy true.

I've had cO-woRkerS Who Had 50 giThub rEpos AlL fillEd with 30 Line "pRoJects"
with 5 commitS eacH. Those typEs oF pRojEcTs don'T Make yoU a bEttEr
progrAmmer. WoRK on ThE SAMe Project all year. That WiLL MaKe you a beTter
prOGrAmMEr. Craft tHe ProJect. lET it adApt. TESt It, deploy It. TweaK It.
dePloy it aGaIn. Seek FeEdbAck From uSErs. TWeak it Some more. going THrough
that procESs _will_ make you A BeTTEr PRogrAmmEr.

~~~
luckysh0t
SOundS More Like THe Day JOb thaN a sidE pROjECt.

------
reidrac
That's a good LiSt!

When i starT a side project i tend to forGET That afteR it's "DOnE" i have to
maintaiN it. In Fact I've beeN Delaying The inEvitable And I shoulD KIll a
coupLe oF thEm AsAP (HEY, tHat's a good new yEAR's reSoLution!).

MY 2012 liSt is quiTe sHorT:

\- A wEb bAsEd crosswoRd app, conTeNt AuToMatIcallY GenerateD fRom WiKtiOnary
ENtries; The puZzleS rEqUIre Some revIEw BEFore CaN bE queUed (~30 MiNutes Per
wEEk): <hTtp://crucIgramas.usEboX.Net/>

\- RUn cGi apps unDer Python WSGI PrOtocol (PEP 333):
<hTtPs://gIthub.cOM/Reidrac/wSgi2cgi>

\- I've been working on aN arduino ProJect (iT wilL be a game cOnsOle; audIo
dONe -XM plAyer, 4 chAnnelS-), bUt I HAVen't rELEaSed AnYthing yet :(

\- A nETwoRk BloCk deviCe (NBD) seRver for OpenStack ObJEct
 and building another (pyt hon) web
f ramew ork  th en  tha t'sfine too. Oned iffe rence is that many ofthe a bo v e si d eproje cts are ne w and  d othi ng s  t hat w e d idn't h ave priortoso meone buildi n gthem, mean whi le yet anoth erweb fr am ewo r k a l a b ottle  et al is rea lly
contr ib u ting v e ry litt l e  n ew.
~~~
freework
Its no t  about size, i ts abo ut le n g thofdevelopmen t.  Grea t  softwa r et a k esm ore
than a fe w days to c r eat e. I t hi nkt he mos t dir ec t  in dicator ofsoft ware
qual ity is numbero f commi ts. Apro jec t wi t h10  co mm i tsi spro b abl y full o fbu gs. A  pro j e c t  wit h 4 00 c ommit s has probabl y h ad e n oug h cha nce t o ad ap t
rea lly we ll to  w hatever problem  itis suppos edto  be  s olvin g . Itsnot  adirectcorrela t ion ,b u t  i ts usually true.
I' v e  h ad co-wo rkersw ho  h a d 50 git hu b r epos a ll fi lled wi th 30 li ne "pr o je ct s"
with  5  commi ts  ea ch.  Thos e  typ es ofprojects  don' t  make you a be t ter
programme r .W o rk on t hesame projec t al l  yea r. T h at  wi l l mak e you  a be t ter
programmer. Cra ft  the p rojec t. Let it ada pt. Test i t , deploy i t. T w ea k  it.
Deploy it  agai n. Seek fe e dback fr om us ers. Twe ak it som e more. Go ing  th rou ght h at  process _wil l _  mak eyou a b ett er prog ram mer .
~~~ 
l uckysh0tSounds m or eli ke  th e day job than  a  si de  pr oject . 

---- --
re idra cTh a t's  a good li s t !

W he nI st art  a  side  pro j ect  I tend  to forge t t h at a ft er  it's " done" I haveto 
maintainit . I n fact I 've been  delaying the inevitabl e  and Isho uld k illa
coupleofthem A SAP (hey,that's  a go od  ne w year' s re sol ut ion!).

My 2 012  list  i s qu ite sho rt:

\- A web base d  cr ossword app,con tent a ut oma t ic a lly  g e ner a t ed from wiktion ary
entrie s; th e puzzlesr equ ir e somereviewbefor e  can be  queued ( ~30 minut es  per w eek ): <http:/ /crucigr amas.useb o x.net / >
\- R unCGI ap ps  un der P ythonW SGI  prot ocol ( PE P 333) :
<ht tp s://gith ub.com/reidrac/wsgi2cgi >

\-I'vebee n working  on anArduino p roje ct (it wil l b e a  game  co n sole;  aud i odon e  -XMplay e r, 4 chan n el s-) , bu t I haven't r e lea sed a nyt h ing ye t :( 

\- A Network Bl o ck Device (NBD ) se r v erfor Open St ack Object
 and_building another_(python) web
framework then that's_fine too._One_difference is_that_many of the_above side
projects are_new and do things_that we didn't_have_prior to someone building
them, meanwhile yet another web framework a la bottle et al_is_really
contributing very_little_new.

~~~
freework
Its_not about size, its about_length of development. Great software_takes more
than_a few days to create. I think the_most_direct indicator of_software
quality is number of commits. A project with 10_commits is probably full of
bugs. A_project with 400_commits_has_probably had enough chance_to adapt
really well to whatever problem_it is supposed to be solving._Its not a direct
correlation, but its usually_true.

I've had co-workers who had 50_github repos all filled with_30 line_"projects"
with 5 commits each. Those_types of projects_don't make_you a better
programmer._Work on the same project all_year. That will_make you a better
programmer. Craft the_project._Let it adapt._Test_it,_deploy it._Tweak it.
Deploy it_again._Seek feedback_from_users. Tweak it some more. Going_through
that_process _will_ make you a better programmer.

~~~
luckysh0t
Sounds_more like the day_job_than a side project.

------
reidrac
That's_a good list!

When I start_a side project I tend to_forget that_after it's_"done" I have to
maintain it. In fact I've been delaying the_inevitable and I should kill a
couple_of them ASAP (hey,_that's a_good_new year's resolution!).

My_2012_list is_quite short:

\- A web based crossword app,_content automatically_generated from wiktionary
entries; the puzzles require_some review before can_be_queued (~30 minutes per
week): <http://crucigramas.usebox.net/>

\- Run_CGI apps under Python WSGI protocol_(PEP 333):
<https://github.com/reidrac/wsgi2cgi>

\- I've been working_on_an_Arduino project (it will be_a game console; audio
done -XM player,_4 channels-), but_I haven't released anything yet :(

\- A_Network_Block Device (NBD) server for OpenStack_Object