Ruby developer and author Justin Weiss joins me to talk about his experience working with Avdi Grimm on a guest episode for Ruby Tapas, why he chose Rails, and his book. Then, Justin gives you his 30-second suggestion to help you become a better developer.

Mentioned:

If you are enjoying the show, would you consider buying me some tea?

In this episode, I talk about how I approach programmatic problems, and I give all developers my opinionated understanding of the most important factor of problem solving: imparting knowledge into your problem solving mechanisms.

Note: there was a bit of an audio issue with the compression on this episode; we'll be fixing it in future episodes. Sorry about that!

If you are enjoying the show, would you consider buying me some tea?

In this episode, I share some of the stuff I've been using. None of these folks are sponsoring the show.

Mentioned:

Also, here's Yehuda Katz's positive thoughts on vim from back in 2010, despite the title:

And reasons why you might consider emacs: Should I learn to use emacs? (Stackoverflow)

If you enjoyed this episode, please consider buying me some tea.

In this episode, we cover (only 2 of) the hardest parts of computer science. Spoiler alert: this short podcast will not solve all of your complex coding conundrums, but it will provide you with some alliterative show notes.

Martin Fowler's quotation of Phil Karlton here: http://martinfowler.com/bliki/TwoHardThings.html

If you enjoyed this episode, please consider buying me some tea.

On today's episode, I talk with Nick Morrison and Kody Dahl, both students about to graduate from the design BFA program at Georgia State University, for the second part of our interview.

Kody and Nick are both incredibly hard-working folks who happen to also work at Whiteboard.

In part two, we have a discussion about their professors, design software, life skills, and we (try) to answer the $150,000 question.

A big thanks to Nick and Kody! Follow them:

On today's episode, I talk with Nick Morrison and Kody Dahl, both students about to graduate from the design BFA program at Georgia State University.

In part one, we start a discussion on formal design education.

The interview went quite a bit longer than we expected it to go, so I've decided to split the interview into two parts, which will both be released this week.

If you enjoyed this episode, please consider buying me some tea.

How do you code a feeling?

We've managed to hit LESS than 5 minutes on this one! Hope you enjoy it. Up next in the queue is our first interview episode double-release, which is a bit longer, so be on the look out!

If you enjoyed this episode, please consider buying me some tea.

In today's episode, we will not be talking about drugs. For long. Instead, we're going to talk about some kind-of amazingly weird trends in how we use technology, and how we might could be more intentional in the time we spend with screens.

We (again) went over the 10 minute mark, but hopefully the discussion is worth the extra half minute to you!

If you enjoyed this episode, please consider buying me some tea.

Learning is one of the most important skills for developers to cultivate. In this episode, I'll talk about why that's the case, and a method for learning you might not have tried before.

If you enjoyed this episode, please consider buying me some tea.

Prototyping is a process that bridges the gap between production and static design. In this episode, I talk a bit about what that means, and about what is required for all good prototypes. If you aren't prototyping now, you need to catch up.

Edit: I accidentally called the Facebook prototyping tool, Origami, "Paper". Of course, this was a mistake. Sorry about that folks.