lunatechian (lunatech-ian)

one relating to, belonging to, or resembling lunatech

acquisition of knowledge

I have been struggling to understand a Concept about something at the work for the last 3 days. Initially, when I started, it was all black.. till a few moments ago it was still black hole (even though I had been filling a few pages drawing boxes and arrows while trying to understand it).. and then suddenly the blackness dissolved as I was hit by enlightenment. The Concept made perfect sense now. It is the moments like this that make the lighthouses of the life - beacons of hope, that I am not dull :-).

Thought for the day - to reach a particular point of thought, where you have a clear picture of the thing, you have to struggle through hours of working through cobwebs misunderstanding and pitfalls.

Update: Enlightenment followed by nice dinner and icecream is much better :-)

Defined tags for this entry:

a weekend in Goa

This weekend I had gone to Goa. One of the good points of living in Bangalore is that it is only 12 hours bus journey to Goa. Here are my notes from the visit

  • Take the sleeper seat in the bus - The Paulo Travels runs luxury buses from Bangalore to Goa. They have two choices of the seats - sleeper and sitting. We had the misfortune to get the sitting seat and could not sleep a wink for the whole journey. The guy sitting behind us was snoring quite a lot and added to our discomfort.
  • Hire a scooter/bike when you get down at Panjim - We did not hire a two wheeler when we got down at Panjim. We reasoned that we would get a bike from the hotel where we were staying. This would make it easier for us to return the bike when it was time for us to leave. However, it was a bad decision. Most buses pass through Panjim when returning to Bangalore. It would have been far easier to return the bike at Panjim and then board the bus to Bangalore.
  • Stay away from the autorickshaws if you can - They overcharge a lot. A lot. If you know where you want to go, it is far more easier to get a bus (but remember that the bus service stops at 7:00 PM). The people there are quite friendly and you can ask almost anyone to give you directions. It is even more convenient to hire a two wheeler if you plan to move around a lot.
  • Watch the sun set over the sea - It really is a site to behold.
  • Eat the sea food and Goan cuisine - If you are a North Indian, give up the desire to eat the chicken tikka and chicken tandoori while you are at Goa. Get your hands on the excellent seafood offered by the restaurants there. Not only is it cheaper, most restaurants make very tasty dishes.
  • Try to get a room in the GTDC hotels - Goa Tourism Development Corporation (GTDC) hotels are government maintained, somewhat clean, comfortable and cheap. We stayed at Calangute Residency (Annexe).

Defined tags for this entry: ,

my perspectives on working in a small company - Part 2

This is a continuation of my previous blog post (my perspectives on working in a small company - Part 1). Here I will list the disadvantages of working in a small company.

  • Lack of resources - By resources I do not mean just in terms of money, but in terms of knowledge-base and manpower too. If a member of the team leaves or is sick, the work pressure on the others increases exponentially. Since most small company lack finance, it usually cuts down on the benefits provided to the employees.
  • Not enough ideas floating around - Since the number of employees are less, you do not have much diversity in line-of-thinking. If you feel like bouncing your ideas off someone else, you will not have much choice.
  • Too much work pressure - The work pressure is way too high. This usually translates into 6 days per week work days .. often with 9-10 hours per day. Though the work pressure is high, the salary and benefits provided usually do not match up to that. Most of the employers are stingy and usually play the carrot and stick game with the employees.
  • Danger of office romance budding - Been there, done that, got stung in the process :-) . Since the number of people are less, and the office hours are long, there is a strong chance of getting involved with someone. Though it does not always have a bad ending, in my observation it affects your work a lot.

Though it may seem that a small workplace is the hunting ground of satan, it is not really so. If the employer is good, the office can be a nice place to work at. I have a small test to check if the employer is a bloodsucker or not. If he says that you have to come in on Saturdays and possibly might have to work on Sunday,it is a sure sign that the office is a sweatshop. Avoid it

Defined tags for this entry:

the long vacation

It has been a long hiatus for my blog postings. A lot has happened in the interim. I got a job at Yahoo! Bangalore (yes, it is the same Yahoo! that brings you the famous yahoo.com ) :-) .


I have shifted to Bangalore (from Delhi). The city is not as bad as I had imagined it to be. The people at Yahoo! are an excellent bunch of yahoos - intelligent and friendly.

Hopefully I will be able to update the blog more often now. Thanks for staying tuned in

Defined tags for this entry:

public and private spaces

I have been thinking on how to distinguish between Private spaces and Public spaces. Let me clarify a bit by what I mean by Public space. Again the Wikipedia has come to my rescue. Wikipedia defines Public Space as

One definition of public space or a public place is a place where anyone has a right to come without paying an entrance or other fee. Typical examples are most roads, including the pavement, and public squares and parks. Typical differences between e.g. sitting on a public bench and sitting on a seat in a pavement cafe:
  • the first costs nothing
  • there is no time limitation
  • one can consume brought-along food and drinks (for alcoholic beverages the law prohibits this sometimes; this may even be the case if it is allowed in a pavement cafe)
  • a pavement cafe may have a dress code such as a prohibition of being shirtless, while in a public space only general law applies
