« back

Food For Thought - Developing a System of Checks

17 Dec 2012

I think I need to develop some checks to balance my sanity.

Today was a lot of spinning my wheels. I was unsure why. After trying what I thought would work and it not working, I spent a good deal of the morning researching how to do what I thought I needed to do. Some of the reading left me feeling even more unsure of things because I thought what I was doing should work. Stepping back, I thought that I needed to re-think some things. I would try solutions that I was pretty sure would work and they wouldn't. Again, I wasn't sure why. Okay, I've drawn this out enough. Do you want to know why my solutions were not working? I never restarted my server to recognize my changes. Yep. That was it. My solution was right from the beginning. I simply overlooked a stop and start of the server. This isn't the first time something small has tripped me up. I'm sure it will not be the last. It is obvious that I need to put some kind of process in place to help prevent this. This will just be food for thought and if you have suggestions, I would love to hear them.

What I am thinking is this...

When working on projects, each one will have a slightly different work flow depending on what you I am working on. I think as I get going with a project, I may make a "process map". What is a "process map"? Well, as far as I know, I am making it up and it is whatever I say it is. Right now I say that it is a workflow documentation with any key information that may be new to you but that you will need to use or anything that bit you while you were working. For example, I know that using something like this 'java -jar cooljar.jar -p 8081' is new to me but I know that I need to use it while working on my project. It is likely that I will forget it for the first several times I need to use it. In that case, if I were to close a terminal tab, I would be kind of screwed or at least inconvenienced enough to the point where it would benefit me to store that line in a process map. I think even the simple act of creating this document would force me to think about and internalize the possible things that could be tripping me up. I would just add things that I think I may need or that have bitten me. Let's make a simple example for my web server project.

1    -start your server -> lein run
2    -start your spec server -> java -jar cooljar.jar -p 8081
3    -check that your anchor tags are properly filled in
4    -check your path

Seems simple enough, right? It's kind of like a stitch in time saves nine or more appropriately, a process map saves you a half of a day. :) I'll keep you posted.

comments powered by Disqus