Soft Skills Engineering

In this episode, Dave and Jamison answer these questions: Questions What should I expect from a junior develop, and how can I help them grow? A junior developer joined my team of 4 a few months ago. He has learned things at a reasonable speed but it is still hard for him to implement new features without any help or existing code to copy. In past jobs, I usually gave juniors simple, easy tasks, but we don’t have that simple tasks in my current job because we’re working on complicated internal systems. Also other junior developers spent lots of their private time learning. I don’t think this junior has spent any time learning in his private time. I don’t want to ask them to learn in their private time, but I just can’t help feel annoyed about the fact that he still cannot pick up a well-defined task in our backlog and complete it by himself. I think he really needs to take some time learning some basics like networking and some skills like keyboard shortcuts of text editors. I know there is lots to learn. However, sometimes I lose my patience when I have to repeat myself. In addition to lack of knowledge and skills, I feel that he always waits somebody to tell him what to do and explain everything to him. I tried to tell him the whole picture of the project before explain a specific task, but I couldn’t see any improvement. What could I do to help him (or make myself feel better)? I’ve worked with 3 managers in the past 2 years at my first company and all of them seem to have trouble producing results from team meetings and one on ones. More specifically, my managers have mentioned things/events/changes they would plan to do with the team or me and several weeks/months go by and the idea is never mentioned again. At times it felt like maybe it was me that was unable to produce the outcomes of said ideas or that maybe I was some sort of a lost cause. However, my most recent manager doubled the ratio of ideas:results, so I don’t think it’s just me. For my one on ones, we have a long running list of things we talk about and even the trail there doesn’t seem to amount to anything. How do I hold my manager accountable for things they say or plan to do? How do I bring up these conversation on one-on-ones without making it seem like I’m the one managing them?

In this episode, Dave and Jamison answer these questions: Questions How should I deal with the product I am building being called “the worst tool in the domain I’ve ever used”? The product I’m working on is quite old, has many customers, but by no means is a product everyone loves or even talks about. Most of the public feedback I see is negative, with very little praise or even good words about it. Lately, it’s been straining me and affecting my motivation to work on this product, even though otherwise I like working on it, with the great team, good tech stack and so on. Thanks! Hi! I miss going to the gym (because of lockdown) and listening to your podcast while I do cardio! My question: I’m a freelance developer working remotely in a team of other freelancers. This is my first full remote and freelance job setup. Recently, I’ve been feeling like the other developers are “just letting the meter run”, as it takes them a long time to complete tasks (without writing unit tests or documentation), the tickets they work on don’t pass initial QA, they log in late in the day and disappear in the afternoon usually without leaving a slack message or status. Is it understandable to think so negatively about them all the time should I just mind my own business and just manage my feelings? Help appreciated - I have been thinking of leaving this project because of them, which is unfortunate because the company and their product are interesting. Thanks!

In this episode, Dave and Jamison answer these questions: Questions I have a question about ‘title inflation’, where you get promoted faster than your experience would normally suggest for that specific title. If I’ve been a ‘Senior Software Engineer’ for all of a year, and am now getting recruiting offers for Director and VP of Engineering jobs, is it worth interviewing and seeing where it goes? I don’t really see myself at that level, but I… might be able to level up to it quickly! Should I take a remote work offer or find a new job in a new place? I am moving to another country with my husband in 2 months. I am the only frontend developer in the team and my company has been having difficulty hiring people, so my boss asked me if I could work for the company as a remote employee. I am reluctant to the offer because my plan has always been to find a new job so that I can blend in with the local community. Not to mention the 12-hour time difference and lack of new challenges. Sadly, I find it difficult to reject him and leave my colleagues behind. What is a better action to take?

In this episode, Dave and Jamison answer these questions: Questions I work for an all-remote company and I’m about to get promoted. The company says they target a salary increase of 5-10%. Assuming they come to me with an offer on the low-end (5-6%), what’s the best way to go about negotiating a higher raise during promotion? I want to stay at the company and also want the shiny new SENIOR job title, so I feel like I don’t have much leverage in this situation. Any advice is appreciated! Rachel asks, Live coding makes me choke. As soon as someone else is watching, my brain immediately goes to mush and I’m like a chicken with my head cut off. Actually recently I learned it’s not just live coding – it extends to live spreadsheet-making and live cooking as well! I guess I’m not into performing? Anyway, this has come up because it’s impacting my career in real ways. For interviews I offer to do takehomes, which I’m great at, but sometimes I’m told live coding is the standard they apply to all applicants. What’s a non-live coder to do? Show Notes Consumer price index: https://www.bls.gov/news.release/cpi.nr0.htm @Channel Twitter account: https://twitter.com/Channel https://interviewing.io/

