Recently, I found two “open letters” on the Internet. Episode 36 has me examining their contents and pointing out where I find fault with each. The letter that started it all was from a PM and was aimed at telling developers how to do their job. The rebuttal, from a Developer to a PM, was written to explain how the PM was wrong and how they should do their job. There is actually plenty of wrongdoing in both letters and we’ll take a look at that with the aim of behaving better and having better attitudes in the workplace.
Links Mentioned in this Show:
The Letter from the PM to the Dev
The Letter from the Dev to the PM
You can also subscribe to the podcast at any of these places:
Thanks to all the people who listen, and a special thanks to those who have rated me. I really appreciate it.
The episodes have been archived. Click Here to see the archive page.
In episode 35, I cover the Apple Watch Event. Of course, the two-hour event was not just about the watch, but that’s all most people cared about. I talk about what new things that we learned about the watch, some of the apps that are going to be available at launch, and what it is like to actually develop for the thing yourself. I also answer the most pressing question… will I buy one? Check it out and let me know what you think.
Episode 34 is a little shorter than my normal solo podcasts, but it is a topic that I have been thinking about for awhile and I just wanted to get it off of my chest. Design Patterns aren’t like Duct Tape – the more you use, the better it is. In fact, they actually won’t all work together if you go in 100% on them. Today, I talk about 2 of those examples and then talk about how you should go about discovering good software design.
Last Monday, Rob Eisenberg released Aurelia.js. This was a culmination of sorts of a whirlwind of activity that was kicked off when Rob left the Angular 2.0 team at Google. A lot of people wondered what he was up to (including me!), so I asked him to be on the show to talk about what’s been going on. We talk about SPAs, why he left Google, what’s special about Aurelia, how to handle learning all of these frameworks, and much more.
Andy Adams wrote a blog post about how to price yourself as an independent software developer. It was so good that I made it a pick of the week. Andy started to see traffic from my site and we struck up a conversation. Right away, I knew that I needed to have him on the show. We talk about how he became an independent, how he sets his rates, how to find customers, some of the perils of creating your own products, and whether you even want to be an independent developer in the first place. It is a fantastic interview, check it out.