Better ROI from Software Development

During September, I'm running a short survey to understand UK Executive's attitudes to custom software development.  Please take the time and have your say at: https://software-survey.red-folder.com/

In this episode I continue to look at professionalism in software development.

I take the fourth oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: I will make frequent, small, releases so that I do not impede the progress of others."

During September, I'm running a short survey to understand UK Executive's attitudes to custom software development.  Please take the time and have your say at: https://software-survey.red-folder.com/

In this episode I continue to look at professionalism in software development.

I take the third oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should."

In this episode I continue to look at professionalism in software development.

I take the second oath from the Programmer's Oath by Uncle Bob Martin, introduced in episode #51, to explore further:

"I Promise that, to the best of my ability and judgement: The code that I produce will always be my best work. I will not knowingly allow code that is defective either in behavior or structure to accumulate."

In this episode I continue to look at professionalism in software development.

I take the first oath from the Programmer's Oath by Uncle Bob Martin, introduced in the last episode, to explore further:

I Promise that, to the best of my ability and judgement: I will not produce harmful code.

In this episode I start to look at professionalism in software development.

Software development doesn't have the same level of professionalism & accountability found in Doctors, Lawyers or Architects.

In this episode I talk about why it is desirable, but unlikely to happen.

And I introduce the Programmers Oath - an attempt to start the conversation 

In this episode I provide a recap of the episodes since the last recap show (episode #25).

This episode is both a recap of the series since episode #25 and a good entry point for new listeners.

During this episode, I'll be summarising the key takeaways - and which episodes to listen to if you want more.

In this episode I want to discuss how dangerous it can be to assume another persons intent purely from their actions.

This is a message I am seeing come up quite a bit lately.

And the more I think about it, the more I see it in everyday business work.

Both in how we perceive our teams and how our teams perceive us.

Over the last few episodes I've talked about learning to improve our individuals, teams and entire organisations to handle change.

In this episode I want to explore why it is so important to that we are learning to build our Software right.

Often the focus of our teams is to build the right thing - which is certainly important. But we also need to think about building the thing right.

In this episode I wanted to continue the conversation on Learning.

In the last few episodes, I talked about;

In this episode I want to looks at how the Software Development team can learn through a number of deliberate practices.

In this episode I wanted to continue the conversation on Learning.

In the last two episodes I talked about why Learning is so important to me personally and Organisational Learning.

In this episode, I want to move onto talking helping Individual Learning.