Soft Skills Engineering

In this episode, Dave and Jamison answer these questions: I work in a flat organization. There aren’t really any titles, and very few managers. There is no common “climbing the ladder” here. What are options for career growth that will help me feel confident that I am progressing in my career? How do references work? I’m starting to look for a new job which means potential employers are going to be asking me for references. I’m not ready to let my boss know I’m thinking of leaving and aside from my current coworkers I don’t know who would attest to my ability as an engineer. I work for a small company (under 50) in an even smaller firmware department (about half a dozen). What am I to do?

In this episode, Dave and Jamison answer these questions: Hi guys! I was faced with quite a dilemma recently. A few days ago one of my co-workers said he was sick and worked from home. But the next day he came to office, constantly sneezing and looking terrible, and for some reason finished the day in the office. The same happened the day after that. I didn’t want to be rude and I felt for this guy, but I didn’t want to get sick either cause I have some important tasks this week. What could have I done? I could not just tell him “go home you fool, you’re contagious!” I could say “Hey! I noticed you’re not feeling very well, why don’t you come to the manager and ask to work from home this week?” But I didn’t have the guts to do this. Besides, what if he couldn’t work from home for some reason? I solved this by lying to my manager that I’m ill too, and worked from home. What is the best solution here? Hi, I recently went through my company’s annual review process. The review went pretty much as expected, with things that I was doing well and things that I could improve on. However, I received some negative feedback which I disagreed with. I asked for additional detail and examples of this, but neither my manager, or his manager (our site lead) could give me any concrete examples. After some further discussion they agreed to remove the comment from my review, but I’m now left wondering why this feedback was added in the first place if there were no examples they could give me. Their explanation for this was that it was feedback for our team, am I wrong or is an annual performance review the wrong place for that kind of feedback? Should I be concerned that they actually do have feedback for me, but were unwilling to do so given my reaction? Is this enough of a red flag to maybe consider looking for a new job?

In this episode, Dave and Jamison answer these questions: How do I deal with the manager on my team who is both not very technical and positions himself as the “boss” spending almost no time with the team (except dragging everyone into more and more meetings! 😡) . My manager upsets and demotivates the team but not upper management and is clearly trying to climb the career ladders as fast as possible. Obviously everyone wants the team to succeed but the friction is growing. Some team members already left with (maybe too subtle) hints at the problem. Should one stage a coup and take over? Silently manipulate people to go to into “the right” direction? Switch teams/jobs and see it burn from the sidelines 🍿? While testing my system at work, I was shocked how little security there was. Two issues exposed the entire system’s data by just changing the query string. Also every API call had no backend check on the user making the call. These are just two examples of many. This is at a gigantic multi billion dollar institution handling hundreds of thousands of people’s data, some of it incredibly sensitive. This fact will be known on my resume. This leads to my question: I am looking for a new job now, and wondering how much detail about these security issues is appropriate to share on a resume? I feel this helps me stand out as a newer dev, but would this be frowned upon by prospective employers that may worry I might overshare their own security issues? Thanks for all your help!

In this episode, Dave and Jamison answer these questions along with special guest Jonathan Cutrell:: I’ve been job hunting while employed (gasp), and I have a number of opportunities that have advanced to the in-person interview. Most of the requests I’ve seen have said that they’ll be 4-5 hours in the office (which seems fairly typical). The problem is that I don’t have unlimited vacation, and I feel dishonest taking so many days off. How can I navigate new opportunities without disrespecting them, or completely failing in my current responsibilities? Hey guys, great show (though I think, as with all shows, it could probably use more discussion of badgers [yes, I said badgers!]). I’m about to start a new job (I took the time-honored and hallowed show advice, though I’m leaving on great terms with my old job) and will be coming in as that fanciest of newly-invented titles in software, Staff Software Engineer. This is the only third time I’ve started a new job [not counting odd jobs in high school and college], and I’ve never stepped into a leadership role before when starting. What are the most helpful things you’ve done or seen other engineers do when joining a team in a technical leadership role? Thanks! Follow Jonathan Cutrell on Twitter @jcutrell and subscribe to the Developer Tea podcast: https://spec.fm/podcasts/developer-tea.

In this episode, Dave and Jamison answer these questions: I have noticed one of my coworkers, a fellow senior software engineer, often interrupts people during their meetings with his comments and thoughts. While I’m not against voicing opinions during a meeting, he does it so often that he takes over meetings. Some of his points are off-topic. He’ll cut off the presenter or another colleague (who displayed good etiquette) mid-sentence, not letting them finish their thought and derailing the flow of the meeting. In our last meeting I tried to quickly respond to his interjections rather than let him finish so we can keep the meeting moving. I thought he would take the hint to think a little more before interrupting. Ineffective so far. I think next time I will recommend that all questions and concerns be held to the end so we can get through all the meaningful content before letting him speak. Any other suggestions on how to deal with people like this? Hi guys! I have a question about setting limits to your work. I hear that its a common practice among developers to set restrictions to their work like turning off slack notifications when at home, not staying late at work, etc. This seems like a healthy approach, and I like it. But I can’t bring myself to do it. I’m a successful developer, I love my job, and I love the work communication in our chat. I have no problems struggling through the workday, but I have problems not falling into work in my free time. I have a lot of friends, a lot of hobbies, I’m definitely not bored outside of work. But still I always have this inner desire to open and read the workchat when I have a free minute, or finish an interesting feature in the evening instead of reading an interesting book. I can’t say it makes me unhappy in some way or affects my private life - I still will go and see a friend if I’m invited and still will attend my yoga class on a normal schedule - but this ““desire”” distracts me sometimes and that’s not normal either. Am I right?

In this episode, Dave and Jamison answer these questions: 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! 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: 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? How do you deal with co-workers who over-explain unimportant issues?

In this episode, Dave and Jamison answer these questions: 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? 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?

In this episode, Dave and Jamison answer these questions: My boss is fairly new to management and has recently made some decisions which had a negative impact on my squad. While this was annoying, it didn’t cause any major problems - we worked around the issues and recovered and everyone including my boss learned from the experience. However, my squad has started criticising him pretty harshly in standups and retrospectives and it’s making me really uncomfortable. Often their criticisms are for things that he has very little influence over and it seems like they’re scapegoating him for the general dysfunction within the company. He’s a nice guy who is trying his best and I wouldn’t want him to think I’m taking part in these badmouthing sessions if word ever gets back to him. He doesn’t manage any of the other squad members. What should I do? I work at a big software company and sit in a room with about 20 people. Not all of them are on my project, and lots of them are REALLY loud. You know like in a stock market or something. I use headphones to listen to your podcast (well, not only yours to be honest) but usually that’s no help. I turn on music - still can hear every word. These guys somehow think it’s ok to discuss their work in our room instead of a meeting room (which we have plenty of), and do it loudly, while me and my team always go somewhere else to talk. I talked to these guys a couple of times about it. They laughed and said they would try to be a little bit more quiet, but forgot this promise 5 minutes later. How else can I handle this situation? I have good relationships with all of them (probably that’s why I had not been taken seriously), but I don’t want to lose them.

When to ask for a raise after exceeding expectations at work; navigating a generational gap in a team of young, dedicated learners; challenges of keeping up with the evolving JavaScript landscape; adopting new technologies and the concept of no bugs-driven development; thriving in a fast-paced environment and learning by explaining things to others.