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.
15: What happens in a kick off meeting?
14: How do you learn?
13: Project Introduction
12: Should you get a CS degree?
11: When should you change to your second language?
10: Is coding less fun when it’s your job?
9: Where do you find jobs?
8: When should you quit your job?
7: Where do you learn?
6: What tools do you need?
5: Which language should you learn first?
4: How do you manage your time?
3: Freelance or full-time?
2: Frontend or Backend?
1: Why are you learning to code?
Trailer: A Question of Code
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Acquired