Side projects (or "side hustles" if you're feeling more entrepreneurial) are a subject that comes up a lot with developers. It can seem like every programmer has seven or eight projects that they're working on in the wings, any one of which could become a world-beating business at any moment. But is there more to this than just hype? Are there more benefits to having a side project than mere bragging rights? What, in short, are the tangible reasons for having one?
Do you need to have them? How much do they factor in when you're applying for jobs? Are they useful when you're just starting out and still learning how things work? How many side projects has Tom started? And is that the same as the number of his side-projects that have reached the MVP-level of done? (Spoiler alert; they are two very different numbers). Find out all this and more in this week's distracting instalment of A Question of Code.
Mentioned in this episode:
49: What is a build pipeline?
48: Agency or product?
47: How do you build a blog?
46: How do you apply to speak at a conference? (with Tony Edwards)
45: Should you take a bootcamp?
44: What is the difference between a framework and a library?
43: Yearly Themes: 2020
42: What does a developer do all day?
41: How long does it take to get a job in tech?
40: Can you trust recruiters?
39: Do you have impostor syndrome?
38: If it's not broken should you fix it?
⚡️ Help us, listeners. You're our only hope
37: When are you ready for a coding job?
36: How do you keep track of your knowledge?
35: Do you git it? (What is version control?)
34: How do you learn a new programming language?
33: How much tooling is too much tooling?
32: How do you prepare for a new job?
31: Should you pivot?
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
Lex Fridman Podcast