Chakravarthy Parankusam

Fix the cause, not the symptom. Intent does not erase Impact. “Code is like humor. When you have to explain it, it’s bad.” ~ Cory House “Bad programmers worry about the code. Good programmers worry about data structures and their relationships.” ~ Linus Torvalds Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” – Martin Fowler “First, solve the problem. Then, write the code.” – John Johnson "Optimism is an occupational hazard of programming: feedback is the treatment." ~  Kent Beck “When to use iterative development? You should use iterative development only on projects that you want to succeed.” – Martin Fowler “Java is to JavaScript what car is to Carpet.” ~ Chris Heilmann “Talk is cheap. Show me the code.”  ~ Linus Torvalds “Make it work, make it right, make it fast.” ~ Kent Beck “Simplicity is the soul of efficiency.” ~ Austin Freeman Your intent does not erase your impact. Your privilege...

TDD eradicates fear of change. As a developer, you shouldn't have to guess whether software is working correctly; You should be able to prove it at every step of the way. A test-driven development (TDD) process allows you to build testing into your daily routine. You can get instant feedback on the changes you are making which will increase your productivity, confidence and peace of mind. Definition: Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved so that the tests pass. This is opposed to software development that allows software to be added that is not proven to meet requirements. Cons of TDD: TDD will make you slow when the design is changing rapidly.  In TDD, emphasis is given to passing tests than design.  Passing tests is NEVER a key to good quality. Quality is made by design, not testing....

The theory of SOLID principles was introduced by Martin in his 2000 paper "Design Principles and Design Patterns". The SOLID acronym was introduced later by Michael Feathers. 1. Single responsibility principle A class should have only one reason to change Martin defines a responsibility as a reason to change, and concludes that a class or module should have one, and only one, reason to be changed (i.e. rewritten). "When designing our classes, we should aim to put related features together, so whenever they tend to change they change for the same reason. And we should try to separate features if they will change for different reasons." - Steve Fenton 2. Open-Closed Principle A module should be open for extension but closed for modification. Of all the principles of object oriented design, this is the most important. It means simply this: We should write our modules so that they can be extended, without requiring them to be modified. In other words, we w...

True Wealth is So Much More Than Money The majority of people think of the word ‘wealth’ in terms of finances only but this is a narrow view of what it means to be wealthy. Wealth consists of every area within one’s life — health, relationships, finances, time, so on and so forth. Different types of wealth: Financial / Material Wealth (Money) Social Wealth (Relationships) Time Wealth (Freedom) Physical Wealth (Health) Mental Wealth (Mindset) Spiritual Wealth (Satisfaction) The majority of people chase money and status at the expense of freedom and health. In the short term, this “works” somewhat to the favor of the individual but in the long term, it produces nasty consequences. Be careful of the system which tempt you in with financial / material wealth (money) but rob you of all other types of wealth (Freedom, Health etc.) What do you think about this ?

Where is your concentration ? Are you concentrating on doing things right or doing right things ? Doing things right will keep you going. Doing right things will make you move in right direction. Both are important; but with out doing right things, doing things right will keep you busy (you might even be very satisfied) and you might land in a wrong place. Dong things right and not doing right things might give you short term results but will fail you in the long term. So, make sure that you are doing right things before you start doing any thing. "Management is Doing Things Right, Leadership is Doing the Right Things" ~ Peter F Drucker Don't just manage your life and work. Lead your life and work. Feel free to share your thoughts in comments below.

Why working quickly is more important than it seems ? The obvious benefit to working quickly is that you’ll finish more stuff per unit time. But there’s more to it than that. If you work quickly, the cost of doing something new will seem lower in your mind. So you’ll be inclined to do more. The general rule seems to be: Systems which eat items quickly are fed more items. Slow systems starve. What’s true of individual people turns out also to be true of whole organizations. If customers find out that you take two months to frame photos, they’ll go to another frame shop.  If contributors discover that you’re slow to merge pull requests, they’ll stop contributing.  Unresponsive systems are sad. They’re like buildings grown over with moss. They’re a kind of memento mori. People would rather be reminded of life. They’ll leave for places that get back to them quickly. Part of the activation energy required to start any task comes from the picture you get in your head ...

As long as you worry about what others think of you, you are owned by them. You own your life only when you don’t need approval from others. “Care about what other people think and you will always be their prisoner.” – Lao Tzu People Pleasing Hides the Real You. Don't Change So People Will Like You - Be Yourself and the Right People Will Love the Real You. Feel free to share your thoughts in comments below.