A Question of Code

We've had some great guests on our podcast, and we've asked each of them for their "Three Top Tips" for new developers. All their advice has been amazing, and a lot of the same concepts have come up time and time again. In this miniseries we're looking back at those top tips, and linking the themes together.This week our theme is "pragmatic learning". There are lots of routes into this industry, and an overwhelming number of things to start learning. Taking a step back to focus on some of the core competencies can be invaluable. So why should you focus on languages rather than frameworks? And what's wrong with copy/paste development (spoiler alert: _nothing!_). Where can you go to learn the things you need to learn? And why should you avoid specializing too early? Find out all this and more in this week's rehashed instalment of A Question of Code.

We've had some great guests on our podcast, and we've asked each of them for their "Three Top Tips" for new developers. All their advice has been amazing, and a lot of the same concepts have come up time and time again. In this miniseries we're looking back at those top tips, and linking the themes together.This week our theme is "documenting what you've learnt". Who benefits when you write about your career progress? Strangers, peers, yourself? (Spoiler: all of the above). What are the less-than-obvious benefits of leaving a paper-trail of your explorations in the world of code? Find out all this and more in this week's rehashed instalment of A Question of Code.

We've had some great guests on our podcast, and we've asked each of them for their "Three Top Tips" for new developers. All their advice has been amazing, and a lot of the same concepts have come up time and time again. In this miniseries we're looking back at those top tips, and linking the themes together.This week our theme is "enjoyment". How do you work out what parts of the job you enjoy most? And how should that knowledge steer your next steps? Find out all this and more in this week's rehashed instalment of A Question of Code.

We've had some great guests on our podcast, and we've asked each of them for their "Three Top Tips" for new developers. All their advice has been amazing, and a lot of the same concepts have come up time and time again. In this miniseries we're looking back at those top tips, and linking the themes together.This week our theme is "getting things done": that is to say, just start already! There's a lot to be said for doing research and preparing thoroughly, but there's even more power in just starting. By doing a thing, you really start to learn the thing. There's a gulf of distance between knowing something "in the head" and knowing that same thing "in the hand". So should you start coding straight away? And what are the best ways to jump in at the deep end? Find out all this and more in this week's rehashed instalment of A Question of Code.

We've had some great guests on our podcast, and we've asked each of them for their "Three Top Tips" for new developers. All their advice has been amazing, and a lot of the same concepts have come up time and time again. In this miniseries we're looking back at those top tips, and linking the themes together.This week our theme is "Just Build Websites". Having a project to guide your learning and apply your knowledge is really useful, especially when you're just starting out (but also useful at every stage of your career). So who thought this was advice worth sharing? Find out all this and more in this week's rehashed instalment of A Question of Code.

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.

We're trying something new this week. Live-coding is famously risky when giving a talk or presentation, but we figured it might be fun to make things even harder by removing all the visual elements. That's right; we're live coding on a podcast!There are a lot of frontend frameworks out there, so being comfortable picking up a new framework is a useful skill to have. To demonstrate and demystify this process, we've picked a framework neither of us have ever used before: Svelte. In this episode we get to "hello, world!" and beyond, and explain how we normally approach the process of learning a new framework.What are "ah ha!" moments, and how often do they come along? What does npm install even mean?! What have we learned about Svelte, and what would our next steps be? Find out all this and more in this week's risky instalment of A Question of Code.Mentioned in this episode:svelte.devUp and running with Svelte 3 (Egghead.io video course)

This week we get deep into the weeds of HTML. What tags do we use (and are they the same as the tags we should use)? And who are we wring our markup for? Just browsers, surely?! But what about search-engine crawlers and accessibility tools?So how can we structure our web pages so that they do a great job in all scenarios? How much do we care about the distinction between links and buttons? Find out all this and more in this week's semantically meaningful instalment of A Question of Code.Mentioned in this episode: Lynx, the terminal-based web browser

