Unfortunately, becoming a real SENIOR in something it’s a huge path, and @lutzhorn said, you’ll have to do a lot of work in real projects, solving real problems and studying a lot. CC basic’s, patterns, architecture, and SO ON.
I disagree with your attitude. Indeed you need to know and experiment lots of topics, but:
- you do not have a road map/ a list with those topics - and this prevents you to estimate how much time you need
- you are gloryfing the subject - and this will likely slow your own progress
It is much easier to become a senior software engineer than to become a software architect. It is much easier to become a software architect than to become the CEO of your company. It is much easier to become the CEO than to become the president of your country, break a record in the olympics or take the Nobel prize. There is nothing glamorous about a senior software engineer, most junior developers will end up seniors some day. Absolutely all senior developers today will become unemployed if they do not update their skills.
Stop selling yourseves short, stop allowing yourselves to be lazy, and stop artificially glamorizing it. This illusion can only hurt you. If you had a list with all the topics and skills you need to be a senior Golang developer - I expect that the average developer needs about 3-7 years to become one.