I have to say that since starting I’ve had a lot less support than I was expecting and I’ll be given something to do but very sparse direction. I’ll go away and do my best and usually be told that based on the little guidance I have done good but maybe we could do it this way or that way, which is great as that’s how we learn right?
Also, preface saying that I’m working on a Typescript React app alone as the others have other projects.
So queue today. I’ve got a todo list of questions about my implementation and things I could do better, which they like my diligence of keeping track. Well I was working on a component and like an idiot I hard coded a lot of the data that is subject to change if say they add a new let’s say PetType. So the SE comes over, tears my code to shreds and like a wizard makes it work even better with only dynamic use of data.
I don’t mind the tearing my code to shreds as again it’s a learning experience but my self esteem has dropped off a cliff.
This is where a team coding standard, naming standard, and formatting standard really helps.
You’re always going to receive feedback on your code. Part of what makes coding fun is that there are a million different ways to make something that works and most people are going to think their way works best. More experienced engineers most likely do know a better way to do it, so take their suggestions, figure out why it’s better, and apply those principles to all of your code. But sometimes junior level people come up with great ideas. It’s important that you know why you made certain decisions, and to be able to defend those decisions. After considering recommendations, consider if they are actually better, and if you think they aren’t, then have a conversation about that.
If you don’t have experience working with dynamic data then it’s normal that you just forgot that you needed props instead of text (or whatever your situation was). Now that you made that mistake, you’ll probably never make it again.
Don’t be too hard on yourself. There is too much for any single person to remember. I’ve been doing this for 20 years and I still have my head in the docs several times a day. On that note, make frequent and liberal use of the documentation. It’s okay to forget stuff you haven’t done in awhile. Yesterday I forgot what the freaking span element was called and I’ve made spans a hundred million times before. It just poofed out of my memory. What’s not okay is not knowing how to find the information you have forgotten. Again, learn the docs and use them religiously.
Always remember that there are two states to every programmer. That link is a funny but accurate reminder of something we all experience…
Good luck. We’re all counting on you.
I do enjoy the feedback and the more negative the better imo as that is a learning experience, plus I can’t handle praise.
I can relate to forgetting things I’ve done before but I agree, we work in this field as we like to solve problems and we are arrogant enough to think (know) we can just Google the answers to everything.
Speaking of docs, I got called out for Googling (with the SE) how to show the long day name using Moment. It is ‘dddd’. I was Googling and just clicking stackoverflow kinda out of habit until she said slow down, go back, let’s go to the moment docs and click on formats. We found the answer much quicker so I need to get in the habit of checking the official docs first.
Also, that meme is perfect. Self esteem goes up and down in this job. I think a lot of my worries will be here until probation is over and that I am safe.
Imposter syndrome isn’t fun.
Make use of ChatGPT if your employer allows it. It Is actually amazing. I’ve been using it for about 3 weeks now and I’m probably 400% faster. GitHub Copilot is pretty great too.