Justifying your dream job
Is giving your employees their dream job going to help or hurt the bottom line? One manager responds.
Dev Connection
Who said computers have to be all work and no play? Software developer and author Ed Burnette shares his unique view of industry trends, technologies, and personalities.
Ed Burnette
Ed Burnette is a software industry veteran with more than 25 years of experience as a programmer, author, and speaker. He has written numerous technical articles and books, most recently "Hello, Android: Introducing Google's Mobile Development Platform" from the Pragmatic Programmers.
Latest Posts
The sweet spot between free and cheap
Like most people I have a toolbox of free software that I use every day. But giving away things is not a sustainable business model by itself. As commoditization drives prices down, what's a commercial software vendor to do? One answer: find the profitable sweet spot between free and cheap.
Reinhold: Rhino stays in Java SE 6
In a notice this week to Java licensees, Sun wrote "This message is to inform you of Sun's decision to remove the Mozilla Rhino (JavaScript for Java) product from the Java Platform, Standard Edition (Java SE) 6." But the rest of the message talked about source code availability, but this sentence made many think that the Rhino binaries were being dropped as well ...
My dream job
If you could design your own dream job, what would it be like? Here are some thoughts about mine. At my dream job, I could immerse myself in the latest technologies and ideas, and spend as much time as I wanted learning (and teaching). If I wanted to use Java in my dream job, I could do it without explaining for the umpteenth time why Java isn't slow....
Simon Phipps gets it right (finally)
At EclipseCon 2004, Sun's Simon Phipps gave a keynote address before a tense audience on the virtues of open source. The presentation was positive and well received, but didn't address the questions that were on everybody's mind. Simon gave another keynote recently at the Open Source Business Conference Europe. What a difference a couple years and a new boss can make...
Ten coolest Eclipse 3.2 features
Eclipse 3.2 was released Friday along with 9 other projects that make up the Callisto Release train. The new release of Eclipse has hundreds of new features that have been developed over the past year since 3.1 came out. For this article I pick out 10 of my favorite features in 3.2 to whet your appetite and give you a reason to upgrade...
Countdown to Callisto: An Eclipse singularity
On Friday June 30, 2006, the floodgates will open and one of the largest coordinated open source releases ever attempted will begin. I'm talking of course about the Eclipse Callisto simultaneous release, or "Callisto release train" as it's sometimes called. The locomotive driving Callisto is Eclipse 3.2, the latest version of the popular Eclipse tools framework and rich client platform. Eclipse 3.2 is significant on its own, containing a year's worth of enhancements to the Eclipse Platform, Java Development Tools, and Plug-in Development Environment. Of particular importance for Callisto are...
Motorola joins Eclipse, proposes mobile Linux project
Motorola announced this week it was investing in Eclipse by joining as a Strategic Developer Member. As part of this commitment, Motorola will hold a seat on the Board of Directors, participate in various councils of the Eclipse Foundation, and dedicate a number of developers to working on Eclipse projects. They also proposed a new project called Tools for Mobile Linux, which will provide frameworks and tools for developing C++ applications that run on mobile devices.
How to pick an open source license (part 2)
In my last installment, I introduced a simple decision tree that could help you decide which (if any) of the many open source licenses you should use for your project. In this part I'll go through some of the most common licenses and see where they fall from this tree. I'll also try to address some of the issues that people pointed out in the comments to my last posting.
HOWTO: Pick an open source license (part 1)
If you write some code keep in mind that it's yours and you get to decide if, how, or under what circumstances, other people can use it. Let's say you've made the decision to release your code as "open source". What does that mean, what is an open source license, and how do you pick the right one? This question comes up all the time so I thought I'd write up a simple decision tree to try to explain the choices.