If you’re about to hit something…turn. Get back on track.
Tuesday, November 30th, 2004Last night I got down to business actually coding again. After one of my last posts on not working fast enough, I entered the evening mentally willing myself to try to work as fast as possible. Soon after starting, I hit a wall. This is the first time I’ve used Idea 4.5 with it’s new project/web module setup and I was trying to use the integrated Tomcat support. Only it would never pick up my jars which I’d included in my classpath inside of Idea. As a brute force method just to get me on track, I was going to just copy all the jars into the tomcat lib, but I knew this would give me errors later down the road. As a quick fix to get me back on track to coding, I switched to trusty, fast Resin. I’ll figure out the Tomcat issue later when I have some idle time to mess around with it. (Anyone have this problem?)
And soon after I was back on track, actually getting my code running fine on Resin. I can’t debug on Resin via Idea (I’m sure there must be a way - leave me comments if you know how), but that’s for later as well.
The key is to realize when you get off on a tangent and aren’t being productive. In the past there have been times when I’ve hit one of these bumps, then spent an hour trying to find an elaborate way around it and gone further down a path which isn’t useful. I’ve gotten better at recognizing this as I’m going and I don’t get down the wrong path for as long anymore. Question yourself - is this going to lead to my end goal? Do I really need to spend 2 hours writing an ant task to perform this job when I can do it manually a couple times over the life of the project and it will take me 15 seconds each time to do it?
Recognize when you’ve hit a wall, take a turn and get back on track.






