What I learned in Software Life... Find Solutions!

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 essential. Having a practical idea to solve a seemingly complex technical problem, always finds real solutions.

Code is the last point to instruct computer.

This is the key fact many of us forget. You cannot do much after code is baked into binaries and delivered. Settings and configurations cannot alter much of the behavoir. They only choose a route already coded. One has to have a feeling of 'this code will never come back' attitude while coding.

If customer reports a defect, THERE IS A DEFECT!

People argue with customers on how a behavior is not a defect. But mind you, if customer is reporting a defect there IS one. The cause may be any thing; a bug in software, customers understanding of new system, lack of documentation, undocumented work around, hardware problems, or even out-of-scope case. Instead of arguing with customer, if you find a route cause and provide logical explanation, customer will agree more than you think!

Comments

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

Tips for a long ride

A long ride on a Motorcycle is a thing filled with thrill and excitement. How much long is 'long'? Should it be defined by distance, time taken, number of breaks or the difficulty level? I think its a combination of all. Depends on how much time you spend and how much stress you are subjected to. None-the-less, here are some tips I scribbled. Before the ride: Research the route. thoroughly. For road conditions, stops, fuel bunks, service and emergency support etc. Estimate timings. Plan the short stops and overnight stay if need be. Book in advance. Research the weather. and prepare for it. Prepare the travel kit. Plan on type of luggage. Plan the weight distribution. Make sure it will be well balanced when on bike. Plan the luggage according to Cabin/check-in concept. Practice some maintenace if you can. e.g. Chain cleaning and lube, puncture removal, minor adjustments and settings. etc. Go for multiple short rides to get used to your bike. You must get used to extended sitt...

Classification of long rides

The perception of long ride varies greatly among motorcycle riders. Especially new ones (does not mean young ones). Some call 400km ride a long ride, some call 1000km ride a medium one. Not that I am an expert on motorcycle riding, but I thought of putting the method to this madness. I jotted down my thoughts about classification of rides. I thought of 3 key parameters viz. Distance traveled, Time taken, and Effort put. Based on these I came up with following categories By Distance: 1. 400-1000 km. A ride should at least be 400km to think of it as a long ride. 2. > 1000 km. These rides really require a lot of preparation, stamina and experience. By time: 1. 2-3 days: Have more than one day, and you can reach longer distances which is essential for long ride. Exceptions exist, but yeah. they are exceptions. 2. week-long: Week long ride requires good planning, carrying of enough luggage and tough mind. It should not just be a rote ride. Some sight-seeing, adventure, experi...

Aniruddha Raste's blogs

Search This Blog