I was getting ready for my next article on .NET but then this thought of how it's always not programming/technical capability or know-how that helps to refine the Software development or any other piece of work.
It's Not an Advice! and just my observations and experiences that I get every day in Software space.
Read/Analyze what others have done: 
Will be helpful for someone new to a project or completely new to Software Development or even other domains. It will be tough to read a past technical/domain documents or Historical Source codes, but I would say it improves certain things like "Analysis", "Patience", "Flexibility" and also "How different we can modify/innovate current requirements based on what was done before us" and also give the range of ideas to speak to your peers and also cross-teams.
Go Cross knowledge:
Sometimes solving mathematical or Logical puzzles or playing a sport or music or just a walk and chit-chat could help refine your thinking process which actually helps in your Software Development process and helps to handle bigger tasks or algorithms. After an early morning run or a fantastic badminton practice...suddenly there is a better clarity of how to design a system or solve a complex bug...Take up that excites you, but just do it as it is normal, don't force it.
Look for Alternatives: 
Sometimes you might reach a solution immediately on top of the head and would be willing to complete that and push the source code and finish it off...hold on!...it might be great to get the solution just like that...you are already good in that, but it's always better to find multiple alternatives, which could be(an improvement in process/performance/quality...that alternative solution could help you at a right moment, where-in you might have to ship a Changeset in couple of hours/days...critical junction...so this pre-knowledge on alternatives will surely come handy)
Open to Review: 
Most of the time it's difficult for Programmers/Designers to take things lightly if someone reviews our code and indicate mistakes (which might be trivial/complex/hybrid.)...Instead try to sit through the points one by one and analyze better and if you feel what you have done is fine...then try to convince in a friendly manner or check with other peers about the corrections suggested and accept them and keep the sync going. This will help to reduce the ramblings in meetings and improve our overall perspective about working in teams, change acceptance and negotiations.
Complex Work: 
Let's say you are comfortable with existing project. Dev/Test Updates, Deployments and Client request resolution. So, this cycle could be good, but to prepare for bigger assignments, in between your regular tasks, take a complex algorithm to solve for another project in real-time...need to crunch extra hours...but in longer run, it will help to get noticed by many teams and increase your chance of getting complex and challenging projects.
Keeping Tabs on Trends: 
As it's quite a competitive landscape, as technology is...It's a given that we need to embrace new trends on technology, those that interest us and practice them to continue the enthusiasm going on. Technology for an extended period is quite a challenging one. Relaxation, Less Motivation and Boring Regularity might haunt us, but then we need to diffuse and keep going forward and be ready for that fantastic opportunity.
I am pretty sure this is not go-to list or a complete list...Just the observations and learnings I got. Hope it at least have some convergence with your observations as well.
Please do Share your own comments/suggestions to improve on this.
Top comments (0)