The New York Times list of Best Small Business Reads for 2011 praises Jason Fried’s article How to Get Good at Making Money in Inc. as the best article this year about making money. Here’s the key line for software developers:
“People are happy to pay for things that work well. Never be afraid to put a price on something. If you pour your heart into something and make it great, sell it. For real money. Even if there are free options, even if the market is flooded with free. People will pay for things they love.”
Joel on Software and CodingHorror are teaming up to produce something new – a sort of an audio Experts-Exchange.com called StackOverflow.com. Here are some notes from Joel on the project, and here’s what Jeff Atwood (CodingHorror) has to say. I enjoyed the first podcast and I’m looking forward to more in the future.
Looks like the SitePen guys have the right idea – provide professional class support and bill for it. Good luck, fellas!
The Journal of Defense Software Engineering published this article raising more alarms (as if that were needed) about the state of computer science education in the US. Money quote:
It is all about programming! Over the last few years we have noticed worrisome trends in CS education. The following represents a summary of those trends:
- Mathematics requirements in CS programs are shrinking.
- The development of programming skills in several languages is giving way to cookbook approaches using large libraries and special-purpose packages.
- The resulting set of skills is insufficient for today’s software industry (in particular for safety and security purposes) and, unfortunately, matches well what the outsourcing industry can offer. We are training easily replaceable professionals.
When I’m interviewing a candidate for a programming job, one of the first things I do is ask them to explain the C language statement
What does it do? How is the result used? etc.
If you can’t work the phrase, “it’s an address” into your explanation, you won’t be able to handle embedded systems work. You might be just fine for a job in financial IT, but there’s just no way you’ll be able to debug something like a stack corruption, memory leak or wild pointer. And the root cause of this weakness is too much Java, and not enough C.