Renounce Nothing, Attach to Nothing...

Table of Contents

Renounce Nothing, Attach to Nothing…

Today I experienced an “AHA” moment in a certain area. Since the topic is universal, I decided to share it. This is somewhat a continuation of a post from a year ago.

I once read a sentence by Anthony de Mello which states, “Renounce nothing, attach to nothing.” A philosophical statement that, although seemed correct in every respect, was so abstract that I found it hard to translate into pragmatic application. However, I have now discovered its practical meaning and importance.

Once upon a time, I didn’t like waking up early. I hated it. I could call myself a “night owl” personality – I like staying up late, but you couldn’t get me out of bed in the morning. After a few years and the influence of external factors such as children, I started to have to wake up early. What’s more, after a few months, waking up early ceased to be a torment for me. Sure, I enjoy staying up at night, but if I need to get up early, it’s not a big problem. And then it hit me…

I used to be so identified with the thought that waking up early was torture and that it wasn’t ME that the very idea of getting up in the morning made me angry. And once I got up, it was best to stay out of my way. Now it doesn’t make a difference to me. I feel that in this area I possess the space of choice, not necessity. I felt great relief. That’s what “Renounce nothing, attach to nothing” means.

And I saw how it applies to so many areas… Not just within programming projects ;-)

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

The Natural Order of Refactoring Examined Part 4: Refactoring to Patterns

The Natural Order of Refactoring Examined Part 4: Refactoring to Patterns

By following the steps outlined previously, we begin to see a more structured solution, predominantly consisting of methods grouped into classes. It’s now time to apply object-oriented principles, such as those encapsulated by the SOLID principles. We analyze the code for patterns of repetition, the need for flexibility, and code smells, and introduce design patterns where appropriate.

Read More
Antipattern: Adrenaline Junkie

Antipattern: Adrenaline Junkie

Understanding Project Pressure and Tension

I constantly wonder why situations arise where pressure and tension are generated in projects. One reason is that most projects are simply complex—you have to coordinate several, sometimes dozens of people, anticipate and plan in advance what will happen, and determine what resources will be needed. As a species, we’re not very good at detailed long-term planning (see: David Rock – Your Brain at Work).

Read More

Have a Clear Vision, Stick to the Intention and Adjust the Implementation

No matter if you are a tech lead, Scrum Master, Product Owner, or a member of the team, if you want to make your idea a reality, here is a very simple (and of course very difficult to implement) advice:

Read More