Aniruddha Raste's blogs

भाग १: आम्ही फटफटी चालवण्याचा निर्णय घेतला "चला गोव्याला जाऊया!" कॉलेजमधील मित्र आणि कुटुंबियांनी वार्षिक गोवा सहलीची घोषणा केली. काही म्हणाले: आम्ही विमानाने जाऊ. काही म्हणाले: आम्ही आगगाडीने येऊ. काही म्हणाले: आम्ही मोटारीने येऊ. श्री (माझा मित्र) आणि मी: (आमच्या बायका त्यांच्या आधी ठरलेल्या कामांमुळे येणार नव्हत्या) चला आपल्या रॉयल एनफिल्ड मेटीऑर्स वर जाऊया! अशा तर्‍हेने आम्ही फटफटी चालवण्याचा निर्णय घेतला. आणि अनेक गोष्टी सुरू झाल्या. मार्ग शोध, रस्त्यांच्या स्थितीचे संशोधन, रपेटीचे नियोजन, नेण्याचे सामान, वजन वितरण, सुरक्षा पोशाख (अंगत्राण) तपासणे, पावसाची तयारी, प्रवासपूर्व देखभाल आणि बरेच काही. आम्ही आंतरजालावर बरेच लेख, ब्लॉग, अपडेट्स वाचले आणि   पुणे-कराड-अणुस्कुरा-राजापूर-गोवा मार्ग पक्का केला. तयारी जोरात सुरू असतानाच माशी शिंकली- नव्हे, डास चावला!- श्रीला चिकुनगुनिया झाला आणि त्याला भयंकर ताप आला! त्याला रपेट करणे शक्यच नव्हते! मी मात्र, एकल रपेट करून सहल पूर्ण करण्याचा निर्णय घेतला. एकल रपेटीच्या निर्णयामुळे काही गोष्टी बदलल्या . एका दिशेला थेट जाण्याचा मनसुबा सो...

  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...

In my previous post What I learned in Software Life... Develop yourself! I talked about developing yourself in order to find better solutions. It is only imperative, that our job is to find solutions to customer's problems. That is the primemost reason why customer goes out and seeks help. Good design can deliver miracles. This is true for any field. Be it Engineering, software, Medicine... what ever. Creating a good design is definitely a challenging job. It is a bridge between 'requirements' that are only stated and 'implementation' that realizes the solution. Any flaw in design will always show up at some stage or other. Practical ideas make more sense in business world. There is a distinct difference between Scientist's world of perfection and idealism and Engineer's world of realization of solutions with available resources. To be able to deliver in given resources which are always limited, tools, processes and competency become e...

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...

In my earlier post What I learned in Software Life...Stay On! I talked about importance of persistance and perseverance.    There is something to learn from everybody.   We underestimate people a lot. People come with different professional, social and educational backgrounds. They have a lot to contribute to a solution. Many innovations can be achieved by using knowledge from people from other disciplines. Do you know what Mahatma Gandhi told about coding? Simplicity is the key to success! On the other hand, you can learn highest level of 'definition of quality' from a child! Criticize yourself . Key quality if you want to progress. It lets you introspect. It lets you learn by self analysis. It give you an ability to look at yourself independently. You become your own mirror! Mind, emotions and intelligence are correlated.   Care for peoples' mind and emotions, and people will deliver intelligence. Many a times people are treated as mere e...

In my earlier post  What I learned in Software Life... Be Open! in the same series, I described an importance of openness.   Continue, even if you face hurdles Losing patience, changing course, switching routes, leaving in the middle, neither take you completion, nor give anybody any satisfaction.Continuing forward is the best way to reach destination. Hurdles will be everywhere. It is your ability to face and overcome them, makes success out of it. Persist against all odds, if you are damn confident of result Many times such persistence may be mistaken as being adamant or egotistic, but your confidence will give you all the energy to persist. You HAVE to be damn confident of the result. Others will create hurdles, as they may not fully understand your path, they may be stuck up with old concepts, they may have fears of trying new ways. You need to persist on your path. Remember ' Eppur si muove ' If you come across a wall, climb it!   This ...

With a rich and happening 17 years of software development life, I learned a lot. Here is what I learned in my professional life. Be receptive and listening . This is very important quality of a good developer. Have a receptive mindset and listening attitude. You will understand many subtle requirements, tricky behaviors of systems and special situations. Inputs can come at any time and in any form. Not all requirements can be stated at the start of project. Not all solutions can be obtained before you start to implement them. Many a times a critical input can come late in the game, or it can come from an unexpected source or in an unexpected form. Previous quality will help you catch such inputs. This necessitates two things: Always be listening to your surroundings, keep grasping the situation and; make your design extendible! Say yes ! Many people are afraid to accept a challenge, accommodate a change or try a new way of doing things.No doubt it requires mo...