Development (and web-dev in particular) is a field full of initialisms and acronyms. We often take them for granted without thinking too much about these things that we use every day. This week we dive into one of the most common TLIs (Three Letter Initialisms) that all web developers will encounter sooner or later: APIs (also known as Application Programming Interfaces).How well do we know our TLIs? How (and why) might you scrape data from a web page? And why would using an API be preferable? And when should you take the time to learn APIs? Find out all this and more in this week's application-interfacing instalment of A Question of Code.Mentioned in this episode:SWAPI (the Star Wars API)httpstatuses.comPostman

To celebrate our eightieth full episode, we pull back the curtain to show you how the sausage gets made. When we were starting out, "meta" episodes like these were a great way to learn how our podcasting heroes ran their shows. Now, we're not calling ourselves "heroes" just yet, but we've been doing this long enough to have some tidbits of advice for anyone looking at starting their own show.How much preparation do we do for each episode? (Spoiler alert: very little) What gear and software do we use to record the show? And how much time does it take to edit? Find out all this and more in this week's introverted instalment of A Question of Code.

What's this? Another of our heroes joining us for a chat!? You betcha! This week we're joined by the immensely talented and infectiously friendly Vaidehi Joshi. You'll know Vaidehi from her work on the Base.cs blog series and podcast (a must-listen show; it's awesome).How did Vaidehi get into the world of computer science in the first place? And is it something she thinks everyone else should do, too? Are technical interviews that lean heavily on core CS skills useful in a world where most developers don't use them in their day-to-day work? (Spoiler alert: the system needs some improvements) And where can you go to improve your CS knowledge? Find out all this and more in this week's CS-friendly instalment of A Question of Code.Mentioned in this episode:Vaidehi on Twitter @vaidehijoshiBase.cs blog postsBase.cs PodcastForemdev.toEdsger Djikstra and his famous algorithmFinding The Shortest Path, With A Little Help From DijkstraMIT Courseware videos

If you're a developer you should absolutely know a little bit about design. You don't need to be an expert, but knowing some of the fundamentals of good layout and "usability" will be a massive force multiplier for your work. It's also a general "life hack" that will improve your career in many, many ways.So what should you do if you're a developer who doesn't know anything about design? How does design fit into a normal project's workflow? Can you get 80% of the benefit by just learning a few simple rules? (Spoiler alert: we think you can!) And where are some good places for developers to learn more about "designing" for apps and the web? Find out all this and more in this week's well designed instalment of A Question of Code.Mentioned in this episode:Refactoring UI bookSteve Schoger's design tips on Twitter

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: Bootstrap (RIP) Tailwind create-react-app

It's another rapid-fire multi-question show this week. Ed has some more questions about CSS, and (hopefully) Tom has some answers. Join us as we dive into the intricacies of the box model, and learn why the dev tools are your friend. Remember: if in doubt, inspect the element!How do you break up different css files? What do we mean when we talk about "Critical Path" CSS? What is the "cascade", and how does it impact "specificity"? What are css custom properties and `calc()`? Find out all this and more in this week's rapid-fire instalment of A Question of Code.Mentioned in this episode:Sass (scss)Critical Path CSSITCSSCSS custom propertiesThe CSS Tricks Guide to Flexbox

It's fan-boy o'clock again this week, as one of Tom's web-heroes joins us for a chat. CSS Trickster and ShopTalkin' podcaster Chris Coyier stopped by for a chat about working as a developer. Chris is full of all sorts of useful advice for aspiring developers. For example, you need some experience before you can know what you want from a job. Learn how to be picky after your first job, but get into the industry as quickly as you can. That way you'll learn so much more that you would if you were working by yourself. Get whatever experience you can, as early as you can.We cover a lot of ground in this show. Why does having a personal site gives you a massive advantage? (Having your own website puts you ahead of a surprising number of people; it should be table-stakes, but it's not!) And what does job hunting (and running a job board) look like in the time of CoViD? What will working remotely mean for junior devs in the near future? Find out all this and more in this week's CodePen-tastic instalment of A Question of Code.Mentioned in this episode:Chris on Twitter @chriscoyierShopTalk podcastCSS TricksCodePenChris' excellent personal site

