
Episode 111: Dogma Rehab and Getting a Co-worker Fired
About this episode
In this episode, Dave and Jamison answer these questions:
-
Hello Jamison and Dave. 💕 your show! 👏
I have been a C# dev for 7 years. Last year, I learn Erlang. I fell in love with functional programming. After that I learned Elm and oh boy… I had never dreamed a compiler/computer could do so much work for me, preventing so many mistakes that would otherwise require an unholy number of “unit tests”.
The thing is I can no longer find satisfaction with any job. I love to write software, but at some point I became almost dogmatic. I abhor more and more the discipline it takes, in certain languages, to make my code be as pure and testable as in an FP language.
I had to do so much un-learning, that now I feel that I am refusing to un-un-learn all these different ideas and paradigms and just go back to making the tests happy.
I seek your humorous words of wisdom on how to find contentment with my job again, without looking at a language and dreading it.
-
I have a co-worker, who is pretty incompetent technically. Over the past few years that I’ve been here, he has proved time and again that he is incapable of learning and really grasping how things work. He is able to accomplish basic feature work, but not capable of making good architecture decisions, or why a given framework should be chosen, or how to solve harder problems (I’m not sure how to describe this. But for example, how to build a resilient API client).
However this person is great at creating slides, and presentations, and JIRAs, so I think management thinks they are ok at their job.
He’s also a nice guy. I’m not sure how to say, hey you suck at your job. Which is pretty harsh. Or to suggest to someone that he should be replaced.
Get every episode summarized
Each time Soft Skills Engineering publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Soft Skills Engineering

Episode 529: Zoom calls on my open floor plan and laconic staff engineer
Soft Skills Engineering

Episode 528: Sleepy family software business and leaving after an acquisition
Soft Skills Engineering

Episode 527: I lost my job after 10 years and am I too old to switch to a securi...
Soft Skills Engineering

Episode 526: Why can't I get promoted so quickly after my last promotion and I g...
Soft Skills Engineering