412 episodes

It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.

Soft Skills Engineering Jamison Dance and Dave Smith

    • Technology

It takes more than great code to be a great engineer. Soft Skills Engineering is a weekly advice podcast for software developers about the non-technical stuff that goes into being a great software developer.

    Episode 411: We have a secret org chart and I'm a big fish in a little pond

    Episode 411: We have a secret org chart and I'm a big fish in a little pond

    In this episode, Dave and Jamison answer these questions:




    Hi :-)


    I work as a Senior Data Scientist, and about half a year ago I joined a start up that was founded by a large corporation. And while this job comes with the perks of a bigger company - like good salary, paid overtime, … , - it also comes with its organizational overhead and politics:


    We are only about 30 people but already a quarter of us acts as managers. I write “act” because the official org chart is flat (with the CEO at the top and the rest of us directly underneath). The unofficial org chart is hidden and depending on who you speak with, you get their view point on how roles and responsibilities should look like.
    As a result, I’m left with putting together the pieces to build a picture that somewhat resembles the truth. So far, I’ve concluded that we have multiple (!) management layers, that there’s a power war taking place in the middle management layer, and that you can make up your own titles that mean NOTHING, because no one has any official, disciplinary authority over any one, but that are still to be respected! What a great opportunity for job crafting :-D


    To make things worse, I prefer and come from organizations that have a truly flat hierarchy. For example, I’m used to step outside of my role should the situation require it (like doing some managerial tasks, supporting sales, …) and that I can speak my mind, irrespective of what the title of the person is who I’m talking to. While this was beneficial in my previous positions, this does not work well here! And while I understand that adapting my behavior would be more in line with the company culture, I find this extremely difficult. On the one hand, because of the hidden org chart, on the other because we are all fully remote and I rarely see people from other teams.


    To avoid accidentally stepping on anyone’s toes, my current solution is to stick my head in the sand and focus on my coding. However, this leaves me disgruntled because I feel like I’m not being myself, and that I’m withholding a viable part of my skill set: to see the bigger picture and serve the company as a whole instead of just implementing tickets.


    Please help, I do not understand how this company works :’-D How would you navigate the situation? I don’t want to quit because, individually, my coworkers are super nice, and the work is really interesting.


    All the best 3



    Hi,


    I’ve been working at a well-known multinational company for a few years now. The entire time I’ve been here, the company has been well behind what I believe to be industry standards, but they have some great perks, which means it’s been really easy for me to create “wow” ideas (just do the same thing that everybody else has been doing for a few years).


    At the risk of sounding full of myself, I’ve noticed that I’ve created a critical person risk. There’s not only no push for me to train others in my work; things I thought were standard knowledge is entirely new to this team! I don’t want to become the trainer for a team that has no desire to learn new skills, and I don’t want to dumb down my work either. Is there a happy medium where I can build exciting new things and not create an absolute craphow when I leave? Should I even care about it since no one else does?




    Show Notes

    The Tyranny Of Structurelessness - https://www.jofreeman.com/joreen/tyranny.htm

    • 35 min
    Episode 410: Guaranteed cost-of-living raises and my manager doesn't like me

    Episode 410: Guaranteed cost-of-living raises and my manager doesn't like me

    In this episode, Dave and Jamison answer these questions:




    Hi Soft Skills!


    I’m writing to you as I look forlornly at my paycheck, unchanged for the last year and a half, and wonder if I’ll ever see market rate again. While I prepare my leetcoding skills for the trek that is your classic Soft Skills Adventure (quitting), I think about future interviews and wonder: how common is it to have something like a COLA clause in your employment agreement? Something like “Oliver will receive a raise of no less than the current CPI% per year”. Are there other ways to mitigate this, other than joining a company with more people and less greed? I don’t think I should have to beg for COLA-s with good reviews in hand. In fact I think those reviews call for raises!


    Thanks for bringing more joy to my life :),


    Mr Twist


    P.S. I am grateful I’m not paid in porridge and any reference to Oliver Twist isn’t to suggest Tech Salaries aren’t livable wages.



    Mr. Peanut Butter asks,


    I’m a senior IC at a small startup and I’m struggling to get along with an engineering manager. M has a say in my promotion and has already said no once, which was pretty painful considering the time and energy I’d spent helping their team succeed. I think there are two headwinds to M changing their mind 1) I’m FE-focused, and M’s conception of FE work is dated and simplistic. 2) M can be a bit of a blowhard. Said generously: M is a top-down thinker, quick to make conclusions, process-focused, and loves discussing architecture and design patterns. In contrast, I’m a bottoms-up thinker, pragmatic, plain-spoken, slow to make conclusions.
    M and I meet regularly to discuss cross-team matters, and it is my least favorite meeting of the week, even weeks that include dentist appointments. M sometimes devolves into lecturing me about software fundamentals (which I know at least a well as they do). I know from experience that there’s an M at nearly every company, so I’m reluctant to order up an SSE Special. How do I leverage this dreaded weekly meeting to turn M from a detractor to a promoter?

    • 34 min
    Episode 409: Fancy title to IC and CRUD is crud

    Episode 409: Fancy title to IC and CRUD is crud

    In this episode, Dave and Jamison answer these questions:




    Listener Shayne asks,





    I’m about to start a new gig after 8+ years at a company. I was an early employee at the current company and have accumulated a lot of responsibility, influence, and a fancy title.


    I’ll be an IC at my new company (also very early stage) but the most senior engineer second only to the CTO.


    What are some tips for this transition? How can I onboard well? How do I live up to my “seniorness” in the midst of learning a new code base, tech stack, and product sector?


    I managed to stay close to the code despite adding managerial responsibilities in my current role, so I’m not worried about the IC work. I really want to make sure that I gel with my new teammates, that I’m able to add valuable contributions ASAP, and that folks learn that they can rely on my judgement when making tradeoffs in the code or the product. Halp!



    I got into software development to become a game developer. Once I became a software developer, I found out I really enjoyed the work. My wife and I joined a game jam (lasting 10 days) over the weekend. I very quickly have realized how passionate and excited I get about game development again! But this has led to a problem - I would much rather be doing that. I find myself moving buttons around or making another CRUD end point a means to an end now, thinking about how I much rather be creating exciting experiences. How can I handle this? Quitting my job to pursue a pipe dream just isn’t feasible.

    • 28 min
    Episode 408: Terrible retrospectives and "hard to work with"

    Episode 408: Terrible retrospectives and "hard to work with"

    In this episode, Dave and Jamison answer these questions:




    I am an electrical engineer working on and off with software for about 15 years. From mainframe applications with Cobol and PL/1 to plant floor supervisory systems with SCADA and some.Net along the way. 6 years ago my husband got an offer to move to Europe and I came along. Had to reinvent myself amidst the chaos of juggling life with a toddler, learning a new language and a new social tissue. After some time I landed a pretty nice job as a DevOps engineer at a pretty cool company. However, I have never really worked with scrum or agile methodologies before and, oh boy…I found out I HATE retrospectives. Like really hate them. They bring me down every time and I anticipate them with dreadful anxiety. I feel they’re just a way to blame other people for what’s not going so well and I don’t see ownership or any improvements actually being made. Action items are frequently just finger pointing and generally about people that are not even present in the retros. In order to improve engagement my boss said every team member is now responsible for the moderation of this dreadful thing and, surprise, surprise : I am next. How can I moderate something I just don’t believe in? I believe in improvement and learning from mistakes and I genuinely believe that we shouldn’t focus on people but processes. I also have to say my colleagues don’t feel the same way as they seem to love retros (yikes!). I think I’m too old/too skeptical for this. Please help!!! Ps.: I love your show and the episode on “that guy” changed my life. I’m forever grateful for the question asker and your answer.



    The Letter J:


    Can you please talk about the PIE theory (performance, image, exposure) and its importance, especially in highly political orgs? I lost my leadership role at a large GSI due to what I believe was a poor image. I felt I could not achieve targets without some level of collaboration (which became conflict once others didnt want to actually collaborate) We hit out targets, but unfortunately, by the time I realized I was labeled “hard to work with”, it was too late. Also, I hereby declare that Jamison is the Norm MacDonald of podcast, which is my highest compliment. Dave is some other comedian, also good. Seriously thank you both for all the humor and advice over the years, it’s been helpful and validating.

    • 33 min
    Episode 407: I'm too territorial and should I quiet quit?

    Episode 407: I'm too territorial and should I quiet quit?

    In this episode, Dave and Jamison answer these questions:




    I am a data scientist and have been at my company for 2 years. Each of the data scientists on my team specialize in a different area of the business (growth, marketing, etc). I have developed a reputation for being the expert in my area and have worked really hard to understand my domain.


    I have a new data science team member who works in an adjacent area and has expressed interest in learning more about “my” area. But every time I talk to him I find myself getting defensive and possessive (on the inside). I don’t want to share my area, and I like being known as the expert, and I don’t want him working on stuff in my domain. Any advice on how to be less territorial here?



    Should I quiet quit?


    I’m a year in to a new job, and am doing well. I work for a large consulting company, and have been doing a decent amount of unpaid overtime by volunteering for internal projects that we can’t bill to our clients! The extra 5-10 hours a week have been adding up, and I feel overwhelmed. I don’t think the extra work is as appreciated as it should be. I’ve received lots of positive feedback, and my performance reviews have been fine.


    Am I getting taken advantage of?


    Will people notice if I step back and just do the bare minimum expected for my job?


    I like being useful, and do genuinely enjoy some of the projects I’ve volunteered for. They’ve probably also been good for my internal visibility, as I’ve gotten to have my name on some large internal announcements and have had some good face time with very senior people. If I end up sticking around here, it’ll probably be good, and I wouldn’t mind a promotion.


    But I’m exhausted, and it’s starting to get in the way of my personal life, hobbies, and even client work sometimes. I’m also wondering if that time would be better spent on upskilling or open source or something outside the company. How far can I cut back without repercussions?

    • 25 min
    Episode 406: Acquired taste and limited mentorship

    Episode 406: Acquired taste and limited mentorship

    In this episode, Dave and Jamison answer these questions:




    Listener Brad asks,


    I am currently a Senior Engineer with a small software company. I have been developing software for more than 20 years. We were recently acquired by another mid sized company. Since the acquisition, things have been going downhill. It feels like they’re trying to nickel and dime their employees to death.


    They moved from a bi-monthly to bi- weekly pay, from accrued PTO to Flex PTO, they sat on merit raises for over 2 months , and have paused all promotions unless you are getting a promotion to management. We have a number of engineers who are deserving, but broaching the subject with HR results in excuses, pushback or silence.


    I have about a year and a half to be in a position to retire but I love what I do and plan to continue for many more years in the right environment. I’m really on the fence as to whether I quit for a new role or hope that they somehow become more efficient. I’ve been doing this long enough to know they will probably not change. So would you quit?



    Hello Dave and Jamison,


    My name is Angelo, and I’m writing to you from Italy. I’ve been enjoying your podcast for quite some time.


    I’m reaching out because I’ve been working for four years at a small company with 11 people in the cultural heritage sector. Although the company produces software, there are only 2 programmers (myself included), while the rest are roles like graphic designers, art historians, and archaeologists.


    It’s a rather unique company in its field, and for that reason, I’m happy to work there, also because I have many responsibilities related to the company’s performance, probably more than I would have in a multinational corporation.


    However, there’s a catch. The fact that there are only two programmers, and in this case, I am the more experienced one, often makes me feel that I don’t have the opportunity to interact with more experienced individuals, and this might hinder my growth as a professional as opposed to being in a team with more programmers.


    My question is: what can I do to compensate for the lack of work interactions with other developers and to keep myself updated?


    I’ve always read that the best growth happens in a company where you’re surrounded by more experienced people, but in this particular case, I find myself in the opposite situation.


    I participate in Telegram groups and often read software development books to stay updated, but it’s also true that the hours outside of work are meant for rest and leisure, so they only go so far. How can I keep pace with those working in larger teams on bigger projects? I don’t intend to change companies at the moment.


    Warm regards from Italy,
    Sinhuè

    • 27 min

Top Podcasts In Technology

ShuffleCast
ShuffleCast
بودكاست رقمي
SahabaCC
Questions for now - Compelling perspectives on digital CX
TELUS International
Smashing Security
Graham Cluley & Carole Theriault
Lex Fridman Podcast
Lex Fridman
This Week in Startups
Jason Calacanis

You Might Also Like

The Stack Overflow Podcast
The Stack Overflow Podcast
Compiler
Red Hat
Coding Blocks
Allen Underwood, Michael Outlaw, Joe Zack
The Changelog: Software Development, Open Source
Changelog Media
Software Engineering Daily
Software Engineering Daily
Syntax - Tasty Web Development Treats
Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers