
Sign up to save your podcasts
Or


As software developers, our job is to deliver software that is appropriate for our user base so that they may solve some sort of problem. This is something I think we struggle with as an industry. In this episode, I dig into the topic of understanding your user base and then offer several takeaways to help you deliver better solutions to them.
We often encounter the phrase "ship early, ship often". What does it mean? Where does it fit into software dev and Agile specifically? In this episode, I examine the phrase and try to dig out some conclusions about when and where "ship early, ship often" really applies.
So many tech talking heads will advise someone in a tricky situation to "find a better job", but what if that's not possible? In this episode, I dig into the options programmers have when they can't or don't want to leave their current jobs.
The vast majority of software projects have deadlines. Sometimes these deadlines are realistic, other times they're not. In this episode, I dig into ways of effectively using what time you have to ship the best code possible, whether that deadline is far away or right around the corner.
Your organization has a specific culture. So does the department in which you work. Even your project team has a specific culture. Who drives these levels of culture? How can it be changed, or should it? In this episode, I dig into the topic and offer thoughts on how to understand, navigate, affect change, and use that culture to enhance your project, career, and overall job satisfaction.
Most software development projects these days divide tasks between the technical people and business people. Technical people include programmers, QA analysts, data professionals, and the like. Business people typically refers to project managers, product owners, and business analysts. For some projects, this dynamic clicks really well, but for others, it can become hostile. In this episode, I dig into some of the pitfalls of this relationship, how to repair and avoid broken dynamics, and why it's so important to keep this dynamic healthy.
Hopefully, our projects reach their v1 ship dates. Those last few months can be exciting and nerve-wracking. Many times, development teams will want to spend some of that period doing code cleanup, but what if v1 scope hasn't yet been completed? In the argument of MVP scope vs technical debt, who wins? I dig into that topic and give some advice on how to defuse the situation and hopefully avoid it altogether in the future.
Last week we dug into the non-technical reasons that cause projects to fail. As promised, this week I turn our attention to the various things that developers do that can cause projects to fail. I also spend a little time talking about the different meanings of failure in this industry. We finish up with takeaways for developers that will help them avoid this situation.
Software projects fail all of the time. When they do, we as developers can take it very personally. I think it's important for us to reflect on how we contributed to those failures, but I think it's equally important for us to understand some of the non-technical reasons that projects fail. In this episode, I explore some of those non-technical circumstances.
Lately, I've been seeing a lot of chatter regarding generalists vs specialists in the field of software development. It's an interesting and somewhat controversial topic. In this episode I dig into my take on it, the history behind the question as I've seen it, and my general thoughts and takeaways.
From the publisher's feed