In this episode, Dave and Jamison answer these questions: Questions Should I change tech stacks every few years in order to not get pigeonholed? Is it a good idea to stick with a tech stack for as long as I can or should I follow the market trend and try to learn another promising tech and then try switching into that? Would you advise me to be more of a specialist or a generalist early in my career, and what about later when I’m more experienced? I’m a full-stack web developer who’s just starting out my first job (if that matters) I love this show so much, I’m even trying your goto advice - quitting my job! But not untill I’ve got another lined up so shhh about it already. In the mean time, I work for a huge agency as a senior(ish) developer and have recently started work with a new team. However, they have issues: no one turns on their camera for video calls, which I’m ok with, but it makes the next bit worse somehow - most say the absolute minimum in response to any questions and offer no opionions / thoughts / ideas. It makes things like sprint retro meetings very awkward. We have a scrum master running our meetings who is clearly struggling to engage the team, I try to hold off to let any of the others answer questions but I always seem to end up picking up the slack. I’ve even started timing how long I’ll let the slience endure before jumping in to answer, I’m now waiting 15 seconds. Have you come accross this before? How can I get people to engage more?

In this episode, Dave and Jamison answer these questions: Questions I have a weekly one-on-one with my manager. What should I talk about in them? Things like feedback and career goals become old and repetitive real soon, and I end up discussing current work items. I understand that a one-on-one is my time to ask questions and don’t want it to be a longer daily-standup. My front-end team mates are in a power struggle with my back-end team mates and my design team mates. They’re intentionally making technical decisions that artificially constrain the choices of other teams. For example, design wants a certain interaction for a new feature, and my team says “nope, it can’t work that way, cause the components we built don’t allow that”. Or, they make tickets for the back-end team as in “endpoints have to work this or that way, because our components assume that structure”. This often seems detrimental and confusing to other teams. When I push back against my team they are angry. When I defend my team other people are angry. When I try to strike a compromise I feel gross because I usually think my team is wrong. I’ve tried talking with other teams and managers about the problem. I feel gross about that too because I don’t want to point fingers or throw my team mates under the bus. Where should I even start?

In this episode, Dave and Jamison answer these questions: Questions Hi Mr.Smith and Mr.Dance, I’m a software engineer at a big software company. I recently learned to self-evaluate and found that I’m really bad at being finger pointed. I am normally an easy-going team player with an open mind. I accept that I can be flawed sometimes, and I would never blame anyone. But whenever someone points their finger at me and says “this bug is caused by YOU!” or more commonly “this bug is caused by YOUR systems!” (sometimes with facepalm emojis or this emoji 🤷), I suddenly become super defensive and frantically try to find counter evidence to prove that it is indeed THEIR system that is at fault, or at least some OTHER systems that is at fault, but definitely NOT MINE. After I cool down for a few days, I regain my composure and realize that what I have done was wrong and not useful to the discussion. This is specifically in the context of informal issue debugging between teams, not strictly a blameless postmortem meeting. I think blaming others is not a good behavior and makes the workplace toxic and unproductive. I would like to improve myself (and others). Any suggestions and recommendations? First of all I have to say a big THANK YOU to the work you’ve been developing, it’s helping me a lot to set my expectations and pave my career path. So, to the question… I’m currently working for a large Brazilian fintech and I’m starting to get a little bit annoyed by the lack of acknowledgement. I’ve already made it clear to my managers a couple of times and I always received great feedbacks and always performed “above the expectations” for my level. But in the last 1:1 we had I was a little bit more insistent about it and the explanation they gave me was “we know that our developers are above the average, we know that a Junior here can easily get Mid-level or even Senior in other companies, but we want to be a tech reference in the country and we don’t want to spoil the devs by promoting them a couple of times in the same year”. I understand this ambition but it got me a little bit frustrated. Of course I don’t want to be a mercenary nor a mediocre developer, but if this is the objective they’re aiming they should at least pay a competitive salary. This conversation really demotivated me, it seems to me they just want a high specialized work-force for a cheap price. I really appreciate everything I’m able to learn inside the company, for sure everyone is above average and being there is like being in school and it’s been really cool. But I’m starting to question if this “trade-off” of low pay and high learning makes sense once you’re already in the Mid-level corporate world. I’m pretty sure I can double my salary in the next month if I wanted to - a couple o recruiters contacted me in linkedin and I also made some interviews -, but this “tech reference and always learning” thing keeps bothering me and I wonder how much of it really makes a difference in the long run.

