On Thu, Jun 14, 2007 at 09:44:27AM +0300, Yossi Kreinin wrote: > Peter da Silva wrote: > >Actually... > > > >I think the analogy "not hiring a brewer who doesn't drink" doesn't even > >go far enough. > > > >Even if you don't like programming, or don't currently program in your > >spare time, I can't imagine someone who's a programmer who has *never* > >written any software that they can't bring in as an example. Even if > >it's something horrid from college that they think sucks, at least they > >could bring it in and explain why it sucks and what they'd do > >differently now. The point isn't to see the code, it's to have the code > >there for them to explain, discuss, critique, apologize for, and so on. > > > > > > > > If you count stuff they did back when they learnt how to program, then, > yes, almost everyone should have done something like that. Although I don't > know where's the CD with all that stuff of mine. I was only referring to > claims about writing code for yourself or the humanity outside of your job.
Except for some vi mappings, I don't have any 'coding' left from my days at the university. (All code was done on accounts that would be wiped out at the end of the semester, and the only way to take anything home would have been paper prints. Which I no longer have). A few times, I was asked to bring in my thesis work - and then I dutifully brought copies of the published articles that resulted from my thesis. Not that those have been very useful, most people would have been lost even before finishing the abstract. Abigail
pgptmwVOIDVPt.pgp
Description: PGP signature
