Powered by RND
PodcastyTechnologiaSoft Skills Engineering
Słuchaj Soft Skills Engineering w aplikacji
Słuchaj Soft Skills Engineering w aplikacji
(4 676)(250 137)
Zapisz stacje
Budzik
Sleep timer

Soft Skills Engineering

Podcast Soft Skills Engineering
Jamison Dance and Dave Smith
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...

Dostępne odcinki

5 z 449
  • Episode 448: Title over salary and from figure skater to software developer
    In this episode, Dave and Jamison answer these questions: A listener named Steven says, Long-time listener of the podcast here—it always brings me so much joy! Should I prioritize title over salary? I’m currently based in Europe, working as a Senior Engineer at a big company that pays really well. The problem is, there’s almost no chance for promotion due to the economy and budget constraints. Plus, because of the organizational structure, I’m stuck solving small problems that don’t have a big impact. It’s frustrating—but again, the pay is great. Recently, I got an offer for a Staff Engineer position at another company. The catch is, the pay isn’t as good (30%+ cut), and I’m not sure about their culture or structure yet. However, the title could potentially open more doors for me in the future. Should I take the offer, accept the pay cut, and hope it’s a step forward for my career? Hello! Long time listener, first-time caller :-) I’m on the final stretch of classes to finish my BS in computer science at WGU, most of which I’ve done while working. I’m now 40, and I have had 3 previous occupations and employers: aircraft mechanic for 5 years at a small shop, figure skater with Disney on Ice for 6 years, and most recently a partner at an environmental remediation/heavy construction firm for 10 years where my primary responsibilities were field crew management and technical writing for ecology reports. I would love your advice on how I could use these experiences to stand out on a resume or in a job interview. How can I indicate that I’m a hard worker and that I know just enough to know that I know nothing and am ready to learn? Thank you for your time, keep up the good work!
    --------  
    28:01
  • Episode 447: Overleveled at FAANG and accidental draft feedback
    In this episode, Dave and Jamison answer these questions: I am a mid level engineer overleveled as a senior engineer in a FAANG company. I got super lucky landing this high paying remote job, but dang… I did underestimate the expectations for my senior level. I had no FAANG experience before, just working at startups, flat hierarchies, just doing the heavy lifting coding. Now it is all about impact and multiplying impact across the team. I am told I should do less IC work and more leading of projects and owning initiatives. Can you give me some general advice on what actions I can take to get from the mid-level to senior-level? I am not really sure, what taking ownership really means in practice… These just seem like empty phrases to me without a meaning… I have had a bit of time, while running a 40 minute build, so I looked into open pull requests. One PR caught my eye and I started to read through it and left a comment with a suggestion for a small change. All in all sounds good probably, but the caveat to this is, that the PR was marked as Draft. I was thinking that it would be useful for the author of the PR to already get some suggestions during development, but the response got me thinking. The author passive aggressively mentioned that the PR is in Draft and that there is more work to do. Am I the jerk for commenting on a draft PR? Second question, what other things should I pay attention to in code reviews to not be a jerk?
    --------  
    30:11
  • Episode 446: Wading through AI slop and they don't get git
    In this episode, Dave and Jamison answer these questions: A listener named Matthias (mah-TEA-as) asks, In episode 444 you’re talking about the problems when hiring in the age of AI. I’m a manager who’s trying to hire right now and frankly I’m at a loss. If feels like I’m wading through a sea of AI slop. What tips do you have to cut through the slop and reach actually good candidates? Where I work the developers do not seem to “get” source code control systems like git. I’m not a developer but have worked with developers at previous jobs and usually the developers instituted good source control practices themselves. Our developers know they should push their code to the repo but only do it weekly/monthly, treating it as a “backup”. Some back up their laptops using tools like Time Machine so think have taken care of safeguarding their source code that way. How can I convince them that working in git, committing their code as they go, pushing regularly, branching/merging, tying code updates to tickets, etc will benefit them far more in the long run?
    --------  
    33:19
  • Episode 445: Staying at my first job and my coworker is insulting other departments
    In this episode, Dave and Jamison answer these questions: A listener named Kevin asks, Hey, found the show and really enjoy it! Been listening from the beginning and have noticed that one of the pieces of advice given is that you should not stay at your first job for too long, because it’s more likely that you’ve not found the best job for you. I think The Secretary Problem is the closest thing being cited. I tend to agree with the math, but I’m still at my first software engineering job after 5 years and don’t really want to leave. There are obviously things I don’t particularly like or people I find challenging, but for the most part, I work on interesting projects with smart people, it’s fully remote, the benefits are great, and my salary is comfortable. There have been times where I started to look for another job, only to have my current circumstances improve enough that I stopped the search. What advice do you have for someone like me? I don’t know if it’s relevant, but I’ve managed to get married, buy a house, and just recently had our first baby. The pressure to provide and be conservative with my career is building. Again, love the show and I hope you’ll get to answering this before I catch up. I started from the beginning in late 2024, and in mid Jan 2025, I’m just past episode 50. I’ll let you do the math. As a tech lead, I joined a project two years in the making which had only one engineer doing everything, including management. In the two years, only a POC has been completed and a “pre MVP-MVP” build is in progress. There is a hangup though, the funding for the project is supposed to come from another departments budget that doesn’t want it, and work was committed by the department I am in, and a third department intended to be completed by the end of the quarter. I have been trying to finesse my teammate into cancelling the project or at least allow a resetting of expectations. My manager agrees with me. There seems to be a tug of war between AVPs and Directors. This has led my teammate to make some corporate aggressive comments. These are being directed in many directions, including department heads opposing the project. In your professional space experience, how can I help my teammate with understanding that his tactics are potentially damaging to his reputation and the project?
    --------  
    26:23
  • Episode 444: Surrounded by apathetic coworkers and put it on my resume?
    In this episode, Dave and Jamison answer these questions: After a decade as a Senior front-end engineer in companies stuck in legacy ways of working—paying lip service to true agility while clinging to control-heavy, waterfall practices—I’m frustrated and exhausted by meetings and largely apathetic, outsourced teams who don’t match my enthusiasm for product-thinking or improving things. It seems allowed and normalised everywhere I go. How can I escape this cycle of big tech, unfulfilled as an engineer, and find a team with a strong product engineering culture where I can do high-impact work with similarly empowered teams? Thank you, and sorry if this is a bit verbose! Thanks guys. Martin ‌ How do you judge your competency in a technical skill and when should you include it on your resume? Should you include a skills that you haven’t used in a while, skills you’ve only used in personal projects, or skills that you feel you only have a basic understanding of? I’m a frontend developer and I’ve seen some job descriptions include requirements (not nice-to-haves) like backend experience, Java, CI/CD, and UI/UX design using tools like Figma and Photoshop. I could make designs or write the backend code for a basic CRUD app, but it would take me some time, especially if I’m building things from scratch. I’ve seen some resumes where the writer lists a bunch of programming languages and technical skills, and I often wonder if they truly are competent in all of those skills.
    --------  
    31:10

Więcej Technologia podcastów

O 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.
Strona internetowa podcastu

Słuchaj Soft Skills Engineering, Techstorie - rozmowy o technologiach i wielu innych podcastów z całego świata dzięki aplikacji radio.pl

Uzyskaj bezpłatną aplikację radio.pl

  • Stacje i podcasty do zakładek
  • Strumieniuj przez Wi-Fi lub Bluetooth
  • Obsługuje Carplay & Android Auto
  • Jeszcze więcej funkcjonalności
Media spoecznościowe
v7.8.0 | © 2007-2025 radio.de GmbH
Generated: 2/21/2025 - 2:31:24 AM