|
----- Original Message ----- From: <boothm@earth.Goddard.edu> Sent: Wednesday, May 17, 2000 5:59 PM Subject: RE: /400 skills test > No one else has even mentioned looking at actual code as a means of > evaluating a programmer. Why not? > > It interests me that no one has yet mentioned a portfolio of code as a > means of evaluating a programmer. I have a selection of code that I feel > represents my abilities and that I feel should be of more interest than a > written test. > > _______________________ > Booth Martin Booth, How does the interviewer know that you wrote the code in the portfolio? Just 'cause you can explain how the code works, and maybe cite a different approach that could have been used, does not mean that you actually designed the solution. IMHO the most important factor for an interviewer to establish is that the candidate understands (or will be able to understand) the business world in which he/she will work Learning the code is the easy bit. Successfully applying that to business practice is what shows experience. I do not believe a code portfolio would be able to show that. Regards, OleBlighty. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.