The process before the content

From my perspective, I still have a long way to go. I do however think that sharing what I know today is valuable, not for the sake of what I share, but for the process of refining the idea. I place the process before the content, with the hope that a refined process will lead to fine content.

Writing is thinking is a good metaphor for how I use this blog. I blog and share my posts public-ally so that I can exercise structured thinking. Looking for ways to better express my thoughts and find the best words to illustrate my ideas.

Both the content and the process really do matter, but as I shape my writing process I make sure that I continually fill my mind with things to write about. I believe that applying the correct writing style to great content will be a valuable skill in any context.

I have already started noticing a change in the way I write at work. Doing blog posts forces me to think through what I’m writing. Knowing that it will be shared publicly puts enough pressure on me to ensure it is at least decent.

Blogging is only for the successful, is how I used to think. Now I know that blogging leads to success. Being ables to communicate clearly is a skill worth practicing.

Simple Money Advice

Someone shared this with me a while ago and I keep thinking about it. The advice is 3 simple thoughts:

  1. Make all you can make.
  2. Don’t be overly lavish.
  3. Give all you can give.

We can grow in our ability to make, spend and give, but we should keep spending in check, while allowing making and giving to flourish.

Docker Compose Volumes Empty?

The problem is that you’re expecting files from the Container to be mounted on your host.
This is not the way it works: it’s the other way around:
Docker mounts your host folder in the container folder you specify. If you go inside the container, you will see that where there were supposed to be the init files, there will be nothing (or whatever was in your host folder(s)), and you can write a file in the folder and it will show up on your host.

Answer from: https://stackoverflow.com/questions/42395748/docker-compose-volume-is-empty-even-from-initialize

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