This week we're joined by Jeremy Keith, a web developer and author who's had a massive influence on at least one of our hosts. Jeremy introduces us to the concept of "resilient" websites, and has loads of advice for developers new to the field. The web is for everyone, and websites should reflect that: if you're using some advanced fancy features, make sure that your core functionality is available to everyone.
We delve into the thorny issues of progressive enhancement and graceful degradation. Are they ultimately the same thing? Or does real-world pragmatism get in the way? Is it easier to become a web developer today? Or has the increase in dev-tooling added too much complexity? Find out all this and more in this week's resilient 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?
77: Should you use boilerplates?
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
Lex Fridman Podcast