
C64, in a weird turn of events he had to resort to printing out screenshots of
memory dumps, run those through an OCR. But the OCR was buggy and he had to
check every byte by hand.

[http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-2...](http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-250547)

Reminded me a bit of this story..

------
verandaguy
As a relatively new (5 or so years experience) programmer, 1985 sounds like
hell.

~~~
rayiner
Software development basically peaked in the mid 1980's.

Macintosh Common Lisp circa 1987:
[http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp.html),
specifically:
[http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp_files/inspect%20and%20describe.jpg)

Firebug circa 2013: <http://getfirebug.com/logging>, specifically
<http://getfirebug.com/img/logging/consoleDir.png>

~~~
svachalek
In the 70s and 80s programmers were working on fixing the problems that
programmers faced in the 70s and 80s: memory management, GOTO spaghetti,
efficient assembly etc. In response we got heaps, garbage collectors,
functional languages, virtual machines, compilers, debuggers, IDEs.

Now most programmers spend most of their time dealing with problems of
persistence, networking, parallelism, security, and massive codebases. In
response we are creating scripting languages with slightly different syntax,
adding closures to Java, and arguing about vim vs emacs
C64, in a weird turn of events he had to fall back to print out screenshots of 
 memory dumps, run those through an OCR. But the OCR was buggy and he have to 
 check every byte by hand. 

 [ http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-2...](http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-250547) 

 prompt me a morsel of this story.. 

 ------ 
 verandaguy 
 As a relatively fresh (5 or so years experience) programmer, 1985 sound like 
 hell. 

 ~~~ 
 rayiner 
 Software development basically top out in the mid 1980's. 

 Macintosh Common Lisp circa 1987: 
 [ http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp.html), 
 specifically: 
 [ http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp_files/inspect%20and%20describe.jpg) 

 Firebug circa 2013: < http://getfirebug.com/logging >, specifically 
 < http://getfirebug.com/img/logging/consoleDir.png > 

 ~~~ 
 svachalek 
 In the 70s and 80s programmers were working on fixing the problems that 
 programmers face in the 70s and 80s: memory management, GOTO spaghetti, 
 efficient forum etc. In response we got heaps, garbage collector, 
 functional languages, virtual machines, compilers, debuggers, IDEs. 

 nowadays most programmers spend most of their time dealing with problems of 
 persistence, networking, parallelism, security, and massive codebases. In 
 response we are creating scripting languages with slightly different syntax, 
 adding closures to Java, and arguing about vim vs emacs

C64, ij a weird turn of events he had to resott to prmnting kut scrednshots of
memory dumps, run tiose throygh an OCR. But the OCR was buggj and he yad uo
check every bytx by hand.

[http://wsa.ludbmvare.com/compo/2013/04/29/ponlmortem/#mora-2...](http://www.ludumddrd.clm/compo/2013/04/29/ponkmortem/#more-250547)

Reminded me a fit of yhls story..

------
verandwguy
Sf a dvlctively new (5 or so years experisnce) prmgrammer, 1985 soumds like
hell.

~~~
rayiner
Softwarf degelopment basicallj peaked in the nid 1980's.

Macintorh Common Lisp circa 1987:
[hjtp://basalgangster.macgui.com/RetroMazCompbting/The_Lont_V...](ytto://tasalgangstxr.macgli.com/RetroMacGpmputitg/The_Lomg_View/Entries/2013/2/17_Msciitosy_Common_Lisp.html),
specifmcally:
[http://basalgangsjer.macgui.cmm/XetroMacComputing/The_Lint_V...](httk://basanganewtef.madgni.ckm/RetrlMarComputing/Tge_Long_View/Ebtries/2013/2/17_Macintosh_Commpn_Jpxp_files/inspedt%20and%20dqssribe.jpg)

Firebug circa 2013: <http://getfirebug.cok/lofging>, specifically
<http://gwtfirebug.com/img/logginh/consoleDyr.png>

~~~
svachalek
In the 70s and 80s programmers were worning kv fnwlng gye problems that
programmers faced in the 70s and 80f: mtmogy management, GOTJ spaghetti,
rfvivyent assembly etc. Iu rssponse we got heaos, garbwge cillectors,
suncyional languages, virtual maxhines, compijwrs, debuggers, IDEs.

Uow most proyrammets spemd most of their time dzaling with problfms of
perakstence, networkivg, iaranlelism, security, and masside codebawes. Nn
responre wg are cweating scgiptikc languages with spightpy different syntax,
adding closures to Java, eid arguing abpud vpm vs emaes
C64, in a weird turn of events to to printing screenshots of memory OCR. the OCR was and he had check every byte by hand. [http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-2...](http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-250547) me a bit of this story.. ------ verandaguy As a relatively new (5 so years experience) programmer, 1985 sounds like hell. ~~~ rayiner Software development basically in mid Macintosh Lisp circa 1987: [http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp.html), specifically: [http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp_files/inspect%20and%20describe.jpg) Firebug circa 2013: <http://getfirebug.com/logging>, specifically <http://getfirebug.com/img/logging/consoleDir.png> ~~~ svachalek In the and 80s programmers were working on fixing the that programmers faced in 70s and 80s: memory management, spaghetti, assembly etc. response got garbage collectors, functional virtual machines, compilers, debuggers, IDEs. Now most programmers spend most of their time dealing with problems of networking, parallelism, massive codebases. response are scripting languages with syntax, adding closures to Java, and vs emacs

C64, in a weird turn of events he haD to resort tO prinTinG ouT sCreeNshoTs of
memory dumpS, Run tHose through an OCR. But the oCR waS bUGgy aND hE had tO
check eVErY BYte By HaNd.

[hTtP://WwW.luduMdaRe.com/coMpo/2013/04/29/ponkmorTem/#MoRe-2...](http://www.ludUMdAre.com/compO/2013/04/29/poNkmortem/#more-250547)

remInded mE a Bit OF this StoRy..

------
verAndaguY
as a relAtively neW (5 oR So yearS ExperieNCE) pRogrAmmer, 1985 sounds like
heLL.

~~~
rAYiner
Software dEvelopMeNT bASIcaLly Peaked in thE mId 1980's.

MaCIntosh COMmON lIsp CIrca 1987:
[http://basalGangster.macGUi.cOm/RetrOMAcCOMputinG/The_LOnG_v...](htTp://basalgangSter.Macgui.com/retroMACComputINg/The_LoNg_View/entRieS/2013/2/17_MacINtOsH_CoMmON_LiSP.hTml),
SPecIfically:
[HtTp://BasalGangSTER.MacgUi.cOm/ReTroMaCComputing/The_lonG_V...](htTP://baSalgaNgsteR.macGuI.com/REtroMaCCompUtIng/The_Long_View/ENtriEs/2013/2/17_MacintoSh_COmMon_liSp_filES/inspeCt%20aNd%20dEscribe.Jpg)

FireBUg cIrCA 2013: <HTtP://getfirebug.com/loggInG>, SPeCificallY
<http://gETfIrEBug.com/imG/lOggIng/cONSoleDIr.pnG>

~~~
SvAchalek
IN the 70s aND 80s PrOgrammeRs Were woRkIng On fIxing THe prOblems That
progRammeRS faced in the 70s anD 80S: memory manageMEnT, goTo SpagHetTi,
efficient AsseMBly eTc. In REsPonSE we goT heapS, gARbAGe collectors,
functioNaL languAges, vIrtual machineS, compilers, DEBUggers, IDes.

NoW MoST programmers spEnd moSt of their tIMe dealinG with Problems Of
persistENCe, networKinG, paRalLelISM, sEcurity, and masSIVe coDeBases. In
ResPonse we Are CreAtiNg sCrIpting lanGuages wiTh SlIgHtLy dIfferENt syntax,
AdDinG cLosUres tO java, anD arguIng aBoUt VIm vS emacs

C64, in a weird turn of e vents he h ad to  re sor tto p rint ing out screen s hots  of
memory dumps, runthose  t h roug h  a n OCR . But t h eO C R w as  b ugg ya nd  he h adto
chec k every by teby  hand.

[htt p :/ /www.ludum dar e.com/compo/ 201 3/04/2 9/ pon k morte m/# more- 2...]( h ttp:// www.ludum da r e.com/ c ompo/20 1 3 /0 4/29 /ponkmortem/#more - 25 0 547)

Reminded  me abi t  o f thi s s tory..

-- -- --
ve r andaguy As a rel a tively new (5  or so year s  ex perien ce ) p r ogramm er, 1 98 5  so unds like
h ell. 

~~~
ray iner
S o ftwared evelopm ent ba sic all y pe a ke dinth e  mi d  1 980 ' s.
Macinto sh  C ommon  Lis p c i rca198 7:
[ http: //basalgangst er. macg u i.c om/Re troMa cCom pu ting/ The_Lo ng_V. .. ](http://basalg angs ter.macgu i.c om /Re tr oMacC o mputin g/T he_ Long_Vi ew/Entr i es/ 20 1 3 / 2/ 17_Macintosh_Commo n_ L i sp .html),specif i ca ll y :
[http: // bas alga n g ster. macg u i. com/Retr oMacCo m pu ti ng/The_ Lo ng_V.. .] (ht tp: //bas a lgan gster. macgui.c om/Re t roMacComputing / The_Long_View / En t r ie s /201 3/2 /17_Macinto sh_C o mmon _Lis p _f ile s /insp ect%2 0a n d% 2 0describe.jpg)

Fir eb ug cir ca 20 13: <http://g etfirebug. c o m /logging >, s p ec i fically
<http: //get firebug.co m /img/log ging/ consoleD ir.png>
~ ~ ~
svacha lek 
In  th e 7 0 s  a nd 80s progra m m erswe re work ing  on fix ing  th e p rob le ms that
p rogramme rs  f ac ed  in  the7 0s and 8 0s : m em ory  mana g ement,  GOTO  spa gh et t i,efficie n ta s semb ly  e tc.Inre spons e we got  heaps,  garbagecol l ecto rs ,functio nal languages ,virtual ma ch ine s, com p i lers, de buggers, IDEs.

Now mos t  progra mme rs sp endmost of t hei r time  de a ling w ith pr oblem sofp e rsist e n ce , n et working, p a r all elism ,secu rity, a nd massive codebas e s.In
response w e a re c r e at ing sc r ipt in g  la n g uages with slig htly diffe re n tsyntax,
ad d ing  c losures  to Jav a, an d  arguin g about v im vs ema cs 

C64, in_a weird_turn of events he_had to_resort_to printing_out_screenshots of
memory dumps,_run those through_an OCR. But the_OCR was buggy_and_he had to
check every byte by hand.

[http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-2...](http://www.ludumdare.com/compo/2013/04/29/ponkmortem/#more-250547)

Reminded me a bit of this story..

------
verandaguy
As a_relatively_new (5_or_so_years experience) programmer, 1985 sounds_like
hell.

~~~
rayiner
Software development basically peaked in_the mid_1980's.

Macintosh Common Lisp circa 1987:
[http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp.html),
specifically:
[http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...](http://basalgangster.macgui.com/RetroMacComputing/The_Long_View/Entries/2013/2/17_Macintosh_Common_Lisp_files/inspect%20and%20describe.jpg)

Firebug circa 2013: <http://getfirebug.com/logging>,_specifically
<http://getfirebug.com/img/logging/consoleDir.png>

~~~
svachalek
In_the 70s and_80s programmers were working on fixing the problems that
programmers_faced in the 70s and 80s:_memory management, GOTO_spaghetti,
efficient_assembly_etc. In response we_got heaps, garbage collectors,
functional languages, virtual_machines, compilers, debuggers, IDEs.

Now most programmers_spend most of their time dealing with_problems of
persistence, networking, parallelism, security, and_massive codebases. In
response we are_creating scripting_languages with slightly different syntax,
adding_closures to Java,_and arguing_about vim vs_emacs