Introducing The Rules of Software Development Podcast
A couple of years ago I wrote a post titled “Rules of Software Development”. The post listed out some rules I believe should be followed by developers in their endeavour to create quality products. You can read that post here.
It also kick started me questioning a lot about software and what other “Rules” there could be. I began thinking about professionalism in software and what it means in-depth. The “Rules” I had put down could essentially be looked at as tips to be professional in software.
The thing about software engineering is that really it’s a new discipline. There isn’t hundreds of years of this industry for a professional culture to have been built around. This means that in some ways we are still trying to find our feet on what exactly is professional behaviour in software.
Last year, my role changed from a technical lead to a software development manager, and this brought about new challenges but also a new perspective on how I would expect a software professional to go about their work.
Having that new perspective made me question what other people in the industry would view as professional in the software engineer role. For instance, while for me I expect quality and TDD to be a standard, a Product Owner is likely more concerned with an engineer engaging with an interest in the business and having a fuller understanding of the wider scope then just his/her part.
Or are they? This was just my assumption that this is what a Product Owner wants, maybe it isn’t.
And so I wanted to get the different view points of what makes a professional software developer from product owners, UX designers, recruiters, development managers, UX researchers, architects, CTO’s, etc. And of course, from software engineers themselves.
So I have started a podcast entitled “The Rules of Software Development”.
You can listen to the first episode with Álvaro Pereda on the following platforms:
Or you can listen below 👍
