258 karma · joined September 22, 2010
-Foresterh
When all you factor into the cost is human life and money, you miss the bigger picture of how we're affecting what doesn't have a voice.
This is more for people who aren't (yet).
Sometimes if they made it far enough, I'd sit with them at a computer and ask them to do something fairly simple, but something they most likely hadn't done before, so they need to figure out how to... then watch how the interact with the IDE, how they figure out how to do something (they can use the internet, any tools, ask me, etc). And most of the time, they just fall flat on their face.
I should emphasize, there are definitely a lot of developers here, but the amount of _good_ developers is less than the amount of jobs looking for them. I have three times in the past two years been the primary resource (interviewer/researcher) for finding new developers, and each time I find 90-100% of the devs I interviewed were just trash. I lucked out one of those three times and found an outstanding one, but the other two times I had to settle on a less than ideal one.
I'd also say that networking plays a huge part... join groups with similar programming interests (such as .Net user group or Alt.Net), post on Facebook that you're seeking a gig, etc... that will you help you get through the pile of devs that are simply developing for the money, not for the love of development.
You give a team a pool table, game console, or some other form of "getting away" from the work, and you'll get back tenfold in terms of work done from them.
The second biggest offense seems to be working hours... too many managers think that programmers should be working the same as everyone else - 9-5, onsite 5 days a week, etc... we just aren't wired that way... when I can put in a few hours at midnight, I'm much more productive for my boss...