Skip to main content

Coding and learning and sharing and earning :-)

Sometime in 2005 I created a website to share practical information on software programming and design. The idea was to share practical programming tips, best practices, howtos, gotchas, etc. The material would come from what I learn writing actual code, and the medium to share it would be a blog, audio, and screencasts.

I started this venture with the intention of doing something I enjoyed, and generating revenue. The website grew steadily, though very gradually. After about a year and a half I had about 27,000 page hits a month, and a few comments per post. I know it is very modest, but I believe it was at a point where it would have grown much more rapidly form there on. But due to various reasons, I was not able to dedicate enough time to working on the website, and eventually I shut it down.

Even though I shut down the website sometime last year, the desire to be able to work on open source software (that has a social impact), share information, and generate revenue from it, persisted.

I started this blog a few months back as the first step towards this goal. I also changed my work pattern and commitments to support this goal. I do actual work (work that pays) for part of the month, and I spend the remaining time keeping my knowledge current (through books, blogs, and podcasts), experimenting with code doing coding katas (right now I am learning Groovy, so my katas are pretty much at the Hello World level in Groovy), writing (this blog), and well... thinking and researching about how I can make all this work.

To be honest, I am very positive that type of work is feasible, but it will need lots of patience and perseverence. No problems, I have both :-).

However the fact is that even though I am seeing an increase in page hits and recent posts have started getting comments, things are not moving ahead at quite the speed I was hoping (in terms of the number of readers and interaction on individual posts). But then again I do not post as regularly as I should. Sometimes I post twice a week, while sometimes two weeks go by without any post at all. This is not good. I have to be more consistent. I am thinking that a frequency of 2 - 3 posts a week is maneagable for me. I think it is also a frequency people would find useful without getting overwhelmed (with too much quantity). If you have found my blog useful, I need your help. Please tell me what frequency of posts would be most useful to you.

My posts have just started attracting comments, so I assume that people do read them and find them useful. Please remember that if you leave a comment, it helps me realize that there are people reading this blog, and to a large extent it motivates me to write regularly :-)

I have a Google Group for programming, and design related discussions, but their isn't much activity on it. Again I am to blame. I should post more frequently to the group and share useful information from time to time. I promise to share more stuff on the group as well.

Sometime back I started @coding_insights, a Twitter feed to share small and useful bits of information related to programming. Some people have found it useful and follow the feed. I am planning to publish as least 1 - 2 Tweets a day.

So along with doing actuak programming I try and share what I learn through this blog and through my Twitter feed. I think it is time to add one more thing... a long time passion of mine... podcasts. I plan to start publishing a podcast sometime next month, and it's going to be all about coding. I will publish a small program which either explains some API, so a coding or design best practice, and then create a podcast to explain the code. If you think such a podcast will be useful, do give me your feedback about what you would like to listen and how much you would like to listen. By how much I mean the length of the podcast. What should be the optimal length of the podcast so that it can deliver value without distracting people from their work.

I will look forward to your feedback. Also if you have any other thoughts, do share them as well.


Popular posts from this blog

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by  Helloquence  on  Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ar