Returning to coding
Omar Lozada
Jul 01, 2017
I joined a company as a Software Engineer (Could it be Boiling frog theory?). Through the course of the project I was involved in, I also learned to take on the hat of SysAdmin(Operations).
Near the end of the project, I was approached informed that I should focus on being a SysAdmin instead because "I am good at that".
Now since, I didn't had any further discussions with this I'm assuming that I somehow assumed that I came short on their expectations as a Software Engineer.
And somehow thought that it would be better than to be fired.
I guess fast-forward now. I became hungry again, missed coding.
Reflecting on why I didn't continue coding. I could attribute to a feeling of failure, and not being good enough compared to my colleagues. Impostor syndrome?
Today, I half-way through my commitment on #100DayOfCode.
Anyone had similar career/life experience?
I haven't had a similar experience (or much career experience at all), but I definitely know what it's like going back to coding. When I was a teacher assistant for my coding bootcamp, I did a lot of teaching and not a lot of coding. I realized how much I missed coding when I started doing it again, and that was a big signal to keep looking for a coding job.
If it's realistic to find a good coding job where you live, I think it's worth pursuing. I wanted to be a programmer, and I kind of wavered a bit when I got my TA job. I'm really glad I pushed through because I got that programming job.
Hope my two cents help! :)