
If I were a sysadmin, then I would certainly “practice” in a large hoster (there are also many but a lot of enike machines in banks) or a search engine portal like Yandex, Mail, Rambler or Google at worst :)
A tester needs to learn from the factory (a large outsourcing company) moving from project to project between systems, applications and organizational structures. In the same place, it seems to me, well studies to the programmer. Hard deadlines and “no one cares about your beauty” have a very positive effect on the understanding of what is
needed and what
we would like . In the case of testers and programmers, the “factory” will also serve as a school - now many factories have to invest in training.
It is also extremely cool to try yourself in some kind of government structure to understand that IT is never “our everything”, then in a small, not IT-company, where the same sysadmin is more a doctor-psychologist than a builder-architect.
')
With PM, a clinical case: some are able to do projects, others are not. By and large, the PM doesn’t care what to do and in what structure to work, and here the “factory” can just play a dirty trick on the PM. In real life, PM is often never “king and god” or at least “native father”, as often happens (and often indeed it does!) PM in a factory. Beyond the borders of pure IT, PM is more often a “negotiator” who simultaneously persuades a teenage daughter to get out of the bath and not be offended by “this freak ... (crossed out) boy”, an overgrown son “do not even try to smoke” (read , finally!), wait for his wife with the arrival of his beloved mother and buying a second car for her, and at the same time solving minor problems at work such as launching a new power unit in a seismically dangerous area.
For PM, you probably just have to try to make a couple of projects for yourself: think up an idea, find grandmas (even just borrowing from your parents or putting aside your favorite premium, which you already noticed on a GPS receiver or other gadget - the point is budget constraint), find the performers (certainly with contractors, not friends), check that it didn’t work like in the joke about the “lighthouse and the well” (when the builders built the lighthouse and turned it over at the very beginning), assemble and launch the project and try to convince yourself that oh it was all worth it.
It is possible to build a house as an exercise, for example - this is for extreme sports. That is, to persuade the parents of this case, calculate the money, find builders, find a plot, find out that such a house cannot be built on this plot, find another plot, understand that money has already depreciated by a certain percentage, take a smaller plot, find out that This area will never live, etc. etc. And again to convince yourself that you like this engine. Then try the same with programmers, marketers, customers and other civilian comrades.
By the way, the last exercise, you should try to go through any IT person.
Why am I all this: you first need to try and see how everything happens in the industry and in a madhouse and only then make a decision in which environment you are most comfortable. Otherwise, IT will present many unpleasant surprises.
PS
Diligently I didn’t want to start an article with the words “I am often asked” :)