News for hackers. Stuff that matters.
Re:Why a career in computer programming sucks [2007] by Turing_Machine on Saturday February 25, 2012 @11:03AM (#3633182)
He's also wrong-headed about the fields he cites as "unchanging". Yes, lawyers still cite Blackstone, but the law is changing all the time nonetheless. Computer programming has similar foundational material (sorting, searching, you name it -- almost nothing in Knuth is "out of date"). Business has changed radically in recent years. Even accountants have to retrain themselves constantly; the Internal Revenue Code changes every single year (sometimes dramatically), rules of accounting change, new requirements like Sarbanes-Oxley come into play.

Sometimes accountants don't get much respect, but I have to admire anyone who can gobble the Internal Revenue Code every year and come up with procedures that (usually) don't get any of their clients fined or jailed and (ideally) don't cause them to go bankrupt.

Re:Why a career in computer programming sucks [2007] by sanxiyn on Saturday February 25, 2012 @11:21AM (#3633225)
> almost nothing in Knuth is "out of date"

Actually, quite a lot of TAOCP are out of date. TAOCP's discussion of floating point arithmetic, while correct, predates IEEE 754 and not that useful now. TAOCP's analysis of algorithms, while correct, ignores locality of reference as it predates importance of CPU caches and branch predictors. TAOCP spends inordinate amount of pages on external sorting with tapes; while external sorting is still important, most of Knuth's specifics are not. I can go on and on...

Re:Why a career in computer programming sucks [2007] by Turing_Machine on Saturday February 25, 2012 @06:41PM (#3634223)
You're making the same mistake as the author of the post -- thinking that the technology of today is the way it's always going to be, and that the ideas of the past are gone forever.

In fact, these things are cyclical. Mainframe->microprocessors->network computing servers. Floating-point emulation using integers on the CPU->External floating-point coprocessors->on-chip math coprocessors->external GPUs. Manipulating gigantic data sets on resources like Amazon S3 has many commonalities with classic tape storage (arguably more than it does with rotating disk storage -- retrieving a big object from S3 brings it in as a stream of data. Reading the whole glob and processing it as a stream is reasonably efficient but random access sucks. Sounds like a tape, no?). IEEE 754 isn't necessarily the last word in floating point arithmetic. I can go on and on... :-)