Senior vs Junior

Petr Zaparka — Mon, 07 Oct 2024 13:27:19 +0000

One of the ways how you can tell when you are talking to a junior developer is the communication level.

I spend 20 minutes on a call with someone who should be able to help me with a problem that is miles outside of my knowledge level.

My approach was to describe the situation. How I got to the point I am now. Where I'm coming from and what I need at the end.
The other person didn't ask any questions just look at things I send him. I could tell he was out of his knowledge level, too, which is fine. But what I was expecting him to do was to try to propose solutions or get someone with more knowledge. Neither happened.

He was afraid to say I don't know.

I am generalising here a lot. Not every junior is this way. But the sad fact is that most of them are. If you think there is even a chance you might have a similar problem and would like to help with that. DM me please I can help.

Happy coding.

Do you have a system in place?

Petr Zaparka — Thu, 22 Aug 2024 14:39:23 +0000

Every time you work on "one-off code" without a system in place, you are wasting your time.

I do things differently.
I have a system in place. Whenever I pick up a "one-off" task like an exporting script for stakeholders, I will save the code I wrote. The next time, there is another "one-off", so I modify the code and save it again. This saved me tons of time over the years.

Do you have a similar system in place?

DEV Community: Petr Zaparka

Senior vs Junior

Do you have a system in place?