Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.
Click here to check if anything new just came in.
February 03 2010
“— The Productive ProgrammerIf you start all your automation projects out in a powerful scripting language, it allows you to make the call as to when it becomes invaluable to add the kind of infrastructure of real code. It also means that you don’t have to learn an entire zoo of special-purpose tools. Scripting languages today give you virtually all the affordances of command-line tools.Useful things tend to never go away. They keep growing and growing until they become an important part of your process. All little utilities reach a critical mass where they become important and thus deserving of real attention. If you build them right in the beginning, you won’t have to rewrite them when that day comes. Try as much as you can to keep behavior in code (not in tools or markup languages like XML). We know all sorts of ways to deal with code: diff to compare versions, refactoring, robust testing libraries. Why would we give all the accumulated knowledge of what we know about code just for the siren song of some elaborate tool?”
Reposted by
fragmad
fragmad
