Slashdot Mirror
Jeremy Allison's Advice to Young Programmers
Hyram Graff writes "Jeremy Allison has written a wonderful piece with advice to young programmers. As someone who's been out of college for just over a year, I find it to be a very insightful piece. Please allow me to say, thanks Mr. Allison!"
I agree completely since it is a fact that has been established over the years, [...]
I have to argue there are still a lot of computing applications where the network is of only tangential interest. Word processing, desktop publishing, video editing, [single player] games, etc. There's no shortage of work where the network is really just a a process for getting an initial set of data onto the machine to be manipulated (if it even does that - eg: photo editing with photos coming straight off the camera).
Mr Allison's advice (and commentary) seems to be very much centred around writing high-performance server applications. Which is hardly surprising, given his background, but may not be equally applicable to all forms of coding (eg: writing GUI apps for GNOME or KDE today is probably quite different to writing X apps twenty+ years ago, and an intimate knowledge of the underlying hardware/OS is only really necessary if your code is performance-sensitive).
[...] i still wonder if iTunes(one of the best examples i could remember) would have been so widely used today if not for the music sharing feature!
Of course it would. The iPod is the main reason iTunes is popular (( don't think I've _ever_ used iTunes music sharing features - or the iTunes Store, for that matter).