Why you shouldn't make a mountain out of a molehill, or make a millisecond out of a nanosecond
I plan on writing all sorts of blog articles on this website, some of the articles will deal with projects I've made or currently working on, others will be about my school, others will be me writing lame comments about other peoples blogs. Sadly, this is going to be one of these blog posts, and its inspired from the blog The Invent with Python Blog on making good code, titled Nobody Cares About a Few Million Nanoseconds. I thought it was a great read, and decided to use this as great article to talk about.
Much like other programmers, I constantly am trying to better my code making the code more efficient and optimized. Because of this, I find myself spending countless hours debugging my code in hopes to finally get the program to work. Without completely rewriting the article I just posted, I'd just like to point out how excellent of an article it is for a beginner programmer in regards to certain aspects like naming your variables, and worrying about memory allocation. The author goes into explaining why this is "97% unneeded" in today's programming due to memory being such a cheap commodity. I am definitely planning on my next programming project, which I plan to write in Eclipse's Java environment.