Being a junior has a lot to do with a state of mind. besides technical skills.
I want to tell you how I changed my “junior” state of mind and how I was able to give value much faster, which translates into a better salary, roles, and opportunities.
I will share practical tips that you can implement starting today.
If you haven’t read it yet, check out
Asking For Help
I often see students and junior developers asking for help by just stating that they have “a problem”.
Communicating in messages can be an important way to avoid interruptions and achieve a flow state, but often, there are too many “noises” over the chat.
In order to avoid interrupting as much as possible, it is important to save time and give as much information as you can.
This way, the people that can help you don’t need to chase you and ask additional questions (or at least, they have fewer).
What to do
- 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐲𝐨𝐮𝐫 𝐩𝐫𝐨𝐛𝐥𝐞𝐦?
- Add the error message
- Explain what is not working
- 𝐖𝐡𝐚𝐭 𝐰𝐚𝐬 𝐬𝐮𝐩𝐩𝐨𝐬𝐞𝐝 𝐭𝐨 𝐡𝐚𝐩𝐩𝐞𝐧?Explain what is the wanted behavior and attach relevant designs or other resources that can help.
- 𝐖𝐡𝐚𝐭 𝐝𝐢𝐝 𝐲𝐨𝐮 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐭𝐫𝐲 𝐭𝐨 𝐝𝐨?This step is usually the one missing. This actually can help the asker think of new ways to solve the issue (“rubber duck debugging”).
This also will save time by avoiding solutions that were already tried.
– – –
– – –
- Who am I, and how did I end up here?I am a software developer and Instructor with extensive experience leading both teams and projects, and over a decade teaching students and training staff.A few years ago, Jonathan (Owner @Solvism) found me a job in a technical position after I moved to the Netherlands. He guided me through the Dutch working culture and got me a great fit. He did this in… wait for it… one day!Since then we kept in touch, and when I had the opportunity to join the team and contribute with my knowledge and experience, I had to jump in! So here I am!My Social