We're joined this week by testing expert (and long-time friend of the show) Brian Okken. Brian literally wrote the book on testing with Python (Python Testing with pytest) and has a lot of strong opinions about the value of testing and testing methodologies in general. Thankfully he's as friendly as he is smart, and was happy to lead us through the sometimes-murky waters of software testing.How did Brian first get into testing, and what advice does he have for those of us just getting started with learning to test our code effectively? What makes a good test (and what makes a bad test)? And what simple questions can you ask to immediately improve your testing game? Find out all this and more in this week's well-tested instalment of A Question of Code.Mentioned in this episode:Brian on Twitter @brianokkenThe Test and Code podcastThe Python Bytes podcastBrian's book, Python Testing with pytestEpisode #22: Why should you write tests?

This week we're joined by Python expert (and super-star podcaster) Michael Kennedy to talk about why Python is such a great language to get started coding with.So why is coding in Python such fun? And why is it so good for beginners and experts alike? Why might Python give you tangible results faster than JavaScript? And once you've learnt some Python, what are your career options? Find out all this and more in this week's pythonic instalment of A Question of Code.Mentioned in this episode:Michael on Twitter @mkennedyTalk Python podcastTalk Python coursesBeginners coursesoftware-carpentry.org

In a tweak to the usual format, this week's show is a frontend-focused rapid-fire question bonanza. Ed's been doing some CSS work this week, and has a lot of questions for Tom (a self-styled CSS expert, whatever that means).What's wrong with `innerHTML`? And for that matter, why is `eval()` so evil? Should you use `px`, `pt`, `em`, or `rem` (or something else) when setting sixes in CSS? What's the deal with browser prefixes (`-moz-`, `-webkit-` etc.)? Are you a bad programmer if you use a z-index of `99999`? (Spoilers: probably). Is it *ever* appropriate to use `!important` in your CSS? Should you use IDs or classes? And to finish with a famously easy question; how do you name things? Find out all this and more in this week's rapid-fire instalment of A Question of Code.Mentioned in this episode:Never use eval()Check if you need a prefix at caniuse.comMindBEMding – getting your head ’round BEM syntax

This week we're joined by Shawn Wang, Senior Developer Advocate at AWS and author of the excellent Coding Career Handbook. Shawn is a career-switcher; he transitioned into tech in his early thirties after a career in finance. He has written a lot about how aspiring devs can better accelerate their careers, and his views are nuanced and full of wisdom that's very relevant to all aQoC listeners (no matter what stage you're at in your career).What does a "developer advocate" actually do, and how do they split their time between internal coding work and external communication work? What does it mean to learn in public, and how should you apply this concept to your personal brand? And talking of personal brands, how can you best market yourself and choose you domain? And what does that even mean for non-celebrity developers? Find out all this and more in this week's rousing instalment of A Question of Code.Mentioned in this episode:The Coding Career Handbooksvelte.devHow to Market Yourself (without Being a Celebrity)Discrimination charges at Pinterest reveal a hidden Silicon Valley hiring problem

Down on your luck? Become a developer! Don't know what to do for a career? Become a developer! Want to earn the big bucks? "Simply" become a developer... We hear this advice all the time, but how much truth is there to it? Can anyone become a developer, and is it a good choice for everyone? And more importantly, is now a good time to transition to a career in programming?We touch a lot of bases in this episode. We ask (again!) if there is a benefit to having a computer science degree, and touch on some hot drama™️ when Ed questions if HTML is a programming language. We also ruminate on the approachability of the frontend. Is it easier than ever to get started creating websites, and is the first-time experience better now for backenders, maybe? And how does the recent explosion in remote working affect junior developers looking for their first gig? Find out all this and more in this week's honest instalment of A Question of Code.