Also, some components I used, most notably Kafenio, sometimes behave in strange ways. Normally, when such problems arise, I either need to work with the developer to fix the problems I'm having, or build the components myself. However, to date the issues during the Bleezer development cycle are not bad enough to force me to take either step.
I've made a few dollars from Bleezer, but I didn't write it to get rich. I wrote it to give back to the free and open source software community that helped me create it. But it has been far better as a replacement for my resume, giving me street cred as a developer (when I started the project, I had been out of that area for a few years) and it got me a fair bit of work.
But now it's time to take it to the next stage of development. The next step is to open source the project. Doing so will result in a loss of control, but it will also allow Bleezer to be better supported. Giving up your baby is hard, but in this case it will free up my time for new projects, and better serve the many people who depend on the tool.
Larry Borsato has been a software developer, marketer, consultant, public speaker, and entrepreneur, among other things. For more of his unpredictable, yet often entertaining thoughts you can read his blog at larryborsato.com.
More news, commentary, and predictions from The Industry Standard:
- Larry Borsato: Thou shalt not ship software before its time
- Larry Borsato: Vetting startup ideas at BarCamp
- Analysis: 10 reasons that start-ups 100% absolutely should outsource (almost) everything
- Analysis: The real problem with Google's Blogger service: Neglect
Post new comment