Put the important things in front, and look at the windows core programming or unix programming immediately after returning home at night, which will help you sleep.
I have become a full-time employee, and all three tasks during the probationary period have been completed. Of the three new features in this department, I contributed 2. I feel like I'm messing with my head. The leader said that the rendering part I wrote surpassed domestic bidding companies, but it was still not as good as foreign ones. Actually, I just added dynamic alpha on top of the color band, lol. The material has not been added yet.
From the current point of view, it is relatively stable. The leader said that as long as he does a good job, he can get a salary increase every year, and he has never been in arrears.
Therefore, it seems that learning should be combined with work.
Since it is self-studying is learning, and then using the learning results in work, it can be considered as paid learning.
Specifically, one master and multiple slaves are more efficient. If you have a master, you will not deviate from the direction; if you have a vice, you can learn in tomato style without being boring or tired. For example, a 10-minute video tutorial, or a case, or a function.
In this way, you can also use every 10 minutes instead of worrying about what to do in the next hour.
Learn what you should learn in the plan, and accumulate it over time before you can actually apply it in your work.
According to the current situation, there are three plans, which can be switched at any time according to the actual situation.
Option A: rendering-based
1. According to learn opengl, type it again, including the pbr content inside. I only saw it before.
2. According to the PBR video tutorial I bought, make a pbr renderer from scratch.
3. Make the pbr of filament
4. Make the pbr of ue one time
Of course, there are also "Physical Rendering - From Theory to Realization" and dx11 (if you have time to download dx12), you should choose the opportunity to do it.
Plan B: osg/osgEarth is the main
1, familiar with the company code is the main
2 when going to work, and osg/osgEarth video tutorials are done when off work
3, and the longest frame of osg is debugged again.
4. Design the 3D digital earth engine.
5. Continue to debug the osgEarth source code.
Of course, if you have time, you have to type all the examples that come with osg/osgEarth. The book is superficial after all. If you have time, copy the code of osg/osgearth again.
Option C: UE is the mainstay in spare time. I don’t leave the company until 8:00 p.m., so the work content is enough during working hours. Engage in UE after get off work. Even if it doesn't work, there are many ways to change jobs or change jobs. Or simply learn to play independent games to reduce work pressure. Put it on Steam or Unreal Mall to increase popularity. (Of course, learn to understand first)
Plan D: Simultaneously
, for example, from Monday to Friday, conduct five kinds of video tutorials:
1, osg/osgearth
2, pbr a series of shder
3, ue
4, socket
5, computational geometry,
Saturday and Sunday at the same time.