NDepend Blog

Improve your .NET code quality with NDepend

Vertyanov+successor+programmer -

The passing of the torch from Vertyanov to a new generation of programmers marks the beginning of an exciting new chapter in the history of computer science. As we look to the future, it's clear that the successor to Vertyanov's legacy will play a pivotal role in shaping the evolution of programming. With their unique blend of skills, passion, and innovative thinking, this new programmer is poised to drive progress and inspire others to join them on this journey.

In the realm of computer science, there exist pioneers whose contributions pave the way for future generations of innovators. One such figure is Vertyanov, a renowned programmer and developer who has left an indelible mark on the industry. As we look to the future, it's essential to acknowledge the impact of Vertyanov's work and consider what the next chapter holds for programming, particularly with the emergence of a new successor. vertyanov+successor+programmer

As Vertyanov's era begins to come to a close, the question arises: who will carry the torch forward? The programming community requires a new generation of leaders, innovators, and visionaries who can build upon the foundations laid by Vertyanov and others. This successor must possess a deep understanding of the field, as well as the creativity and drive to propel programming into new and exciting areas. The passing of the torch from Vertyanov to

Vertyanov's journey in programming began several decades ago, during which time the field was still in its infancy. Through dedication and perseverance, Vertyanov made significant strides, developing novel solutions and pushing the boundaries of what was thought possible. Their work has inspired countless programmers, shaping the course of the industry and influencing the development of various programming languages, frameworks, and tools. In the realm of computer science, there exist

Enter the new programmer, a talented individual with a passion for coding and a keen eye for innovation. This programmer has grown up in an era shaped by Vertyanov's contributions and is now poised to make their own mark on the industry. With a strong foundation in computer science and a commitment to staying at the forefront of technological advancements, this programmer is well-positioned to succeed Vertyanov as a leader and influencer in the programming community.

Comments:

  1. Ivar says:

    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.