Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Programming Things I Wish I Knew Earlier

theodp (442580) writes | more than 4 years ago

Programming 1

theodp (442580) 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. 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?"

Sorry! There are no comments related to the filter you selected.

Things I wish I knew earlier (1)

BlueFigToast (1430459) | more than 4 years ago | (#33494134)

This is the equivalent of doing the hokey-pokey. [] Two rules to guaranteed success with computers: 1. Always have a path back, to the way it was, before you messed it up. 2. Always follow rule #1. Wayno
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?