It's been about 4 months since I officially switched over to full time development from managing the QA team.
On one hand, I feel a little disappointed that I haven't been able to really develop my frontend skills as much as I'd hoped for, or expected I would have by now. I've only worked on a few small bugs on the frontend and a little bit with our old legacy frontend code. I haven't worked in React too much yet, even though I tried starting work on my own for a small work related React project. It turns out when your day job involves a ton of backend code and running integration tests locally, it takes a bit of time to switch to a Docker profile that is meant for frontend. Doing that every day is just not feasible for me.
So while I'm a little less afraid of curly braces, I don't think I'm close to being comfortable with React and Redux just yet, or with frontend systems altogether.
But on the other hand, I'm pretty proud of how far I've come on the rest of the work -- the backe...
I'm starting to find that I end up with a lot of downtime at work -- in between waiting for my Docker profile to build, or for the container to start, or waiting for code review feedback. These minutes don't add up to anything substantial enough to really put toward the next JIRA ticket, and so I usually find myself browsing Slack and catching up on conversations. Not really meaningful.
So I decided to come up with a list of small exercises I can work on while I'm waiting, for whatever it is. Here's my list of resources so far!
Ok so this one is a site for elementary aged children. But it is a ton of fun, the exercises are short and simple, and incredibly adorable. And hey, if they can learn this stuff, so can I! codeclubprojects.or...
One of the problems with being a new developer is that I have so little confidence in my skills, even when I should trust my gut.
My team is currently working on an engineering wide initiative to convert our codebase to a new Permissions model. This week I've had the task of taking a particular scary bit of code and migrating it over.
Today, I was working on a Python integration test failure that didn't make any sense. By all means, this test should have been passing. I spent a couple hours on Wednesday struggling over this code, trying to figure out what it was that I was doing wrong. But I couldn't see anything! Naturally, I figured I must have missed something. I made some mistake, somewhere. I'm new at this, after all. I must have done something wrong.
But after spending 5 hours digging into deep layers of this code, three services away from the code I modified, getting the help of two of my teammates and my manager and then finally an engineer from another team, we f...