software engineer

About ten years ago there was a rumour. If you want to get things done, and if you want to get them done fast, go for PHP.

Yes, it's been like a badly done perl ripoff with even worse object orientation and inconsistent apis, but somehow the people creating in software in PHP were able to deliver.

And they were able to deliver fast, open for changes in the last 24 hours and they fixed bugs in production fast.

From a software engineering professionals point of view this sounded risky, unprofessional and dangerous. This could only lead to crappy code.

Close race this week, but coming out on top for "most insightful" was a comment from The Buzz Saw in response to Disney's Anthony Accardo whining that the tech industry hasn't propped up legacy businesses that are slow to adapt to a changing market.

According to Chris Aitchison, you're not a "software engineer" if you write code an develop applications - you're a "software gardener":

CIO: "To fill a requirement for flexible content and management and e-commerce, Melbourne-based software engineer Stephen McDonald has released two open source projects built with the Django framework."

Linux.com: "Some Linux Foundation members don't do anything just a little. That's certainly the case with Paré, a software engineer based in Montreal who traveled nearly 4,000 miles by car last summer to attend the first ever LinuxCon."

Have you heard about Google’s 20 percent time?

Google encourages their employees to spend 20% of their work time working on their own projects.

Looking for a Ruby or Rails job in this economy? They're still there! They seem to be getting posted daily on jobs.rubynow.com but we've got 5 of our own that have come in via the Ruby Inside jobs board.