I was thinking today of what most software engineers / developers/ architects / (insert favorite title here) do when they are not on a time-intensive project.
Quite incidentally, I found out today that some of our brethren do nothing. Well, they stare at the screen or read more and more and more news but don't do anything intellectually challenging. So I thought it may be worthwhile to write about what I do, and see how it compares to what a few other folks end up doing.
Here's my version of it:
About 2 weeks before the project actually ends, I start getting a little antsy. At the point, I am making minor bug fixes, fixing loopholes in documentation, preparing installshield setup files, etc.
My first option begins by heading over to my boss's office and looking at the big TO-DO list on the board. I pick the next task on the list that would be within my range and the product lines I work on. Then ensues a long discussion with my boss regarding why the project needs to be done, what needs to be done, if there are any specific requirements and how I am capable of doing it.
With the first stage done, I generally head on over for some caffeine - strong caffeine. Now starts the process of requirements generation, proof-of-concept development, architectural selections, design documents, talking with stakeholders, research, poof! (can't believe I actually said all that in one breath and still missed about 20 things)
That was option number 1 - or the easy option. It's really not that difficult - someone tells you what to do.
Here is option number 2 - or the more intellectually challenging option. This comes into play when either there is no project for a short time or I can't convince my boss that I can lead the next project. This is when I go get some coffee - the strongest coffee I can make and eat some chocolate to get the sugar pumping as well. I sit at my desk and ask simple questions. This can range from stupid things like "What if I someone were to come up with a license to use the Internet" to "How can I make my next project more effective?" or something like "What is something cool that I can add to my current applications?" These are simple questions with not so simple answers which take me back to the feeling that I had in grad school when I started n my thesis - all I thought was "COOL". Its a time when I have to pick a topic, read a lot about a different subject, understand it and then apply my knowledge towards solving a problem. There is a thrill, an excitement that these projects bring me - perhaps a sense of self- satisfaction.
As one of my projects reaches its closing stages I wonder what kind of a journey I am going to embark on this time around. I will keep you posted on my new project.
In the meantime, it would be interesting to know what other software professionals do. Keep the comments coming.