I love the approach. That's how I got all my IT jobs in the 20 years or so I worked in IT. I got my foot in the door however I could, and then focused on adding as much value as possible in some area, becoming an asset for the company. Of course, this required reading a lot outside my day-to-day, but it wasn't so hard because I just loved IT and it didn't quite feel like work to me.
It's not as important to choose the right stack or framework from the start but becoming proficient and then expanding and pivoting that expertise "on the job" to master some specific area and using that to build a career.
Thanks for the response! I agree that getting in "si o si" is the most important part. As far as the specialization, probably just generally looking at what your ideal employers are looking for and picking something from there is good enough.
I love the approach. That's how I got all my IT jobs in the 20 years or so I worked in IT. I got my foot in the door however I could, and then focused on adding as much value as possible in some area, becoming an asset for the company. Of course, this required reading a lot outside my day-to-day, but it wasn't so hard because I just loved IT and it didn't quite feel like work to me.
It's not as important to choose the right stack or framework from the start but becoming proficient and then expanding and pivoting that expertise "on the job" to master some specific area and using that to build a career.
Thanks for the response! I agree that getting in "si o si" is the most important part. As far as the specialization, probably just generally looking at what your ideal employers are looking for and picking something from there is good enough.