Why I no longer call them goals

Calling your goals, “goals”, leaves you at a disadvantage. From now on, I suggest that you call them outcomes.

Let me tell you why. An article in the New York Times spells it out clearly: names have power. The way in which we speak about things affects our brains.

The term “goals”, has multiple meanings, depending on the context. In one way it means where you’d like to be, but in many other instances, it can mean, dreams, vision or desire. A wish, far off, into the future. Goals also have you thinking about the end result and not so much on how to get there.

Calling your goal an outcome, automatically implies that, for something to come out, something must go in. Your mind starts to wonder about how, and as research has shown, we solve problems in our sleep. The more you think about your outcomes the more you are likely to work towards them.

I have made a decision. I will only put my dreams on my outcomes list if I have attached a new habit to it. Want to lose weight? Add the habits of a better diet and regular exercise. Want to earn more money? Attach the habit of developing your skills and reading. If the outcome is worth pursuing the habit is worth cultivating.

If what you are thinking about is truly a “goal”, try something more specific, like dream, vision or desire, but don’t call them goals.

Featured image by Andrey Larin https://unsplash.com/photos/Kodkas71tT8

Habits of Highly effective Software Engineers

Valuable advice from the “Tech Lead”. A career in software engineering is a long term game, it’s a marathon, not a sprint. Having habits like these, ensure that you’re preserving yourself as you grow in experience and influence.

  1. Healthy Lifestyle, exercise, water and nutrition. Keep a good posture.
  2. Good Sleep routines.
  3. Continual learning. Keep your skills sharp.
  4. Have result-oriented work ethic. Focus on being effective, get work done.
  5. Keep things simple. For yourself and others. Complexity works against you.
  6. Create periods of deep work in your day.
  7. Collaborate with other programmers to save time and effort