Partner im RedaktionsNetzwerk Deutschland
Radio Logo
The station's stream will start in null sec.
Listen to Soft Skills Engineering in the App
Listen to Soft Skills Engineering in the App
(171,489)
Save favourites
Alarm
Sleep timer
Save favourites
Alarm
Sleep timer
HomePodcastsTechnology
Soft Skills Engineering

Soft Skills Engineering

Podcast Soft Skills Engineering
Podcast Soft Skills Engineering

Soft Skills Engineering

Jamison Dance and Dave Smith
add
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 t... More
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 t... More

Available Episodes

5 of 359
  • Episode 358: Sticky Note Scandal and startup appeal
    In this episode, Dave and Jamison answer these questions: During our next team meeting I jokingly gave a status report on the state of my desk and referenced the note. I believe this was the first time someone had publicly acknowledged the note writer, and it invoked a very passionate response from my teammates expressing their own annoyances with the anonymous writer. ‌ It began to escalate the following week. Copy cat writers began writing their own sarcastic notes, and junior devs were (jokingly) doing handwriting analyses to find the culprit. I participated in none of this. However my manager pulled me aside to say he is now forced to address the situation due to someone filing an official complaint that I was “instigating workplace harassment” and that I created a “hostile, unsafe environment”. He informed me we will be having a meeting with HR regarding this incident. I have never had a meeting with HR before. I am very afraid of potentially losing my job due to this. I find this whole situation ridiculous and feel very frustrated. Please help me not make this a bigger mess than it already is. Aaron asks, Last week I listened to a show where Jamison announced that he was looking for work, and specifically looking for small to medium startups. I have only worked at larger tech companies, and currently enjoy my position within one of the largest. However, I’ve always wondered what it would be like to work at a startup. What makes startups appealing? Is it still reasonable to expect a good work/life balance, or do you go in expecting a big shift in how you dedicate your time?
    29/05/2023
    35:13
  • Episode 357: Waiting to be paid and survivor's guilt
    In this episode, Dave and Jamison answer these questions: A listener Steve asks, How long is too long to wait to be paid? I’ve worked for 4 early stage startups in my career. Two were successful. One failed. My current one is “limping along” but showing signs of taking off. At the startup that failed, we stopped getting paid and some of us stuck around for 2-3 months until the CEO closed the business. I ended up unpaid for nearly 3 months of work. At my current startup, we are 3 months behind, and it has been this way for 6 months. The CEO is transparent about fund raising and clients slow in paying invoices. My question is still how long before I follow your age old advice? Listener Jess asks, ‌ How do I get past survivors guilt when my company does mass layoffs, but I am not one of the casualties? I’ve been at the company less than a year, and this is the second time they’ve fired THOUSANDS of people, including from my team; folks I work with at least weekly, and folks who have been at the company significantly longer than I have. I feel guilty that I, “The new guy”, am still employed, but the folks who’ve been there for years aren’t. How can I get past this and keep working to ensure I’m not caught up in the next round of layoffs? My manager says I’m doing good work, and the layoffs included complex inputs, but it that only helps a little bit.
    22/05/2023
    29:16
  • Episode 356: Ummmmmmmmm and failed spikes
    In this episode, Dave and Jamison answer these questions: I recently started listening to your podcast from the very start of the show! One of the largest differences I noticed (aside from the audio quality, lol), is how often you used filler words like “um”. How on earth did you manage to stop using them? In work presentations and demos, I often end up using the filler words, and listening to the recordings later is painful. The rehearsed parts of the presentation go smoothly, but as soon as I go out of the “script”, I start depending on filler words. How do I get better at this? How exactly should spikes go? I’ve done some deep dives to understand the scope and steps of an upcoming effort, all with detailed write-ups, only to later realize during the implementation that I got some things wrong or missed out some important details. Isn’t that the point of a spike, to root out any unknowns or surprises? Short of just doing the actual implementation, which I’m pretty sure is also missing the point of a spike, What am I doing wrong and how can I properly present post-spike findings to my team?
    15/05/2023
    28:54
  • Episode 355: Driving kids instead of team and jk i quit
    In this episode, Dave and Jamison answer these questions: My architect is too busy with his kids! His kids have had a lot of school and medical issues over the last few months and he’s ended up flexing a lot to take care of them. This causes meetings to get rescheduled or scheduled far out in the future, which is contributing to timeline delays on some large projects that need more attention. I don’t want to be rude and insist that he put the company above his family, but he needs to be driving organizational alignment, not his kids! I’m stressed out by not knowing when he’ll be available and having to do extra work or take important meetings without having him as backup! ‌ Can you help me understand what happened here? I was put on a ‘performance improvement plan,’ and it became pretty clear to me from the negative feedback at my first review that I simply didn’t have the skill to perform at the level that was being asked for. Instead of immediately looking for a new position, I decided to take some personal time off to work on myself and my mental health, and to use the remainder of the performance improvement plan time to prepare myself emotionally and financially for that. I didn’t blow off work, but I also wasn’t invested in the performance improvement plan either. A few days before my final review, I quit instead of being terminated. Management seemed really confused and angry when I quit. Why would they be so upset if they were about to terminate me anyway? One in particular started backtracking and pretending like I wasn’t going to be terminated.
    8/05/2023
    25:52
  • Episode 354: Good at circuits, bad at git and ghosts of team members past
    In this episode, Dave and Jamison answer these questions: I work at a startup that makes embedded devices and the software that runs on them. Everyone on the tech team does both. We recently hired someone to lead the tech team to give the CTO more time for other duties. My new boss is incredibly experienced with hardware design and embedded systems and has been in the industry for a long time (40+ years). However, they are not familiar with modern software practices like version control. They will frequently ask us to do things like delete all copies of a broken version of software. When we try to explain how git works they will ask us to make a new repo with the now working version of the software even if the fix was a 1 line change. How can I politely explain that they just don’t understand how this works and correct them without being rude? What’s a “normal” rate of performance firings on a team/engineering department? I recently got a new job at a growing startup, and it’s fairly uncomfortable seeing the ghosts, on messaging apps and docs, of like 6 people in the ~25-person department who’ve been fired in the last half year. With that said, the department is continuing to hire, so I don’t think this necessarily means I should be worried. But does that sound like an unusual amount of performance-based firings?
    1/05/2023
    29:07

More Technology podcasts

About Soft Skills Engineering

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.
Podcast website

Listen to Soft Skills Engineering, No AC Only Fans and Many Other Stations from Around the World with the radio.net App

Soft Skills Engineering

Soft Skills Engineering

Download now for free and listen to the radio easily.

Google Play StoreApp Store