Home > Uncategorized > Programming Things I Wish I Knew Earlier

Programming Things I Wish I Knew Earlier

September 6th, 2010 09:25 admin Leave a comment Go to comments

theodp writes “Raw intellect ain’t always all it’s cracked up to be, advises Ted Dziuba in his introduction to Programming Things I Wish I Knew Earlier, so don’t be too stubborn to learn the things that can save you from the headaches of over-engineering. Here’s some sample how-to-avoid-over-complicating-things advice: ‘If Linux can do it, you shouldn’t. Don’t use Hadoop MapReduce until you have a solid reason why xargs won’t solve your problem. Don’t implement your own lockservice when Linux’s advisory file locking works just fine. Don’t do image processing work with PIL unless you have proven that command-line ImageMagick won’t do the job. Modern Linux distributions are capable of a lot, and most hard problems are already solved for you. You just need to know where to look.’ Any cautionary tips you’d like to share from your own experience?”

Source: Programming Things I Wish I Knew Earlier

Related Articles:

  1. Programming Things I Wish I Knew Earlier
  2. Anti-Piracy Lawyers ‘Knew Letters Hit Innocents’
  3. YouTube Was Evil, and Google Knew It
  4. BP Knew of Deepwater Horizon Problems 11 Months Ago
  5. Dell Knew About Computer Failures
blog comments powered by Disqus
YOYOYOOYOYOYO