QA junior, not easy?

I want to share my little experience at the beginning of Quality Assyrians Engenireeng.
What should a junior tester know? To have an idea of how to describe test scenarios and correctly draw up defects, know what black box testing is, and understand how regression testing differs from functional testing. That is, the junior's tasks, in fact, are only technical in nature (yes, of course, there are no written and oral reports, but there are so few of them that they can be neglected). The younger is interested in knowledge, which is directly related to testing the functional. Understand how the risk differs from the problem and where to launch it, if you have identified the first or encountered a second.
Also, in my opinion, a good tester should be able to read and understand the code. What for? Yes, if only because testers cannot always create test scripts, considering the system a "black box". Moreover, the ability to program and automate is no longer a craft of the elect, but simply an instrument that should and should be used. Hence the conclusion: learn programming languages  (PHP, ruby, python, java, c ++). Possessing them, you can always master the "newfangled" framework and understand how you test and why.
This should work. How much theory has not been read, without practice, it evaporates, is forgotten, not understood.
A good tester is like a samurai sword. First of all, the sword has one mission: the sword must be cut very well, and the tester should test well. Therefore, the tester must understand what testing is, what is his task, and also during the day correctly prioritize their work

Be proactive. Remember the 7 skills of "7 habits of highly effective people"? First, the main thing is to be proactive.