A Question of Code

{{ show.title }}Trailer Bonus Episode {{ selectedEpisode.number }}
{{ selectedEpisode.title }}
|
{{ displaySpeed }}x
{{ selectedEpisode.title }}
By {{ selectedEpisode.author }}
Broadcast by

Summary

Being stuck sucks. Unblock yourself by explaining your problems to other people (and maybe to inanimate objects, too?)

Show Notes

It is a truth universally acknowledged that any developer in possession of a bug must be in need of a rubber duck to talk to.

There are lots of ways to get "stuck" when programming. It can often be because of something simple, like a syntax error or typo, or maybe a fundamental lack of knowledge or experience with the system you're using (be it an API, framework, or whatever...). It could even be an "architectural" issue, or a bizarre language quirk. Perhaps it's a situation where a weird hack is required? Do you know them all?

One of the most effective ways to get "unstuck" it to rubber duck. That is to say, to talk about your problem to someone (or something). Explaining an idea helps clarify it in your own mind, and if you can't explain something clearly then there's a good chance that you don't really know it. So what are the benefits of sharing often and early? What is "The Curse of the Demo"? And why can pair-programming be a super power? Find out all this and more in this week's talky instalment of A Question of Code.

What is A Question of Code?

A newbie coder and a seasoned veteran discuss the questions that always come up when someone begins learning to code.

Ed is looking at getting a career in programming and has been learning to code for just over a year. During this time he’s been building up a stack of questions that keep coming up from other newbie coders. Luckily, he’s got someone he can ask for help: Tom. Tom’s a seasoned coder, having worked in the industry for a few years now and has all the answers Ed needs, or does he?