Going by this definition, Private Space can be defined as its exact opposite.

There has been a lot of malls springing up in Delhi and nearby areas these days. The general population considers them to be a Public Space .. i.e anyone can come into the mall, browse around and generally hang-out. However, the homogeneity of the crowds at these places (teens with branded clothes, mobile phones, and generally with an I don't care but am conscious of your stare) leads me to think there is something wrong with it. I don't find this same homogeneity when I go out for a walk in my colony's road .

I have come up with a test to see whether a space is really private or public. The test is Does the place allow beggars and street urchins to come into it ? If yes, it is a public space. The roads and park in my locality cleanly qualify as a public space. At least the external grounds of Priya cinema hall, PVR Saket cinema hall, Dilli Haat qualify as public space. However, the malls like Ansal Plaza, 3Cs fail to qualify this test.

My reasons for choosing beggars and street urchins for my test is simple. Most people dislike being around them. To put it bluntly, their voice is the easiest and the first to be censored. Hence, if you want to test censorship, test whether the entity(in this case the owner of the mall) censors them. Now start extrapolating their censorship. Will these mall owners allow protesters protesting, let us say, the increasing private school fees. I doubt it. Will these protesters be disallowed from waving their placards and sitting on a hunger strike at the Jantar Mantar ? I doubt it.

Places which portray themselves as public spaces are not necessary so. Just some random musings on a Saturday afternoon while I was feeling sleepy at work :-)

Defined tags for this entry: ,

my perspectives on working in a small company - Part 1

Till a few days back, I worked in a very small company (5 people including the office boy). Over the next two days, I want to list down the advantages and disadvantages of working in such a small sized company. I am doing this, so that the next time I have to choose again, I have a written down list of checklist of my experiences that I can go through while making the decision.

The advantages are

  • Freedom to experiment with Free Software - Most (All ?) small companies work on a small budget. They are always looking for ways to bring down their working costs. In this, Free Software offers a definite advantage. The owners are willing to adopt option that you have researched and which have a cost advantage. From my perspective, this is a definite plus. It aligns well with my philosophy that software should be Free.
  • Freedom to have a say in who is hired - In my previous workplace, I was the one doing the interviews and vetting of the resumes. I was able to get two of my classmates from my college into the company. We were quite comfortable with each other and knew each other's quirkiness. In case of any problem, we usually were able to work things out by talking openly with each other. This definitely helped in getting more work done.
  • Lack of politics and backstabbing - This was the biggest plus as far as I am concerned. It allowed us to concentrate on the work at hand or our respective areas of interest without worrying if anyone else was going to take the credit of our hard work. I think since all of us were friends, taking anyone's credit was the last thing on our mind. Also in a small company, it is quite easy to see what is area of expertise of each person.
  • Multi area of expertise - I worked as a system administrator, programmer, team leader and the support guy for our products. This really helps in identifying areas that interest you. In my case I found that I prefer programming more than working of network security (which used to interest me a lot during my unemployment days). Having expertise in many areas also helps you when you are looking for a new job.
  • More responsibility - I used to maintain the production server at my company. I doubt that in even an average sized company they would have handed over the root password to a newbie. These things are not rocket science. Anyone can master them when he is faced with a hard choice of either learning the new thing or getting fired. In a smaller company, you have to be a fast learner and really have the belief that even though things are not making sense right now, they will start making sense once you are through the HOWTO or the quickstart guide. It really does wonders for your confidence.
  • Importance of writing and speaking without mixing in geek-terms - A thing which I learned early was the need to write in "normal" english i.e. writing things after filtering out all the geek talk. I was the support guy and when clients mailed me with their problem, my first reaction was to explain to them (in full gory details) why things were not working. Over time, I saw that they were more confused with my replies. I then learned the importance of illustrating my emails with screenshots and writing in terms of what people can understand.

In my next entry, I will detail on what are the disadvantages of working in s small company

Defined tags for this entry:

02-Feb-2005

On 1st February I joined a new company, Data Armor. With the new job, I also became one of the many Delhi commuters (someone who travels regularly from home in a suburb to work) . At my first job, I was lucky enough to have my office located at a fifteen minutes drive from my home. The traffic on that part was pretty light. However, the new office is at least forty five minutes drive, and that too through the very heavy traffic. I start out early in the morning and thus (have been able to escape) traffic snarls in the morning. However, the journey back is quite another story. I have to snake my way through bicycles, scooters, bikes and fast moving buses. :-(

On the positive side, I am working as a programmer right now, which is a very important change from my previous job as a programmer/sysadmin/team leader/support guy. I have always liked programming and got sucked into sysadmin-ing since I worked on Linux and knew a bit about networking. However, I do not really grudge being a sysadmin. It provided a bit of extra butter on my bread (through freelancing jobs) and bought me in tune with quite a few interesting people.

I think the problem right now is to chalk up a routine which balances my job+commute time+reading and learning time+ time for my efforts in the linux and php community.

Defined tags for this entry: