Skip to main content

What I learned in Software Life... Develop yourself!

In my previous post What I learned in Software Life...People make great teams!  in the same series I mentioned about how peoples' interactions and nurturing is important to success. In this post, I would like to share my thoughts on self-development

Continuous improvement must be a part and parcel of your life - be it professional or personal.

Training is best learning

I completely believe in this. If you can explain a topic to other person, you yourself get command over it. While explaining a concept, you get to look at the topic from different aspects. As a trainer, when you answer questions from audience, you have to be prepared to respond to variety of questions coming from audience. It is a challenging job to satisfactorily answer them. An unexpected case study may come up. This helps make your foundations stronger.

Find similarity of concepts across various fields

Many different fields implement similar concepts whose underlying principles are same. It is very interesting to know and learn this. This is why children are told stories which are imaginary, but with real concepts. E.g. there is lot of similarity in fluid flow and traffic on a road. Understanding behavior of one system will help understand behavior of other system.

Love your work

This is absolutely essential if you want to find pleasure in your work. You can take the whole experience and the result to unexpectedly high level. You also get mental satisfaction that keeps boosting your energy and enthusiasm.

Show interest in multiple subjects

Having interest in more than one subjects gives you multiple benefits. You will not get bored very often. You will always have a topic of interest to work with. Moreover, Key concepts of one field can be ported to another field. E.g. I tried applying some concepts from Ayurveda to developer personalities. Can a historical personality like Mahatma Gandhi tell us something about coding?

Comments

Post a Comment

Popular posts from this blog

Pune-Goa-Pune Motorcycle solo ride: A ride that was many things!

  Part 1: We decided to ride "Let's go Goa!" College group of friends and families announced the yearly Goa trip. Some said: We are flying.  Some said: We will take train.  Some said: We will drive. Shree (my friend) and I: (our wives not coming because of prior commitments) let's ride our RE Meteors! That's how we decided to ride. And a plethora of things started. Route search, Road condition R&D, riding schedule, packing list, load distribution, checking on safety gear, rain preparations, pre-ride maintenance and so many. We searched a lot on the web. read a lot of articles, blogs, updates and finalized on Pune-Karad-Anuskura-Rajapur-Goa route. While preparations were in full swing, Shree caught Chikungunya infection and was down with high fever! There was no possibility of him riding! However, I decided to ride solo and complete the trip. With Solo riding decision, few things changed. Non-stop one-way ride changed to a break journey. I d

A short ride to Kondane caves

This time it was a combined Trek and Ride experience. Motorcycle ride for 3 hrs. from Pune to Kondane caves base, Mini-trek of 45 min. to Kondane caves and ride back home.  My younger son Chinmay was my partner. He likes to ride with me once in a while, and definitely likes to trek :-)

Forcing to lock, Choosing to engage...

In last post Customer is the king... and more! , I wrote about inevitable customer dependency and how sellers may take advantage of it. Dependency should not create a sense of 'being locked' with the product or service. Some ways by which customer gets 'locked' are: Proprietary data format and ways to read / write it Custom components to do trivial jobs User accounts, loyalty programs Restrictive licensing Artificial compatibility between hardware and software components of same seller What are the ways to reduce - if cannot entirely remove - customer's dependencies on sellers and their products? Some ways are: Increase standardization, use minimal standards Increase generalization, reduce specialization Make product flawless Make product stateless Educate customer to help himself Make system customizable / soft coded Provide compatible components and let customer assemble it to suit his purpose Make interaction transactional Some of th