This content originally appeared on DEV Community and was authored by Domnic Omondi
Being a junior developer is tough. You’re new to the game, trying to navigate the world of coding and development while also trying to impress your employer with your skills and knowledge. But what happens when you’re sucked from a remote job only 2 weeks after starting the job? It can be devastating, especially when the reasons for getting sucked seem petty or insignificant.
In my case, I was sucked from my first remote job as a junior developer after only 2 weeks. The reasons given to me were that my commit messages were poor, I was using a line spacing of 2 instead of 4 and I took long to deliver a working login page which was more of a backend problem than mine because the API endpoint was not working. I was confused at first and hurt by these reasons, I tried to ask for a second chance but it was too late because my replacement was already on standby. I was new to this job and this was my first time working remotely. I didn't realize that these small things could cause such a big problem.
As time passed, I began to see why my employer was unhappy with my performance and I knew it was over for me the day I received a long voice note from my boss. My commit messages were indeed long and poor, it made it difficult for my team to understand what I was working on or what changes I had made. This made it challenging for them to review my work and offer feedback. On top of that, using a line spacing of 2 instead of 4 may have seemed harmless, but it made my code difficult to read, edit and merge with the main branch. My last two commits before getting sucked were much better and I thought I was progressing well but maybe it was already too late to make things right
As a junior developer who was still learning how to communicate my work effectively and present my code in a readable format. But my employer and seniors had a responsibility to share feedback on areas where I could improve, even if it seems small or insignificant.
Getting sucked from a remote job as a junior developer taught me valuable lessons about the importance of attention to detail, collaboration, and communication which was my biggest problem, I didn't know how to effectively express myself and explain what was going on or what I was up to. It also taught me the value of taking ownership of my mistakes and working hard to correct them.
In conclusion, being sucked from a remote job as a junior developer and worse after only 2 weeks can be discouraging, but it's important to take the situation as a learning experience. Be keen on small details, and work on your soft skills as much as your hard skills, soft skills like effective communication, and collaboration with your team ensure that expectations are met. In the end, it will be worth the effort to become a better developer and excel in your career.
This content originally appeared on DEV Community and was authored by Domnic Omondi
Domnic Omondi | Sciencx (2023-04-25T16:19:13+00:00) Why I got sucked only 2 weeks into my junior developer job and what I learned.. Retrieved from https://www.scien.cx/2023/04/25/why-i-got-sucked-only-2-weeks-into-my-junior-developer-job-and-what-i-learned/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.