Wednesday, April 21, 2010

Wealth Isn’t How Much You Earn

 

via The Simple Dollar by Trent on 3/23/10

At age 25, Jim makes $100,000 a year. He's constantly traveling for business. He has a large home in which he often doesn't visit some rooms for months at a time. He eats out every single night. He drives a leased Lexus, which he updates every few years at the end of the lease. He buys a whole new wardrobe every six months, taking the leftovers to Goodwill. He spends everything he brings in.

At age 25, Bill makes $35,000 a year. He lives in a smaller home and doesn't travel much. He makes most of his own meals at home. He drives a Toyota Corolla, which he owns free and clear. He wears clothes until they're worn, then shops at Goodwill for replacements, often picking up Jim's barely-worn clothes. At the end of the year, he usually has about $5,000 of his income left over, which he sticks into his stock investments which earn 8% a year.

In ten years, Jim's net worth hasn't grown a cent. In those same ten years, Bill has $72,000 in the bank.

At the twenty year mark, Jim's net worth still hasn't grown a cent. In those same twenty years, Bill has built up $228,098 in the bank.

At the thirty year mark, Jim's still breaking even. Bill, on the other hand, has $566,416 in the bank.

At age sixty five, Jim hasn't accumulated a cent and will be working for the man for the rest of his life. At the same age, Bill has $1.3 million in the bank and can do whatever he wants for the rest of his life – and probably already started doing that a few years earlier.

It doesn't matter how much you earn. It matters how much you save.

When I was twenty five, my net worth was negative and heading south rapidly. I spent more than I earned and I didn't really worry about the consequences of it. I figured if I had the money – or the credit – I certainly ought to spend it in whatever way made my life more enjoyable right now.

I'm now thirty one. My net worth is still negative (although it would be positive if I counted the value of my home towards it, which I do not), but it grows every month in a positive direction and will soon become positive even without the house value.

One might immediately think that I must have made my life less enjoyable to make that change. Actually, my life is more enjoyable now.

I have a better grasp on the things that actually make me happy and I don't waste my money on things that don't.

I'm not chained to a desk and a career, fearing the pink slip – I set my own career rules and goals.

I'm not afraid of getting the mail any more and I don't wake up at night worried about how I'm possibly going to make ends meet or pay all of this off in the future.

Perhaps best of all, my financial position is improving every single month and I no longer see the long-term future as some kind of musty cloud that will "work itself out." I know it's getting better and I know that, if I continue on this path, I'll be able to easily have some of the big things I actually want in life, like a beautiful house in the country with some wooded land in the back.

My life now is something I'll happily trade having a shiny new Lexus and an iPhone and a set of high-end golf clubs and eating out every night for. In exchange, I'm not worried about the future and I have career and personal freedom I would never otherwise have.

Wealth has little to do with how much you earn. It's how you spend – or save – it.


 
 


 

Saturday, April 3, 2010

Nishad's marriage

Today was a busy day. Of course every day I am in office its a busy day for me. But today, I took the trouble of travelling a long distance to attend a friend's marriage function in Kozhikode, Kerala.

Nishad A V is a room mate of mine from college days. A star player, he is the most athletic, (and one of the popular ones) among us. And he got married today at a small function attended by more friends than relatives. But the fun part was that I got to catch up with a lot of friends I had forgotten even existed.

My observations.

1.Kozhikode city hasnt changed at all, except for the well maintained roads.
2.It's getting hot all over the state. And even we locals cannot adjust to the heat now.
3.This was my first experience of a muslim wedding.
4.The food was awesome!


Its after a long time I said hi to a few of those guys. But please pardon me.Its just that at one point I worked really hard to get this busy. And today,I think I enjoy my work and being busy.


So here's wishing the newly wed couple a happy married life.


And off you remaining bachelors and bachellorettes, what are u waiting for ? Give us some more reasons to travel home and catch up.

Thursday, April 1, 2010

Now you can easily add images to your scraps!

 
 

Sent to you by Ranji via Google Reader:

 
 

via Orkut Blog by A Googler on 3/26/10

We're always listening to what users have to say about orkut, and we're constantly working to improve your orkut experience. One of the suggestions we've received many times is to bring back to the ability to add photos to your scraps to the new orkut. We're happy to announce that this feature is now available!

To add images to your scraps, first click the text box to write and edit a message. You'll then see customization options, such as font color and emoticons. Click the image icon to add an image to your your scrap:



You can upload images from your computer, add from your Picasa Web Albums, or search for them in Google Images.

As we like to say, a picture is worth a thousand words. So, hopefully this feature will improve the way you share things with your friends on orkut!

Posted by Marco Domingues, orkut operations team



 
 

Things you can do from here:

 
 

File transfer in orkut and iGoogle chat

 
 

Sent to you by Ranji via Google Reader:

 
 

via Orkut Blog by A Googler on 3/29/10

Have you ever wanted to quickly send a file to a friend who's online? Now it's easy! We're excited to announce that you can now share pictures, documents, and other files with your friends while chatting in orkut and iGoogle. To give it a try you don't need to install anything, simply start a conversation with a friend and click Send a file... in the 'Actions' menu:



This feature is also compatible with the file transfer functionality in the Google Talk downloadable software, so you can share files directly from the web with folks who use the desktop version.

File transfer is available in orkut and iGoogle only for now. We're working on bringing it to Gmail as well, and we'll keep you posted when that happens!

Posted by Lizhen Wang, software engineer



 
 

Things you can do from here:

 
 

Tuesday, March 30, 2010

Fwd: Nice process, but what about the engineering bits?

 
 
 

via Ayende @ Rahien by Ayende Rahien on 2/19/10

Software processes has always been a popular topic of discussion in our industry. Those can get quite heated, with advocates of the "stable / stale" Waterfall method pointing fingers toward "rapid / rabid" Agile methods, with the CMMI people throwing documents around and Lean people standing on the sidelines muttering about Waste.

This isn't a post about a specific software process, I'll defer that to another day. Instead, I want to focus on a flaw in the basic building blocks in many* software building processes.

They ignore the actual building the software.

That may sound ridiculous on the face of it, after all, how can a software process ignore the act of building software. But take a look at the following diagrams:

image

If you'll pay attention, you'll notice that those processes talk about everything except how to actually build software. They talk about people, about requirements, about managing customers, about a whole lot of things, but not about the part where you have people sitting down and writing code. In most of those, in fact, that part is usually defined as one of those:

image

Why is that a problem? After all, isn't there a big distinction between software engineering (we know what to do, now let us do it) and project management (getting to know what we need to do, and verifying that we did it right). Those processes deal primarily with project management and leave the engineering part to be defined in a way that fit that particular project. Surely that is better, right? In theory, it might be. But there is a big problem when you have a software process that ignore the software engineering aspects of building software.

The problem is that that in many cases, there are hidden assumptions that are going to hammer you down the road if you use a certain process with engineering practices that doesn't fit it. Take a look at the following chart, showing a team velocity over time, does this look familiar?

image

The term I heard used for this is Scrum Wall, but I have seen similar results in other processes as well. The best description for that is Allan Kelly's:

You hit the Scrum wall when you adopt Scrum and everything goes well, then, after a few Sprints things don't work any more - to use an English expression, they go pear shaped. You can't keep your commitments, you can't release software, your customers get annoyed and angry, it looks like Scrum is broken.

This is what happens when you adopt Scrum without technical practices such as Test Driven Development, continuous integration and refectoring. When teams adopt the Scrum process, they go faster, show progress, things look good... and then the quality becomes a problem. Now the team are fighting through quick sand.

The code quality is poor and developers are expected to continue to make progress. Maybe the Scrum Master/Project Manager reverts to past behavior and demands overtime and weekend working. Maybe the team start busting a gut to keep their commitments. Either way the team is heading for burn-out.

The major issue is in focusing so much effort and time on project management with what amounts to willful ignorance of the technical and engineering practices will inevitably leads to disaster. The process of building software is intractably linked to the engineering practices involved in building the software. Moreover, some technical practices are actively harmful in some scenarios and life savers in others.

Many Agile and post-Agile processes focus on short cycles, each of them producing something with a distinct value to the customer. That may be an iteration, a commit or a feature, where the goal is to increase the velocity over time so we can provide as much value to the customer in as short a time as possible. What those processes ignore are things like technical debt, large scale refactoring and non functional efforts. Oh, you see those things mentioned on the edge, but they aren't something that is dealt with heads on, as a core issue to consider.

There is a bit more to that, actually. The software engineering practices and the project management strategies are linked and of paramount importance when the time comes to decide how the software should actually be built. No, this is not tautology. We just need to take into account Conway's law and expand on it a bit.

Any organization that designs a system will inevitably produce a design whose structure is a copy of the organization's communication structure.

Part of the design process of a project should include design the team(s) structure, the project management strategy and the software engineering practices in order to align the end result with what is desired. Ignoring this leads to imbalance in the project, and if that imbalance is big enough, and goes on for long enough, the project is going to rip itself apart.

* Nitpicker corner: I said many, not all. Don't bother to list me software process that deals with it. I had a reason to explicitly list the processes that I did.


 
 



 

Tuesday, March 16, 2010

Revisiting Finland

I miss Finland !

Sure, the work was hectic, and I hardly got time to explore the place, but it sure was fun being there.

Finland is now on Google street view which means, now you can see the place too. You can use the mouse inside the controls to zoom around. You need Flash installed to use Google Street View.

For example, here is the place where i was stayin in Finland


View Larger Map

The building on the let was where I was staying and which I nearly set on fire during my cooking experiments.

This is a shot of the of the road to my office.


View Larger Map

This is where I was staying the second time I was in Finland.


View Larger Map




This is the Railway station in Helsinki, Capital of Finland


View Larger Map


And here is the Accenture office in Helsinki, Finland.


View Larger Map