Welcome to the ultimate junior web developer survival guide, part 2! 🎉
If you're new here: this guide is a series of multiple posts where I docu...
For further actions, you may consider blocking this person and/or reporting abuse
Really good retrospectives. It’s valuable advice for engineers at all stages!
Fun fact to share 🤪
I appreciate great engineers. Sometimes I think we should give more credits to self-sufficient engineers ;)
Thank you!
Sounds like a tricky co-worker to deal with, hats off to you for working with engineers like that. :-) I can't imagine how hard it must be.
aha :) yes, jokes aside, we all have areas to improve. great tips in the post!
The last one is always hard for me.
I think that when you feel you are about to solve the problem you have been working on for a few hours, you have already missed a better solution.
It's like if the right solution is in a path you didn't take and that's already behind you. The only way to get there is starting over with all the new knowledge you acquired that will allow you to see the path this time.
Totally agree, thanks for sharing your refreshing take on this!
This doesn't have to be a bad thing. I do this a lot myself, and often don't even mean for it to be the final code. Writing code can be a really good way of exploring a problem because you can test solutions easily and see what works.
The key is to not get too attached to any particular solution; if something doesn't work, start the next iteration.
Section 2 is always hard no matter what field you are in. The more time dedicated to solving a problem the harder it is to let go... much like a dog
I'm proud of my self for being capable of killing anyone's child, even my own. Agh that came out wrong.
Back to the topic, 3rd point is hard for me. Sometimes I spend to much time on solving a problem and fail miserably. Then next day, boom, I solve it in under a hour. Sometimes hitting a 10 minute walk around office can do wonders.
So relatable. I still struggle with it, too. This week I had to make some CSS changes and after literally spending an entire day on it, I still wasn't getting the desired results. I knew for a fact there had to be a better way to implement it. The next day, I took a step back and suddenly had my "Eureka!"-moment, facepalming in disbelief that it took me so many hours to achieve a very simple solution haha!
Great tips!
Thanks for reading!
As a junior developer myself I have problem with all three. Grate article!
Same here, I guess writing them down and sharing them with the community is a way to hold myself accountable and to remind myself not to get stuck on these things :-) Glad you liked it!