It will be very useful for every Java developer to understand what the JVM is, how the code gets into it and how it is executed. The article is more suitable for beginners, but more experienced programmers can also find something new in it. The article briefly describes how the class file works and how the virtual machine processes and executes bytecode.

The main focus of Java developers was to create portable applications. The JVM plays a central role in portability — it provides an appropriate level of abstraction between the compiled program and the underlying hardware platform and operating system. Despite this additional “layer”, the speed of applications is unusually high, because the bytecode that the JVM executes, and it itself, are perfectly optimized.

Tip 1: ask!

Perhaps the first and most obvious piece of advice is – don’t be afraid to ask. Asking questions is an important skill, one of the most useful in the future, in my opinion. By the way, you can ask not only your direct colleagues in the project / type of activity, but also colleagues from related areas: testers, managers, analysts. Sometimes knowledge gained by accident turns out to be the key to understanding more serious problems. Besides, human experience is the most valuable thing; many things cannot be learned from books. Over time, an understanding of this comes.

Tip 2: write it down!

Have a thought about what you can do in the project? Save. Have an idea of ​​how you can improve your skills? Write it down. Then you can revise these notes and learn something important, or maybe understand that you have already achieved something. In times of crisis, such “save” help to remember why you chose what you are doing at all.

Tip 3: get inspired!

One more thing: find non-financial motivation. When a person decides to “enter IT” for the sake of relatively high salaries, without being interested in the field as such, it is very noticeable. There is nothing wrong with finance, but it shouldn’t be the only driving factor. If the eyes do not light, then no zeros in the work book will be able to light them.

Tests (test cases) can be grouped into sets (test suites). If testing fails, the programmer will see the names of the culprits – suites and tests. In this regard, the name should inform the programmer about the causes of the trouble and the modules involved.

The name can be useful in other cases as well. For example, a customer found an error in the program, which means that the programmer must either add a new test or fix the existing one. Therefore, you need to be able to find the test by the nature of the error, and well-chosen names can help in this.

Typically, the test name consists of the name of the class or function being tested and reflects the specifics of the tested behavior. For example, the names TestIncorrectLogin and TestWeakPasswordRegistration could be used to check the correctness of the login and the module’s reaction to a too simple password.

Tests can be located both with the tested code, and in a separate project. Obviously, the main project shouldn’t depend on tests, it doesn’t need to know that someone is testing it. It is considered good practice to separate tests and production code, but there are exceptions – for example, if we need to check the implementation, i.e. the correctness of the work of its private methods of the class. In this case, tests can be placed right inside the code under test (or a friendship relationship between the class under test and the test is used). Usually there is no such need, and only the interface is covered with tests, since it is he who shapes the behavior of the class.

The heyday of ICOs in 2017, which is now often compared to the “dot-com boom”, was followed by a rapid decline in investor interest in this form of fundraising. This is due to the high risks of ICO, because in most countries of the world there is no legal regulation in this area. Investors’ interests are not protected in any way, the legal status of digital assets is not legally defined, and the attitude of regulators remains skeptical. Therefore, ICO as a way to attract investment is increasingly inferior to STO (security token offering).

Security token offering: approaches and risks
In the case of STO, the status of digital assets is determined more precisely, since the tokens being placed are similar in characteristics to securities that have a fairly extensive legal regulation.

Nevertheless, STO is still perceived with a degree of caution today, since no country in the world has a systemic legislative regulation of the placement of security tokens, which would be based on long-term law enforcement practice. But despite the distrust of regulators and market participants in cryptoassets, in some countries they are trying to solve this problem at the state level. After all, national legislation can be brought into line with modern technologies in order to attract new investments into the economy.