Getting My Ruby Slippers Part 1
When I first started at Theorem, it was obvious what my strengths were. I like to think of myself as a modest, front end super hero ;) My entire team really appreciated the contributions I was making on the FE. I implemented a theme, created a catalog for components, configured code quality tools, added multiple layers of testing, streamlined build processes, started using typed code, and only broke prod a few times in the process. I fixed it too though. I dang near coded myself out of a job. Not really, but I did complete my dedicated front end work leaving gaps in what and where I could contribute. So I made a list of front end tasks to fill these gaps. They were super important items that would have a huge impact on the project. So I did them and they did. There was one problem, the work I did was not approved by our client and did not have sprint value in the terms of points towards our contracted work. I was at a fork (not a git fork) in the road. I could continue to be a front end specialist and continue doing what I do best or I could put my team first and provide a more rounded value to them by helping out on our back end code.
I really enjoy knowing what I am doing and the thought of becoming a rookie at anything is not exactly thrilling.