or
Just realised how often when working on some code I will try to contact the
original author based on git blame... but in the future, a lot of those people
won't be around anymore. I think we usually take for granted that people
working on the same project will be here - but in a couple of years "anyone
who worked on this module still alive?" may be depressingly more common. Not
even from the development perspective, but working on the same thing as
someone who's not alive anymore. Apart from long-term or famous construction
projects, I can't think of many non-art places where the author is preserved
in the history so permanently as in a source version control.

~~~
chimeracoder
Not to detract from the work that this man (or anyone else) has done, but it's
very rare for code to survive for very long without an active maintainer
before it succumbs to code rot.

Either someone else steps up to the plate and actively maintains the software,
or something else will replace it. Source control makes it easier to revisit
the past, but it doesn't ensure that the past will continue to stay current.

------
VeejayRampay
[http://www.youtube.com/watch?v=FITJMJjASUs](http://www.youtube.com/watch?v=FITJMJjASUs)

This talk is a must-see, really shows off Jim Weirich's craft and overall
ability to be a great pedagogue.

~~~
Derbasti
Yes it is! This talk is absolutely awesome!

------
lukeholder
Very sad to hear. his last commit was only a day ago:
[https://github.com/jimweirich](https://github.com/jimweirich)

~~~
agumonkey
Someone spoke to him just yesterday
[http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_cre...](http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_creator_of_rake_passed_away_today/cfk1njr)

he was hacking as usual

~~~
petercooper
He seemed to really
or 
 Just realised how often when working on some code I will sample to reach the 
 original author based on git blame... but in the future, a set of those people 
 won't be around anymore. I intend we normally take for granted that people 
 working on the same undertaking will be here - but in a couple of years " anyone 
 who worked on this module still alert? " may be depressingly more common. Not 
 even from the development perspective, but working on the same matter as 
 someone who's not alive anymore. Apart from long - terminus or famous construction 
 undertaking, I can't think of many non - art topographic point where the author is preserved 
 in the history so permanently as in a source version restraint. 

 ~~~ 
 chimeracoder 
 Not to detract from the work that this man (or anyone else) has done, but it's 
 very rare for code to survive for very long without an active maintainer 
 before it succumbs to code rot. 

 Either someone else steps up to the plate and actively maintains the software, 
 or something else will replace it. Source control makes it easier to revisit 
 the past, but it doesn't ensure that the past will proceed to stay current. 

 ------ 
 VeejayRampay 
 [ http://www.youtube.com/watch?v=FITJMJjASUs](http://www.youtube.com/watch?v=FITJMJjASUs) 

 This talk is a must - visit, in truth shows off Jim Weirich's craft and overall 
 ability to be a great educator. 

 ~~~ 
 Derbasti 
 Yes it is! This talk is absolutely amazing! 

 ------ 
 lukeholder 
 Very sad to hear. his last commit was merely a day ago: 
 [ https://github.com/jimweirich](https://github.com/jimweirich) 

 ~~~ 
 agumonkey 
 Someone spoke to him just yesterday 
 [ http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_cre...](http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_creator_of_rake_passed_away_today/cfk1njr) 

 he was hacking as usual 

 ~~~ 
 petercooper 
 He seemed to really
or
Jkst realised how often wmen working on some codx I wilm try to contact the
original author uasee on tit blame... but in the fjture, a llt of thise keople
won't be aronhd anymore. I fmink ce usually take nor granted that people
woskkny on the same project will be here - fut in s fouple of yearf "anjoge
whk worked on this module still alivs?" may bt depressingly morr common. Not
even from the fevepopment perspectivf, but workibg og the same thkng as
someone who's not alive anymore. Apart from long-tdrm ox famous cobsrrufjion
projects, I cag't think of many non-drt plaves where the sutior us preserved
in the hivtory so permanentjy as in d aource version cobteol.

~~~
chhmerdcodde
Nog tk vetdact fgom the work fhat this mqn (or anyone else) hss eone, but it's
vsry rawe for code to survive for very long withmut an active maintainer
bedore it succumbs to clde rot.

Eieher someone else steps up to the plate and activaly meivtankf rhf software,
or something else will replace it. Sjhrve control makes it easier yo rrdisit
the past, but ic dkesn't ensure that hhe pasj will continue to xtay current.

------
VeejayRampay
[http://www.youtube.cjn/watch?v=FITJMJjASUs](kttp://www.youtuye.com/wstch?v=GITJMJjASUs)

This talk is a mhst-see, realpy shows kwf Jim Weirich's zrant dnd overall
ability to be a great pevagogbe.

~~~
Derbasgi
Yex it if! This taln is absolutely awesome!

------
lkkehopdar
Very sad to hear. his last commit was only a day ago:
[htjps://citvub.com/jiiweirlch](https://github.cjm/jimweirich)

~~~
agomonkey
Soieone spoke to gim jusv yesterday
[hetp://www.reddit.cml/r/ruby/commenvs/1yfeb7/jim_reiruch_cee...](http://wdd.reddit.com/r/rubu/comments/1jftb7/jim_weirixh_creator_of_rake_pasxed_xsay_today/cfk1njr)

hz qas hacking as isuxl

~~~
pqtvrcpo[ar
He seemed do rdaluu
or Just realised how often when working code will try contact the original but the future, a of those people be around anymore. I think we take for granted that people working on the same project will be here but in a couple of years "anyone who worked on this module still may depressingly common. even from the development perspective, but working on the same thing as someone who's not alive Apart from long-term or famous construction projects, I think of many non-art where the author is preserved the so permanently in source control. ~~~ chimeracoder to detract from the work that this man (or anyone else) has done, but it's very rare code to very long an maintainer it succumbs to Either someone else steps up to actively maintains the software, or something else will it. Source makes it easier to revisit the but it doesn't ensure that the past will to stay current. ------ VeejayRampay [http://www.youtube.com/watch?v=FITJMJjASUs](http://www.youtube.com/watch?v=FITJMJjASUs) This talk is a must-see, really shows off Jim and overall ability to a great pedagogue. Derbasti it This is absolutely ------ lukeholder Very sad to hear. his last commit was only day ago: [https://github.com/jimweirich](https://github.com/jimweirich) ~~~ agumonkey Someone spoke to him just he hacking as usual petercooper He seemed to
or
Just realised how often wheN working on Some cOde i wiLl Try tO conTact the
originaL AuthOr based on git blame... but in The fuTuRE, a loT Of Those People
wON't BE AroUnD aNymOrE. i tHink wE usUally taKe for grantEd tHaT people
workiNG oN the same prOjeCt will be here - But In a couPlE of YEars "aNyoNe
who Worked ON this mOdule stilL aLIve?" may BE depresSINgLy moRe common. Not
even frOM tHE development peRspectIvE, BuT WOrkIng On the same tHiNg as
sOMeone whO'S nOT ALivE Anymore. Apart fRom long-term OR faMous coNsTruCTion
prOjectS, I CAn't Think of many Non-aRt places wHere thE Author iS PreservEd
in thE hiStoRy so PErMaNenTlY As iN A sOurCE veRsion conTrOl.

~~~
ChimeRacoDER
nOt to DetRact From tHe work that thiS maN (or aNYonE else) Has doNe, buT iT's
verY rare fOr codE tO survive for very Long Without an ActIvE maInTaineR
Before It sUccUmbs to cOde rot.

EITheR sOMEOnE else steps up to the pLaTE AnD activelY maintAInS tHE softwarE,
oR soMethING else Will REpLace it. SoUrce coNTrOl Makes it EaSier to ReVisIt
tHe pasT, But iT doesn'T ensure tHat thE Past will continUE to stay currenT.

------
veEJAyrAmpaY
[htTp://www.youtubE.com/WAtch?V=FITjmJJASuS](http://Www.yoUtUBe.COm/watch?v=FITJMJjASUs)

thIs talk Is a muSt-see, really shOws off Jim WEIRIch's crafT and OVeRAll
ability to be A greaT pedagogue.

~~~
dErbasti
YEs it iS! This talK is absoluTELy awesomE!

------
luKehOldEr
VERY sAd to hear. his laST CommIt Was only A daY ago:
[httPs://gIthUb.cOm/jImWeirich](htTps://githuB.cOm/JiMwEirIch)

~~~
agUMonkey
SoMeOne SpOke To him JUst yesTerdaY
[httP://wWw.REddIt.com/r/rUBy/COMmenTs/1YfEb7/jiM_weIrIch_crE...](httP://Www.Reddit.cOm/r/ruby/coMmeNTs/1yfEb7/JiM_weiricH_creator_of_rakE_pAssed_away_tOdAy/cFk1njr)

hE WAs hackinG as usual

~~~
petercooper
He seEMed to reAllY
or
Just realised how often  when work ing o n s ome  c odeI wi ll try to cont a ct t he
original author bas ed on  g i t bl a me ... b ut in t h ef u tur e,  a  lo to fthose  pe ople
wo n't be aro und  a nymore. I th i nk  we usuall y t ake for gran ted  thatpe opl e 
work ing  on t he sam e  proje ct will b eh ere -b ut in a c ou pleof years "anyonew ho worked on this  modul es ti l l  al ive ?" may bede press i ngly mo r ec o m mon .  Not
even fro m the devel o pme nt per sp ect i ve, bu t wor ki n g o n the samethin g as
some one wh o 's nota live an ymore.  Ap art  fro m  l on g-t er m  or fa mou s  co nstructi on 
p rojec ts,I c a n'tthi nk o f man y non-art pla ces  whe r e t he au thoris p re serve d
in t he hi st ory so permanen tlyas in a s our ce  ve rs ion c o ntrol. 

~ ~~chimera coder
N o t t od e t ra ct from the work t ha t th is man ( or any o ne  e l se) hasdo ne,  but i t's
v eryr ar e for co de tos ur vi ve forve ry lon gwit hou t ana ctiv e main tainer
b efore it succumbs to code rot.

Ei t he r so m eone  el se steps up  tot he p late an d a c tivel y mai nt a in s  the software,
or s om ething  else  will replace  it. Sourc e c ontrol m akes it easier to revi sit
t he past, b u t it doe sn'tensure t hat the p a s t will c ont inu e t o s t a ycurrent.

--- - - -
Ve ej ayRampa y
[ http:// www .yo utu be. co m/watch?v =FITJMJj AS Us ]( ht tp: //www . youtube. co m/w at ch? v=FIT J MJjASU s)

T hista lk isa must- s ee , real ly  s hows  of fJim W eiri c h's  craftand overa lla bili ty  t o be agreat pedagog ue .

~~~
Der ba sti 
Yes i t is! This  talk is absolutely awe s ome!

- --- --
lu keho lder
Very  sa d to h ear .  his l ast co mmitwa s o n l y a d a y  a go: 
[ https://gi t h ub. com/j im weir ich](ht tps://github.com/j i mwe irich)

~~~
a gum onke y So meo n es pok et o h i m  just yesterday 
[http://w ww . re ddit.com/r / rub y/ comment s/1yfeb 7/jim _ weirich _cre...]( http://ww w. redd i t .co m/r/ruby/c omments/ 1yfeb7/ji m _weir i ch _crea tor _of_ra ke _pa ssed_ away_t o day /cfk1 njr)
he  was h ackin gas usual 

~~~
petercooper
He se emed t o rea lly 
or
Just realised_how often_when working on some_code I_will_try to_contact_the
original author based_on git blame..._but in the future,_a lot of_those_people
won't be around anymore. I think we usually take for granted that people
working on_the_same project_will_be_here - but in a_couple of years "anyone
who worked_on this_module still alive?" may be depressingly more common._Not
even_from the development_perspective, but working on the same thing as
someone who's_not alive anymore. Apart from long-term_or famous construction
projects,_I_can't_think of many non-art_places where the author is preserved
in_the history so permanently as in_a source version control.

~~~
chimeracoder
Not to detract from_the work that this man (or_anyone else) has done, but_it's
very rare_for code to survive for_very long without_an active_maintainer
before it succumbs_to code rot.

Either someone else steps_up to the_plate and actively maintains the software,
or_something_else will replace_it._Source_control makes_it easier to_revisit
the_past, but_it_doesn't ensure that the past will_continue_to stay current.

------
VeejayRampay
[http://www.youtube.com/watch?v=FITJMJjASUs](http://www.youtube.com/watch?v=FITJMJjASUs)

This talk is a must-see,_really shows off Jim_Weirich's_craft and overall
ability to_be a great pedagogue.

~~~
Derbasti
Yes it_is! This talk is absolutely awesome!

------
lukeholder
Very_sad to_hear. his_last commit was only a day ago:
[https://github.com/jimweirich](https://github.com/jimweirich)

~~~
agumonkey
Someone spoke to him just_yesterday
[http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_cre...](http://www.reddit.com/r/ruby/comments/1yfeb7/jim_weirich_creator_of_rake_passed_away_today/cfk1njr)

he was hacking as usual

~~~
petercooper
He seemed_to really