Boilerplate code is code that you import into your project to give you a scaffold to build on. It helps get you to the fun stuff faster. Or does it? This week we discuss why you might (or might not) want to use boilerplate, and dig into what parts of our own stacks we think of as being "boilerplate".
Does Ed think that CSS "frameworks" are true boilerplate? And what old-school boilerplate tool rustles Tom's jimmies? What should you use at the start of every project? And where do you draw the line? Find out all this and more in this week's cookie-cutter instalment of A Question of Code.
Mentioned in this episode:
89: Top Tips review: pragmatic learning
88: Top Tips review: document what you learn
87: Top Tips review: enjoy what you do
86: Top Tips review: just get things done!
85: Top Tips review: why should you build your own website?
84: Why should you own a rubber duck?
83: How do you get started with a new framework?
82: What is semantic markup?
81: What is an API?
80: What’s it like behind the scenes of a podcast?
79: How important are CS fundamentals? (with Vaidehi Joshi)
78: How can developers get better at design?
76: CSS Revisited (Rapid Fire)
75: Why do you need a website of your own? (with Chris Coyier)
74: How do you get started with testing? (with Brian Okken)
73: Why is Python a good starting point for learning to code? (with Michael Kennedy)
72: CSS Extravaganza!
71: How should developers market themselves? (with Shawn Wang)
70: Is "become a developer" still good advice?
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