In this episode, Dave and Jamison answer these questions: Questions I’m feeling bored and disengaged with my job lately, but I’m pretty sure it’s one of the best jobs I can find: my manager and teammate are great, my compensation is very high for my area, worklife balance/benefits etc are excellent, and the mission and product the company make are awesome and help the world! On top of all that I think the work is technically interesting! But still I’m bored and disengaged :( I can’t tell if I’m just burned out from the pandemic and this is how it’s manifesting, or if I just have a serious case of “the grass is always greener” and now that I’ve been on this team for 2 years I’m ready just for a change of scenery. I want to fall back in love with this job, but how can I do that? Do you have any advice? Changing teams isn’t a great fit as this is a small office for the company in a ““satellite”” site, with only one other team that I’m not super interested in. I could of course take the patented advice and find a new job that might be equally great, but what else can I do? Listener Very Verbose asks, Love the show! I’m rapidly working my way through the backlog and dread the day that I reach the end and have to wait a whole week for the next one! :) Whenever I write a message to a coworker I tend to start with a huge wall of text, then revise it down to something smaller and hit send. I do this with emails, slack messages, code review feedback, you name it. Even this question I’ve re-written a few times! I feel like I’m over-thinking things, and trying to make sure there is no misunderstanding in what I’ve written. For example, a relatively small piece of feedback for a code review might be re-written many times, because I’m concerned that I will come across as overly negative or condescending if I just send through my first draft. Often, the feedback is positive and they agree with the points that I’ve raised. But they’re only seeing 2 points, when I probably started with 10 and deleted 8 of them that I later deemed to be ‘too nitpicky’ before sending it through! Naturally, all of this takes time and I’m often wasting more than 20 mins, only to end up sending 2-3 sentences at the end of it. Do you have any tips for helping me get to the point, so that I can be more productive and move on with other work? Do I just need to care less about what they think of me? Should I just skim over the code, say “LGTM”, and suppress the fear that I may have just approved a critical bug to go to production? Appreciate any advice you can give. Unfortunately, I don’t think inventing a time machine to go back 18 minutes after spending 20 minutes writing a message is a reasonable option :) It would take me several decades to be happy with the time machine before I turn it on!

In this episode, Dave and Jamison answer these questions: Questions Hello!! This is maybe the opposite of a problem, but I’ve found myself stuck - how do you navigate too much interest from outside parties? I work in a pretty niche subsection of software dev, so I field a lot of job offers/recruitment when people start to put together a new team. These are usually coming from managers/people I would be working with directly (and admire!) rather than recruiters. Generally the opportunities are something I could see myself doing one day, but I’m perfectly content in my role as-is for the time being. Where’s the line between expressing interest in future opportunities (emphasis on future) without stringing people along? How many “catch up” conversations are reasonable before it shifts from maintaining a relationship to active recruiting? Apologies if this comes across as a humble brag but I’m getting overwhelmed. Love the show, you rock 🤘 I recently started a new position at a startup after being recruited by one of their senior leaders. Being a startup the company has had its ups and downs, including some layoffs within the last year. I am really loving the company so far, the people, the culture. They really seem to care about correcting past mistakes and listening to feedback from everyone. There is still a good amount of turnover among engineers and engineering managers. I’m sure some turnover is normal especially at startup. But at what point does it really become something I need to be concerned about? What questions should/can I ask to help me get a better picture of what is going on? Is there anything specific I should look out for that might be my cue to start creating a backup plan?

In this episode, Dave and Jamison answer these questions: Questions Hello, I have been working as a software developer for 10+ years now and recently took a job at a non-technical company. I was recruited to craft a web app for this company and thought they had an idea of what it means and the changes it may require. I am the only developer on the project. I feel like, either I’m not communicating well/at all, or they just simply don’t care about the work they recruited me for. I don’t have a good work/life balance since I’m always anxious when I receive an email from the company fearing someone will complain about the quality of my software. I feel isolated and unable to show how my work positively impacts the company Since I know my work is not perfect, I feel like I should not complain at all and just make my software bug-free. I’m doubting my abilities and starting to think I actually don’t know anything about Software Engineering. Because the company is non-technical, do I have the right to say that my work is that essential? What should I do so I don’t feel like crap every morning before going to work? In your last episode, you brought up a listener question about a developer of eight years accepting a senior developer position. I’m in a similar boat, but with far less experience. How much less? Well I’ve worked as a developer only for THREE. This is by no means a flex, but I’m kind of worried that I’m in over my head. There was little due diligence on my new supervisor’s side, so my trepidation is that I’ll be two/three months into my new job and they’ll look at my perf and see “this kid is not a senior at all”. I know, the classic imposter syndrome. I’ve been straight forward with my new supervisor about my experience level—or lack thereof—and they seemed not too worried about it. Do you guys have any advice for me going into this? What can I do to maximise this opportunity I’ve been given this early in my career? Love the show!