Read "Software engineering" by Ian Sommerville. Any edition (maybe from 6 onwards, though they are slighty different.. pick latest u can get). Maybe skim/skip t

Read "Software engineering" by Ian Sommerville. Any edition (maybe from 6 onwards, though they are slighty different.. pick latest u can get). Maybe skim/skip the (technical) parts u think u know, and read the rest. Most will not make sense initialy.. does not matter, keep reading. u need to get all that "uploaded" in brain in order to be able to grasp it one day. It took me 10 years to be able to skip all the technicals. And another 10+ years to understand why u may ever need the rest.. for judgment etc... Maybe pick some big-enough open-source project in a domain u know well and follow it - how and when they do change what. Dont worry, it does take years to really form your own judgment. btw u will need some philosophy/methodology/human-side too.. there's not many of it in the above book. For more, see the recommended readings on www.svilendobrev.com/rabota/ have fun