Earlier this year, I was invited to be on the The Grumpy Developer Podcast. It was a lot of fun, I really enjoyed my time on the show, and Mike – the host – and I hit it off.
Recall that the show aims to achieve the following:
If you’re a designer or project manager, you can consider me your friendly developer translator. I’m here to help you bypass the Grumpy Developer Syndrome and achieve a happy transition from design to launch. If you’re a developer…well…you’re welcome. Let’s all celebrate a departure from Happy Designer Land to a world where design-dev-project managers can all get along.
Fast forward a few weeks and I was invited back on to the show for another conversation about a variety of different things all of which were programming related.
The Grumpy Developer Podcast: Episode 41
You can checkout the episode by visiting its respective page, but you’ve likely already got a copy of the episode in your application of choice if you’ve previously subscribed to the show.
Anyway, in this episode, Mike and I talk about the following:
- A brief mention about one of my current projects
- Some lessons learned from previous blog posts
- The Obligations of Learning a New Programming Language
- Various design patterns
- Advice and thoughts for budding developers who have time to dive to into a variety of languages
- What would I be doing if I were not working with WordPress and associated technologies?
- Why WordPress is seen as an application with a low barrier to entry
- What is the future of WordPress?
- …and more
Comments on this particular post are closed as I’d rather the discussion – if any – happen on the episode’s page. And if you’ve not already subscribed to the show, I recommend it.
The show features some good discussion and a lot of great guests who are worth listening to even if they aren’t working specifically in your field.
The Grumpy Developer Podcast Revisited was written by Tom. Check out additional articles on the full blog at Tom McFarlin.
Read more here:: The Grumpy Developer Podcast Revisited