Yes, that is correct.
Note that your t object is of an anonymous inner class, which is a subclass of Thread. As an instance of an anonymous inner class, it can execute the methods of the enclosing class. I am assuming myMethod() is a method of the enclosing class.
So, as you see, creating and starting a thread in
Java is very easy. However, achieving successful concurrent operation, in any non-trivial application, is not at all easy.
Suddenly, things are quite different to how they were in your single-threaded program. In single-threaded code, if nothing in the currently-executing method says that object A should change, then object A won't change. In multi-threaded code, some other thread could change object A at any time. So you need to consider when this would cause problems, and use things like synchronized, wait() and notify() to avoid them.