NDepend Blog

Improve your .NET code quality with NDepend

The Daily Laws- 366 Meditation...robert Greene -

| Month | Theme | Core Question | Source Material | | :--- | :--- | :--- | :--- | | | Self-Mastery | How do I discover my life’s task and control my emotions? | Mastery , The 48 Laws | | February | Human Nature | Why do people act irrationally, and how do I accept this? | The Laws of Human Nature | | March | Power | How do I navigate hierarchical environments without naivety? | The 48 Laws of Power | | April | Seduction | How do I influence others through indirect charm (not just sex)? | The Art of Seduction | | May | Deception | When and how should I strategically disguise my intentions? | The 48 Laws , The 33 Strategies of War | | June | Strategy | How do I think multiple moves ahead in conflict? | The 33 Strategies of War | | July | Mastery | What is the apprenticeship phase, and how do I achieve creativity? | Mastery | | August | Human Nature II | How do I recognize toxic types (e.g., the narcissist, the envier)? | The Laws of Human Nature | | September | Power Dynamics | How do I maintain authority without becoming a tyrant? | The 48 Laws , Mastery | | October | Seduction II | How do I avoid being seduced/manipulated? | The Art of Seduction | | November | Sublimation | How do I channel dark impulses (anger, envy) into creative energy? | Mastery , The 48 Laws | | December | The Sublime | How do I achieve a detached, lifelong perspective on power? | All works synthesized | 3. Key Philosophical Threads Four recurring principles unify the 366 meditations:

Greene adopts a descriptive (not prescriptive) stance. He argues that power dynamics exist in all human interactions—corporate, romantic, political. The Daily Laws teaches readers to see these dynamics clearly, even if they choose not to manipulate them. The “Reverse” sections (e.g., “Law 1: Never outshine the master… Reverse: If you are the master, encourage outshining”) provide ethical balance. The Daily Laws- 366 Meditation...Robert Greene

Over 60 meditations (primarily in January and February) focus on emotional intelligence as Greene defines it: not expressing empathy, but rather mastering one’s own reactive nature. He argues that anger, jealousy, and insecurity are “leaks” that others can exploit. Example: February 14th – “The Law of Irrationality” explains why people overreact to perceived slights. | Month | Theme | Core Question |

Abstract Robert Greene’s The Daily Laws (2019) is not a new philosophical treatise but a curated, chronological digest of his previous six bestsellers. Designed as a daily reader, the book extracts 366 lessons (including a leap day entry) to serve as a pragmatic toolkit for navigating power dynamics, mastering a craft, understanding irrational human behavior, and practicing strategic thinking. This paper examines the book’s architecture, its core thematic months, its pedagogical function as a “master’s course,” and its critical reception. 1. Purpose and Structure Unlike Greene’s narrative-driven works ( The 48 Laws of Power , Mastery ), The Daily Laws adopts a behavioral modification model. Each day presents a meditation—a quote, a historical anecdote, and a practical command. The year is divided into 12 thematic months, each addressing a distinct facet of Greene’s overarching philosophy. | The 48 Laws of Power | |

Comments:

  1. Ivar says:

    © 2026 Grand Node. All rights reserved.

    I can imagine it took quite a while to figure it out.

    I’m looking forward to play with the new .net 5/6 build of NDepend. I guess that also took quite some testing to make sure everything was right.

    I understand the reasons to pick .net reactor. The UI is indeed very understandable. There are a few things I don’t like about it but in general it’s a good choice.

    Thanks for sharing your experience.

  2. David Gerding says:

    Nice write-up and much appreciated.

  3. Very good article. I was questioning myself a lot about the use of obfuscators and have also tried out some of the mentioned, but at the company we don’t use one in the end…

    What I am asking myself is when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
    At first glance I cannot dissasemble and reconstruct any code from it.
    What do you think, do I still need an obfuscator for this szenario?

    1. > when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.

      Do you mean that you are using .NET Ahead Of Time compilation (AOT)? as explained here:
      https://blog.ndepend.com/net-native-aot-explained/

      In that case the code is much less decompilable (since there is no more IL Intermediate Language code). But a motivated hacker can still decompile it and see how the code works. However Obfuscator presented here are not concerned with this scenario.

  4. OK. After some thinking and updating my ILSpy to the latest version I found out that ILpy can diassemble and show all sources of an “publish single file” application. (DnSpy can’t by the way…)
    So there IS definitifely still the need to obfuscate….

Comments are closed.