Two years ago, I learned that you can be a brilliant programmer and write awesome code but if your code doesn’t help solve some problem or doesn’t ease someone’s pain, then you’re not really doing your part. This is exactly the lesson that this book tries to drive home. It goes through the different aspects of creating a product from the programming and support to the licensing and legal side. The book also includes several interviews with people who have already done that.
My workplace has a subscription to SpringerLink. So I’ve been having a blast looking at the different books over there. I found lots of books that are on my Amazon wish list and so i was like a child at a candy store. The problem is that the books are provided via separate pdf files for chapters. I am not sure why they do that, I think to make it tougher to pirate the files?
Michael Ivey recently wrote about his git work flow over at My Git Workflow and it turned out to be a pretty useful article and was just the encouragement that i needed to blog about my own experience. Although I’ve used git before, I much rather use bzr whenever possible. I’m not into religious wars about tools, so use whatever you like. I work as an independent programmer(freelance programmer if you prefer) and so I am often working on several projects at the same time, mostly on my own, but sometimes with 1 or 2 more people involved.
Wikipedia has been a vital source of information for me and hardly a day goes by where i don’t use it to read up on something. Amazingly, topics covered on it range from the down right silly to the most advanced technical topic. All reviewed and scrutinized by the mass public. I just donated today as part of the “put your money where your mouth is” campaign. Although my donation is small and something i should have done a long time ago, I think that every bit helps and its always better late than never.
Last week, i sat through a demo of a certain document management system provided by a vendor. The system in itself is pretty good. Although if it was up to me, I would never choose a proprietary system for a vital project. Since you essentially would be putting yourself and your data at the mercy of the provider. What was interesting though was their licensing terms. Aside from the system itself, you have to buy “modules”.
A couple of months ago, we started working on a project, code named firemote, to help in the detection and prevention of forest fires in Lebanon. I didn’t say anything about it because i was waiting for it to be announced, and the announcement was finally done a few days ago. The press coverage(in english) is at The Daily Star - Politics - AUB team invents new tool to help battle forest fires
It just occurred to me today. Running your own business, you try to optimize the hell out of everything to make as much use of your time as possible. Employees on the other hand, wish to be as unproductive as possible. But i have to say, I still don’t understand how people think. Its one thing to have a lazy day, but to turn laziness into a habit is just plain wrong.
My NDA Policy ~ I have decided to starting signing them! : Texas Startup Blog discusses Non-Disclosure Agreements and how the author has decided to react to it. I think it is brilliant. Also of interest are the other linked articles such as To NDA or Not to NDA? That is the question. My stance on NDAs is that i only sign specific ones that actually relate to confidential information. And i only do that to make newer clients feel more at ease.
I finally got around to releasing the BombMaker Gnome applet that i blogged about. I’ll share with you a little secret, I’ve actually been using it for the past 6 months or so. I even learned to package debian packages just so that i can release it.(manually installing gnome applets is a bit too much) There were a couple of snags along the way, mainly in the packaging part and specifically in using autotools for that.
Strange title, isn’t? I don’t actually make bombs :) although during the last war, a lot of people probably thought i did. In my KDE days, i used to make a lot of use of an applet called KTeaTime(http://docs.kde.org/stable/en/kdetoys/kteatime/introduction.html#whats-kteatime). Its a nice little applet that tells you when your tea is ready after you select what type of tea you want. So if you select extra black tea for example, it will remind you that your tea is done after 10 mins for example.