Skip to main content

Benifits of blogging

A few days back I was discussing with a friend, how small companies can use blogging to their advantage. To survive in business each company has to maintain a certain brand image for itself. The brand image helps in attracted good customers as well as in attracting good talent to work for the company. Large organizations do the brand building in many ways, some of them being through advertisements, brochures, conferences, and their salesforce. Small companies however do not have the deep pockets that their larger counterparts enjoy, but many small companies do excellent work, and it's a pity that they are not as well known as they should be. The Internet and the concept of grassroots publishing gives smaller organizations, the tools to network and make themselves better known. Blogs and Podcasts are two of the more frequently used tools that can be used. In this weblog I talk about Blogs. I will to talk about Podcasts in another posting.

Blogs as opposed to books capture small ideas. A book is a treatise, it deals with a concept, fact, or fiction in significant detail. An article is a smaller unit of writing, and a blog is the smallest. In a blog one writes about something distinct in a terse and useful manner. Offcourse not all blogs are terse and many are not useful, but that is because there are so many bloggers, all of whom want to share their personal rants with the world.

A blog may proceed towards a book, but it need not. It can be a collection of thoughts, stories, etc that we want to share with our readers. Let me explain why it is important. A couple of days back I was reading Times Ascent. There were recruiting advertisements from well known companies (most of those adds were large and in color), and there were adds from smaller companies. I am sure some of the smaller companies must be really good, but anyone reading Ascent has no way of knowing it. Applicants looking for a job will first apply to the larger organizations, and only those candidates who are not sure of getting selected with the big guys will look at the unknown companies. I think there are two factors that come into play here. The size and the glitz of the advertisement, and the fact that a company is known. An advertisement that does not have any of these factors will most likely be ignored by the good candidates. Size and glitz come at a huge price, and probably are not affordable for a small organization. But being known in the software community is not very difficult. As an example, Joel Spolsky runs a small software company which is reasonably well known and he is also able to attract good talent. He gets summer trainees from Stanford. He has achieved this because he has created a certain persona for his company through his writings (essentially blogs) on the Internet. I am sure it takes time, but the returns that he gets are definitely worth it.

For a practical implementation outlook, all that needs to be done is spend 15 minutes a day writing about experiences with methodologies and technology. It can be a collaborative process where everyone contributes and something good emerges at the end of every week. At times it can also be a personal effort and not a collaborative one. Time spent on this activity will not be wasted, because the process of writing also helps the writer articulate her thoughts, and not to mention write better comments in code :-) If an organization can come up with short peices of useful writing, publish them on their website, and also get them published in magazines then they will create a certain rapport with the software community. The name of the organization will stick in peoples mind. Now when the organization advertises for job openings, they will get a better response because more potential candidates will have heard of the company, and will know that they do good work. In time the advertising can also happen through the blogs. Very often talented developers might apply on their own, because they want to work for a company that does great work. Off course it will be a while before this will happen, but as they say: A long journey begins with the first step.

Comments

Popular posts from this blog

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb-1.8.0.7.jar org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path