Why Wandercoding dot com
Why are we here? No, not in the larger, existential sense. Why are we here at Wandercoding.com? Well, there are a number of answers, but the main one is: software people don’t think about their careers very much. Some do, of course. Some people want to become a Chief Technical Officer, go into management, or become a project leader. Most software people’s consideration of their career is more along the lines of, “Gee, I hope I don’t get laid off when the company starts outsourcing work to India or China” or “I hope my raise doesn’t suck this year because the economy sucks.” Most software people will spend time researching a new language, toolkit, or algorithm without thinking twice about where the time goes. Of course, it has a direct correlation to your job. However, what if you took twenty minutes a week to think about what you could do to improve your career for the long term. Doesn’t sound so bad, does it?
Right off the bat, I’m sure that a bunch of you will comment that I am way off base here. You’ll say that you, of course, care deeply about your career. After all, you found this website, didn’t you? The answer is that you found it because you care about your career. The rest of your colleagues didn’t, because they don’t care. Help them out, send them the link.
Now that we’ve settled that, what’s coming? In this space we’ll be talking both about general career-oriented topics and specific stuff for software-related people. Here are some of the things that will be covered in the time ahead:
- Coding design tips
- Career paths
- Dealing with colleagues
- Dealing with marketing, sales, management
- Managers dealing with coders
- Your suggestions for topics
- Whatever comes up or strikes me at the time
It is my sincere hope that this site is useful, informative, thought provoking, or at least entertaining. I’ll be posting my own comics now and then, too, just to add to the variety. Welcome aboard.
Bill Myers has been writing software professionally since 1986. He has Bachelor’s and Master’s Degrees in Mechanical Engineering and has been writing engineering-oriented software ever since. He has worked on products for knowledge-based engineering, architectural modeling, diagramming, drawing markup, solid modeling, and finite-element modeling. His current job is writing software to support engineering automation for the Composit Group (see www.compositgroup.com). In his spare time, he teaches Judo at Cornell University, and works on various projects both related and unrelated to software.