Jeff Atwood of Coding Horror fame is kind of hard to write about, because I agree so much with him it's almost silly.
Take todays blog, for instance; http://www.codinghorror.com/blog/archives/000878.html
Named "The best code is no code at all", he succinctly argues that the biggest enemy to writing good code is ourselves, as programmers.
I've felt for a couple for years or more that I'm getting more and more sick and tired of being slave to a host of things that has nothing to do with the problem whatsoever.
We're getting bogged down by ant (or gods help you - maven) scripts, we have to battle code versioning systems of various lethal potency, and when the day is done we still have to create seven new classes and interfaces - several quite obscure and weird - just to be able to use a single kind of functionality of a fine API. We're not even using it in an edge-case scenario, we're trying to use it for the most common purpose for which it was built!
And then we've never even started to write the actual logic of what we're trying to achieve yet.
These reasons, in a nutshell, along with LOC bloat is my main reasons for using javascript almost exclusively, after almost 10 years as a Java/J2EE and occasional .N0t programmer.
You can also be very certain that the next time I code server-side again, I will _SO_ use a scripting language, probably PHP.
Take todays blog, for instance; http://www.codinghorror.com/blog/archives/000878.html
Named "The best code is no code at all", he succinctly argues that the biggest enemy to writing good code is ourselves, as programmers.
I've felt for a couple for years or more that I'm getting more and more sick and tired of being slave to a host of things that has nothing to do with the problem whatsoever.
We're getting bogged down by ant (or gods help you - maven) scripts, we have to battle code versioning systems of various lethal potency, and when the day is done we still have to create seven new classes and interfaces - several quite obscure and weird - just to be able to use a single kind of functionality of a fine API. We're not even using it in an edge-case scenario, we're trying to use it for the most common purpose for which it was built!
And then we've never even started to write the actual logic of what we're trying to achieve yet.
These reasons, in a nutshell, along with LOC bloat is my main reasons for using javascript almost exclusively, after almost 10 years as a Java/J2EE and occasional .N0t programmer.
You can also be very certain that the next time I code server-side again, I will _SO_ use a scripting language, probably PHP.
Comments