So, I’ve been keeping people apprised of my new web dev job and what I’ve learned. I’ve did one at one month. I’ll do one more for the three month mark. I’ve also decided to write a master “what I think you should do to try to get a job” document and that will probably be up some time next week or so.
So, things are still going pretty well. They’re officially hiring me (some of you may remember that I had to do the first three months as a contractor because of some, errr, disagreements about what is legal in CA but not in AR). And they’re giving me a slight raise, so I guess I’m doing OK. I’m certainly not the star of the dev team, but considering my education/experience and where I am in the hierarchy, they seem pretty pleased.
I guess there isn’t much to add over my previous two posts.
Testing. I guess the theme this time would have to be testing. They’ve always encouraged unit tests but instituted a rule that any PR must have 80% coverage for any file that it touched. Unfortunately, another fairly new person and I were working together on something that touched a lot of files so we both had to spend the next week writing Jest tests. One 500 line file - we added three lines but then had to do coverage for the whole file. Holy crap, I had to learn fast. In the end I got fairly decent at it. Or, as I like to say, “I am now and expert at remedial Jest testing.” The scary thing is that some of the other newbs have started to come to me for advice on testing. Every now and then I’ll even get asked a question by one of the more experienced guys. I guess the hard work paid off.
Teamwork and Communication. Yes, those soft skills that people complain about? They’re important. One of the things I love about this team is how well everyone works together and communicates. I’m glad I’m a part of that.
Work Life Balance. I’ve been doing 8-10 hour days at work and often 2-4 hours at home. It’s taken its tole. I got a week off this holiday so that’s nice, but it’s time to back off a little. Being well rested makes a difference. And I have to make time to get to the gym. And eat better.
Frustration. I recently heard someone describing being a developer as being “constantly frustrated”. Yup. That’s a big part of it. We like to think that eventually we’ll just be typing stream of consciousness code, smiling, with bluebirds chirping away on our shoulders. In reality, there is a lot of time just figuring out how to get something to work, getting frustrated. Obviously it happens less as you get better, but if you’re coding anything with doing, you’re going to have times of frustration. I need to learn to take it in stride.
Side Projects. I need to start learning the backend here. I know Node/Express/Mongo, but they’re Java/MySQL. Oh well, it’s an opportunity to learn something new. Just as soon as I understand sagas a little better… I also need to build my wife a web page. Cool.
Oh well, that’s about it. I really am enjoying the job and the people. And I’m amazed that they pay me this much money to basically come in and solve puzzles all day.
I hope you all find your job soon. And if not, don’t give up. I was starting to get frustrated. My wife was starting to give me the “Really?!? Are we ready to admit that this was a deadend idea?” look. And then I got it. And FCC was a big part of it. And all of you.