
Sign up to save your podcasts
Or


Blaming the last programmer. We've all done it. It's practically a time-honored tradition. I find it both fascinating and annoying. In this more lighthearted, I talk about blaming the coder before you and some of the insights about it.
Last week I talked about rollouts in general. Today we're going to talk about ways I've seen software rollouts go horribly wrong.
Whatever kind of developer you are, for most of us shipping code is our overall objective. At some point, all the theory about patterns and business rules and the debates about frameworks and tech give way to the realities of getting your code in front of the users. In this episode, I talk about those realities.
We like to think that people get what they deserve, that their good or bad karma will catch up to them. This is true even of logical thinkers like programmers. We like to think that developers who work hard and ship good software will be rewarded and that good leaders will be promoted into management. In this episode, I talk about these ideas and whether or not they're realistic.
I expect a lot of myself professionally. That comes largely from my upbringing and my early 20s, and it sometimes causes me to be really hard on myself. I also tend to carry those expectations over to others, and that can cause me to struggle when I feel others haven't met those expectations. In this bonus episode, I talk about those expectations and whether or not they're realistic.
Incorporating trendy new tech into our projects can be a big temptation. Last week I talked about some of the dangers of doing just that, this week I want to talk about the criteria I think your project should meet if you are going to pull in some of those things.
Programming, and web dev especially, can be prone to fads. In some respects, they drive innovation, but from another point of view, I think the constant reinvention stifles our ability to build solutions that can stand the test of time. In this episode, I dig into the dangers of fads and how I ended up burned out from web dev.
I can be a pretty honest and direct guy, and that has gotten me into hot water as a programmer on more than one occasion. In this episode I talk about my struggles with trying to be more diplomatic and the mixed feelings I have about it.
Last week we talked about the importance of building key relationships in the hopes of giving you, your developers, and your project an increased chance of success. What if those relationships go wrong, or already are? In this show I go over how to repair those relationships when possible and mitigate them when you can't.
"Office politics" brings to mind images of nasty people backstabbing each other to jockey for position at the office. These days people prefer the phrase "soft skills". Whatever phrase you use, the truth is that maintaining good relationships with key people can help programmers and their projects really succeed. In this episode I go over some of those relationships that I think are really helpful for software developers.
From the publisher's feed