Tesknij_za_kolejnym_dniem May 2026
Paradoxically, longing for the next day requires a deep appreciation of the present. You cannot authentically look forward to a future if you are completely detached from your current reality. To "long" for tomorrow is to plant seeds today. It is the athlete training in the rain because they long for the race; it is the student studying late because they long for the career. In this sense, the phrase bridges the gap between being and becoming . Conclusion
At its core, longing is often associated with the past—a nostalgic ache for what has already slipped through our fingers. However, "tęsknij za kolejnym dniem" flips this temporal focus. By longing for the future , we shift from a state of passive regret to one of active expectation. This mindset transforms the mundane passage of time into a series of opportunities. When we "long" for tomorrow, we are essentially affirming that our story is unfinished and that the best chapters are yet to be written. Purpose as the Catalyst tesknij_za_kolejnym_dniem
"Tęsknij za kolejnym dniem" is an invitation to reject cynicism. It is a reminder that hope is a discipline, not just a feeling. By cultivating a sense of yearning for what is to come, we imbue our lives with a sense of momentum and grace. It teaches us that as long as there is a "next day," there is a reason to keep moving, to keep creating, and to keep believing in the beauty of the unknown. Paradoxically, longing for the next day requires a
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.
Nice write-up and much appreciated.
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?
> 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.
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….
Ok, Btw we compared .NET decompilers available nowadays here: https://blog.ndepend.com/in-the-jungle-of-net-decompilers/