In this episode, Dave and Jamison answer these questions:

1. On Episode 66 you attempted to answer my question: ‘How bad can a Junior Front End Developer be?’ Well, I’m now 4 months into my new job as a Junior Front End Developer and it turns out, they can be pretty bad!

   I’m in this junior role I feel overqualified for. My peers rate me as a solid mid-level, and I’ve started to realize that I’m not really a “junior”. I think this can all be attributed to learning from really good devs at my last company. My best friend is a Senior JS Contractor (legend) and I talk to him about code and best practices everyday.

   Question: Would you ever hire someone at a mid-level role even if they only had 6 months of profressional experience? i.e. how much weight do you put on the CV?

   I love you guys, listened to every podcast!

2. Thank you so much for the show, I’ve been binge listening to old episodes ever since a friend of mine suggested it. Your excellent, and often comedic, advice has been getting me through the work day and I really appreciate it! Onward to the question!

   One of the members on my team, who is more senior than me, often does poor work, and the rest of the team picks up the slack to redo the work, pushing out deadlines we would have otherwise met. I know better than to vent about this at work even though it is very frustrating, however now I’m in a bit of a predicament. Part of our annual review process requires us to provide feedback on each of the members of our team which is not anonymous. The feedback is used to make decisions about raises and promotions. This individual has mentioned that they expect a promotion to a team lead position in this upcoming review cycle, which makes me quite nervous. Should I be honest in my review and mention my concerns or should I take the much more comfortable route that will also protect relationships on my team of pretending everything is fine.

This is a re-broadcast of episode 73 from August 2017. We’ll be back next week with a new episode!

In this episode, Dave and Jamison answer these questions:

1. A developer on my team has been rewriting my code under the guise of “code cleanup” without saying anything to me. Is this normal? What should I do?
2. How do you deal with co-workers who over-explain unimportant issues?

In this episode, Dave and Jamison answer these questions:

1. Shan writes:

   “Awesome podcast! I’ve used your advice to better communicate with my employers which has been super helpful.

   I recently was working as an intern at a company where I did quite a bit of significant work. I left to pursue a Master’s in CS. I set the expectation that I would be available for questions, but not bug fixes during at least the beginning part of grad school. The company said that was totally fine and they would take any amount of work I could give them.

   I’ve noticed some bugs that have to do with what I was working on. I feel really bad for my team having to work on those bugs while I’m not. It is getting to the point that it is distracting me during the day as I see emails or Slack messages about them. I want to help them, but I just don’t have the time. I am also worried that the reputation I built up of being a solid engineer is damaged.

   Should I apologize to my teammates that have to work on my now legacy code?

   I have this feeling of having abandoned my team. Any thoughts on how to mitigate those feelings?

2. I work as software engineer at a ~10 person software agency. During my last review my manager rejected my salary raise proposal arguing that I reached the top level for my current position. He said to get a raise, I would have to act as project manager to get commissions for new projects I acquire. I feel conflicted, since even though I like the idea of upping my game, I do not know much about handling this kind of situations with clients. What is your recommendation for developers getting out of the world of code and into the world of people? Bonus question: Ideas on how to get new projects from clients?