A Question of Code

89: Top Tips review: pragmatic learning

Ed & Tom Hazledine — Mon, 16 Nov 2020 20:00:00 +0000

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.

88: Top Tips review: document what you learn

Ed & Tom Hazledine — Mon, 09 Nov 2020 20:00:00 +0000

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.

87: Top Tips review: enjoy what you do

Ed & Tom Hazledine — Mon, 02 Nov 2020 20:00:00 +0000

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.

86: Top Tips review: just get things done!

Ed & Tom Hazledine — Mon, 26 Oct 2020 20:00:00 +0000

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.

85: Top Tips review: why should you build your own website?

Ed & Tom Hazledine — Mon, 19 Oct 2020 20:00:00 +0100

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.

84: Why should you own a rubber duck?

Ed & Tom Hazledine — Mon, 12 Oct 2020 20:00:00 +0100

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.

83: How do you get started with a new framework?

Ed & Tom Hazledine — Mon, 05 Oct 2020 20:00:00 +0100

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.dev
Up and running with Svelte 3 (Egghead.io video course)

82: What is semantic markup?

Ed & Tom Hazledine — Mon, 28 Sep 2020 20:00:00 +0100

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

81: What is an API?

Ed & Tom Hazledine — Mon, 21 Sep 2020 20:00:00 +0100

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:

80: What’s it like behind the scenes of a podcast?

Ed & Tom Hazledine — Mon, 14 Sep 2020 20:06:50 +0100

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.

79: How important are CS fundamentals? (with Vaidehi Joshi)

Ed & Tom Hazledine — Mon, 07 Sep 2020 20:00:00 +0100

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:

78: How can developers get better at design?

Ed & Tom Hazledine — Mon, 31 Aug 2020 20:00:00 +0100

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:

77: Should you use boilerplates?

Ed & Tom Hazledine — Mon, 24 Aug 2020 20:00:00 +0100

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:

76: CSS Revisited (Rapid Fire)

Ed & Tom Hazledine — Mon, 17 Aug 2020 20:00:00 +0100

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:

75: Why do you need a website of your own? (with Chris Coyier)

Ed & Tom Hazledine — Mon, 10 Aug 2020 20:00:00 +0100

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:

74: How do you get started with testing? (with Brian Okken)

Ed & Tom Hazledine — Mon, 03 Aug 2020 20:00:00 +0100

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 @brianokken
The Test and Code podcast
The Python Bytes podcast
Brian's book, Python Testing with pytest
Episode #22: Why should you write tests?

73: Why is Python a good starting point for learning to code? (with Michael Kennedy)

Ed & Tom Hazledine — Mon, 27 Jul 2020 20:00:00 +0100

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:

72: CSS Extravaganza!

Ed & Tom Hazledine — Mon, 20 Jul 2020 20:00:00 +0100

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.com
MindBEMding – getting your head ’round BEM syntax

71: How should developers market themselves? (with Shawn Wang)

Ed & Tom Hazledine — Mon, 13 Jul 2020 20:00:00 +0100

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:

70: Is "become a developer" still good advice?

Ed & Tom Hazledine — Mon, 06 Jul 2020 20:00:00 +0100

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.

69: Why bother with side projects?

Ed & Tom Hazledine — Mon, 29 Jun 2020 20:00:00 +0100

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:

Tom's new newsletter side project: Podcasts for Nerds
Episode #53: What are some good things to build?

68: Are bootcamps worth doing? (with Kirsty Simmonds)

Ed & Tom Hazledine — Mon, 22 Jun 2020 20:00:00 +0100

This week we're joined by Kirsty Simmonds, a developer who has successfully survived a coding bootcamp. We love hearing stories about people who have transitioned into tech from other careers, and Kirsty's tale is a good one.

As well as giving us an honest and fair insight into the mechanics and specifics of taking a bootcamp, Kirsty also has a ton of actionable advice for other people in a similar situation. In fact, it's all good advice for all of us. What parts of the traditional coding job-application did she find worked the best? What are the red (and green) flags you should watch out for when interviewing? And what tips does she have for those of us staring down the barrel of a take-home technical challenge? Find out all this and more in this week's outstanding instalment of A Question of Code.

Mentioned in this episode:

Kirsty on Twitter @torahwilcox
Kirsty's excellent blog post about job searching
Episode #45: Should you take a bootcamp?
Episode # 61: What questions should you ask in an interview?

67: How can developers help fight climate change? (with Natalia Waniczek)

Ed & Tom Hazledine — Mon, 15 Jun 2020 20:00:00 +0100

We're joined for this episode by Natalia Waniczek. Natalia is a web developer building hybrid mobile apps and websites at Elixel. With a passion for environment she's not afraid to voice her opinions and advocate for climate change.

It's easy to assume that working as a web developer doesn't have much of an impact on climate change, but it there are second-order effects that most of us haven't considered. So how does our work impact the environment, and how serious is this impact? What can we do in our day-to-day work to make the situation better? And how can we learn more about this important topic? Find out all this and more in this week's environmental instalment of A Question of Code.

Mentioned in this episode:

66: How do you get started in data science? (with Tom Sainsbury)

Ed & Tom Hazledine — Mon, 08 Jun 2020 20:00:00 +0100

We were joined for this episode by Tom Sainsbury, a neuroscientist who has a wealth of experience in using programming to deal with data. We discuss the ins and outs of "data science" as a discipline, as well as how it intersects with the world of professional programming.

How do you deal with your data when you're collecting 500GB per day? How do scientists interact with code in a lab setting? What uses are there for data science in the wider tech industry? How can you tell a story with data and code? Find out all this and more in this week's scientific instalment of A Question of Code.

Mentioned in this episode:

Pandas
Jupyter Notebooks
Book: R for Data Science, by Garrett Grolemund & Hadley Wickham
fast.ai course
kaggle.com (datasets)
pydata.org
Find Tom Sainsbury on Twitter as @sainsbury_tom

65: Should new developers get involved in open source? (with Jeremy Walker)

Ed & Tom Hazledine — Mon, 01 Jun 2020 20:00:00 +0100

It's an exciting show for Ed this week. If you've listened to almost any of our previous episodes, you'll have most likely already heard Ed spreading the Good News (TM) about Exercism.io - an education platform that combines coding exercises and online mentoring. Ed's used it for ages, and talks about it any chance he gets. In this episode we get to chat with one of Exercism's co-founders, Jeremy Walker.

So what actually happens on Exercism? Who's it for, and what will they get out of it? What does it mean to learn a new programming language idiomatically? How do you "manage" an online community, and how do you deal with the inevitable Bad Eggs? If you're a developer that wants to get involved in open source, where are good places to start? And what is the etiquette around getting stuck in on GitHub repos? Find out all this and more in this week's exercising instalment of A Question of Code.

Mentioned in this episode:

Jeremy Walker
Exercism
Episode #21: How do you get started with open source?
Video: 4 ways that Exercism sucks (and how we're fixing them!)

64: How do you get started with Pandas? (with Boris Paskhaver)

Ed & Tom Hazledine — Mon, 25 May 2020 20:00:00 +0100

This week we were joined by Boris Paskhaver, a software developer, Agile consultant, online educator and author. Boris is based in New York City and has 240,000 students across 6 courses on the e-learning marketplace Udemy with over 1 million minutes of video content consumed monthly. In our discussion we talk about his upcoming book, *Pandas in Action*, as well as his own transition into coding. Boris was a data analyst before he was a software engineer, and found that Pandas was a great bridge between Excel and Python.

So what actually is "Pandas" (spoiler alert: it's "Excel on Steroids" for Python). Why does Pandas make for such a good introduction to coding in general? And would Boris recommend a bootcamp to other people looking to kickstart their tech career? Find out all this and more in this week's Excel-superseding instalment of A Question of Code.

Mentioned in this episode

Boris' book: Pandas in Action
Use code podcodeq20 for 40% off all products from Manning Publications
Pandas
Jupyter Notebooks

63: What is i18n? (with Eli Schutze)

Ed & Tom Hazledine — Mon, 18 May 2020 20:00:00 +0100

This week we're joined by internationalisation (i18n) expert Eli Schutze. Originally from Nicaragua, Eli is a London-based web engineer and speaker currently making money work for everyone at Monzo Bank. In this episode she clears up some common misconceptions around the issue of translating apps and websites. It turns out that doing i18n properly often runs counter to a lot of the principles developers are taught when they learn programming.

Why do we call it "i18n"? (Spoiler: because it's hard to say!) And why do developers need to do the hard work of i18n themselves? Why not just use automated tools? How does i18n work on a technical level, and what is likely to go horribly wrong when developers try to be too "smart"? Find out all this and more in this week's international instalment of A Question of Code.

Mentioned in this episode:

Find Eli on Twitter @elibelly
Monzo Bank
Eli's recent conference talk about I18n: Internationalization is a Piece of Cake
W3C Quick Tips for i18n on the Web
W3C Internationalisation Resource List
Falsehoods Programmers Believe About Names
Pseudo-localization at Netflix

62: What is it like to have a mentor? (with Amber Wilson)

Ed & Tom Hazledine — Mon, 11 May 2020 20:00:00 +0100

This week we got to speak with Amber Wilson. Amber is a front end engineer with 3 years experience and an interest in lots of things to do with the web. Right now she's especially interested in accessibility, security, and performance. And in this episode we were able to grill her about the specifics of having (and being) a mentor.

We've spoken about the power of mentoring a lot on this show, and this episode is a fascinating look into the reality of tech mentoring. How did Amber find her mentor? What does that mentoring look like? And how much does Amber think Find out all this and more in this week's true-life instalment of A Question of Code.

Mentioned in this episode:

61: What questions should you ask in an interview?

Ed & Tom Hazledine — Mon, 04 May 2020 20:00:00 +0100

Let's set the scene. You've landed an interview for your dream job in tech. You've crushed it on the technical evaluation and wowed them at the whiteboard; everything's going your way. At that point, somewhere towards the end of the face-to-face segment, you'll be hit with the following challenge: do you have any questions for _us_?

We _love_ questions here at A Question of Code (surprise, surprise), so of course we've got some advice for that inevitable scenario. There are some great questions to ask prospective employers, and some more risky ones too. So what should you ask your interviewers when you're being interviewed? Is it a good idea to "get all up in their face"? And how can you turn the situation to your own advantage? Find out all this and more in this week's questionable instalment of A Question of Code.

Mentioned in this episode:

Patrick McKenzie's epic piece on Salary Negotion

60: What is a resilient website? (with Jeremy Keith)

Ed & Tom Hazledine — Mon, 27 Apr 2020 20:00:00 +0100

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:

Find Jeremy Keith online at adactio.com
Read Jeremy Keith's books at abookapart.com, including the oldie-but-goldie HTML5 for Web Designers.
Code Bar
Jeremy's band, Salter Cane
webpagetest.org
Jeremy's blog post about Getting Started
Design agency, Clearleft

59: How do you prepare to give a presentation?

Ed & Tom Hazledine — Mon, 20 Apr 2020 20:00:00 +0100

Even though all current in-person have been cancelled, some tech events are still happening. Many conferences are transitioning to being fully-online, and anyone can release anything they like on YouTube (other video hosting services are available).

How do you keep your presentation sounding natural? When pre-recording, what things shouldn't you edit out? What does it mean to move at the speed of thought? Should you have a full word-for-word script? Find out all this and more in this week's presentable instalment of A Question of Code.

Mentioned in this episode:

58: How do you run a remote conference?

Ed & Tom Hazledine — Mon, 13 Apr 2020 20:00:00 +0100

We've talked about organising conferences before (in episode #46). And we've talked about pivoting before as well (way back in episode #31). This week we're covering the mother of all pivots; converting a fully-booked in-person conference into a 100% remote event.

So what needs to change when an event moves online? And what do the speakers have to do to adapt? And, perhaps most importantly, how can an event recreate all the "extra curricular" experiences that make attending a conference so valuable? Find out all this and more in this week's indoor instalment of A Question of Code.

Mentioned in this episode:

Tony Edwards on Twitter
Future Sync conference
Total Fandom podcast
Our show from last year's Future Sync, Episode #20: What is it like to attend a tech conference?
Episode #46: How do you apply to speak at a conference?
Episode #31: Should you pivot?

57: Why is time so hard to work with?

Ed & Tom Hazledine — Mon, 06 Apr 2020 20:00:00 +0100

This week's episode is another deep-dive into a niche coding topic. This time, we're dealing with time. In short, writing code that deals with times and dates is horrible. We're here to tell you that, as a sensible developer, you should avoid it at all costs.

But if you're unlucky enough to actually _have_ to programme with times and dates, what are some of the common pitfalls? What "gotchas" are lurking in the depths? And how can you deal with them in the most effective way (and hopefully not be driven insane in the process)? Find out all this and more in this week's timely instalment of A Question of Code.

Mentioned in this episode

The Problem with Time & Timezones - Computerphile
Internationalis(z)ing Code - Computerphile
Why 2020 Started On December 30th - Tom Scott
The world's silliest time zones - Map Men
Daylight Saving Time Explained - CGP Grey
moment.js

56: How can you make code habitable?

Ed & Tom Hazledine — Mon, 30 Mar 2020 20:00:00 +0100

It is easy to think that when you are writing code your target audience is a computer. But almost all code is more than a simple list of instructions for a machine to follow. A mature codebase is a living, breathing thing that gets touched by many, many developers. So how do we go about writing our code for _humans_?

What does "habitability" mean in a code context? How does the Broken Windows theory transfer to the code you write? And why should you avoid "code golf" at all costs? Find out all this and more in this week's locked-down instalment of A Question of Code.

Mentioned in this episode:

55: Any tips and tricks for effective home working?

Ed & Tom Hazledine — Mon, 23 Mar 2020 20:00:00 +0000

Lots of people are working from home now, and for many it's their first experience of being a remote worker. Ed is in this boat too - it's very new for him, having only worked from home for a single day at the time of recording. Tom, on the other hand, has worked remotely for many years (in some form or other).

So what obstacles has Ed already encountered? Which parts of WFH are worrying him most? And what tips and tricks does Tom have to share from his (and his more qualified and cleverer colleagues) experiences? Find out all this and more in this week's quarantined instalment of A Question of Code.

Mentioned in this episode:

Episode 19: What is it like to be a remote developer?

54: Why do people write "bad" code?

Ed & Tom Hazledine — Mon, 16 Mar 2020 20:00:00 +0000

It's a sad fact of the world that bad code exists. But is this just developers doing their best impression of builders? "Who put this in, mate? It's all got to be ripped out and replaced". Is all old code bad code? Are there reasons that bad code gets written? Are the justifiable excuses and mitigating factors?

If you're just starting out in your coding career you might think that only bad developers write bad code, but the truth is more nuanced than that. As you gain experience you are certain to encounter bad code written for good reasons. So what are the common reasons that bad code gets written? And how can you take steps to avoid it as much as possible in your career? Find out all this and more in this week's incredible instalment of A Question of Code.

Mentioned in this episode:

Ed's appearance on episode 135 of the Cynical Developer podcast

53: What are some good things to build?

Ed & Tom Hazledine — Mon, 09 Mar 2020 20:00:00 +0000

We think that the best way to learn *is* by doing (it works for us, but your milage may vary). So when you are learning to code, what should you be doing? What are good things to build when you're just starting out? It's all well and good to say "Just Build Websites" *(©️ shoptalkshowdotcom)*, but *what* websites?

So what do we think you should build? Do we think different types of project are useful for complete beginners and those with a little bit more experience under their belt? What did we work on when we were first learning? And what do with think are the characteristics of a great self-driven project for learning? Find out all this and more in this week's gorgeous instalment of A Question of Code.

52: What gear do you use?

Ed & Tom Hazledine — Mon, 02 Mar 2020 20:00:00 +0000

We've talked before about the essential equipment you need when learning to code, but this week we take a look at all the tech and tools that we use everyday. Get two nerds in a room and you'll have three opinions about what is the best technology to use. A lot of this stuff is definitely optional, but we get utility from using it nonetheless.

So what kind of equipment gets Ed excited? And which bits of kit does Tom think provide the most value? Which of our hosts spent way too much on the Worlds Best Pencil? Find out all this and more in this week's useful instalment of A Question of Code.

Mentioned in this episode:

51: What is a Minimum Viable Product?

Ed & Tom Hazledine — Mon, 24 Feb 2020 20:00:00 +0000

Creating an MPV (Minimum Viable Product) is a big deal in "startup land". But what are they, exactly? How do they differ from a normal proof-of-concept or technical prototype, and are they a useful part of the development cycle?

MVP is an oft-abused term, but why do people insist on skipping the "viable" part? What should you bear in mind when creating a genuinely useful MVP of your own? Find out all this and more in this week's fortuitous instalment of A Question of Code.

Mentioned in this episode:

Future Sync conference
Cargo Cult on Wikipedia
Mechanical Turk on Wikipedia
SWAPI (the Star Wars API)

50: What's so special about the command line?

Ed & Tom Hazledine — Mon, 17 Feb 2020 20:00:00 +0000

What is a CLI, and what is a GUI? What are the key differences? And why would you choose one over the other? Are there tasks that cannot be accomplished in the command line?

The command line has a steep perceived learning curve, so is it worth the time-investment to learn properly? And is there any benefit to switching to a non-standard shell or terminal application? What are "bash" and "zsh"? Find out all this and more in this week's favorable instalment of A Question of Code.

## Mentioned in this episode:

hackertyper.net
Terminal emulators
Episode #35: What is version control? (GIT)
SourceTree
z-shell ("zsh")
iTerm2
Lynx: a command-line web browser

49: What is a build pipeline?

Ed & Tom Hazledine — Mon, 10 Feb 2020 20:00:00 +0000

At some point you're going to want to put the code you've written onto the internet. In the "bad old days" you should FTP your files onto a server and boom; you've got a working website. Easy peasy. But why don't we work like that any more? What are "build pipelines"? And what do terms like CI and CD stand for? And what do they actually mean? Who or what are Jenkins and Travis?

Do we need to know all these things? (Spoilers: yes, we do!) What are the benefits? Do they help with automation? With testing? With code backups?

The question on everybody's lips is this: why has deployment become so complicated? Find out all this and more in this week's fantastic instalment of A Question of Code.

Mentioned in this episode:

Continuous Integration vs Continuous Delivery vs Continuous Deployment on StackOverflow

48: Agency or product?

Ed & Tom Hazledine — Mon, 03 Feb 2020 20:00:00 +0000

What are the differences between working at an agency and working "in house" for a single company or product? How much does team size factor into the different experiences that the developers have? And is it an issue of design vs. development, or frontend vs. backend? (Spoilers: no, it isn't) And how important are good project managers? (Spoilers: very) Find out all this and more in this week's fabulous instalment of A Question of Code.

47: How do you build a blog?

Ed & Tom Hazledine — Mon, 27 Jan 2020 20:00:00 +0000

We think that every developer should have a blog of some sort. But they shouldn't be hard to create. In this episode we dive into the mechanics of building and hosting your own blog. We run through many of the options and answer the common questions. Why use a blogging tool? What is a Content Management System, and do you really need one? What do we think of the "Off the shelf" options? Are they all garbage, or do some have their uses?

What are Static Site Generators and why are they useful? When are they not the best option? And once you've built your site, where do you put it? Find out all this and more in this week's excellent instalment of A Question of Code.

Mentioned in this episode:

Ed's blog
Episode #24: Should you write about what you’ve learnt?
WordPress.org `!==` WordPress.com
Perch, the "friendly" CMS
Ed uses the Pelican SSG
Tom uses the Eleventy SSG
Markdown(.md), the ultimate style-agnostic markup language
Netlify is awesome for static-site hosting
dev.to is a lovely community for blogging if you don't want to create your own site

46: How do you apply to speak at a conference? (with Tony Edwards)

Ed & Tom Hazledine — Mon, 20 Jan 2020 20:00:00 +0000

AQoC takes on a new flavour this week with the addition of our first ever guest: the magnificent Tony Edwards, organiser of the Future Sync tech conference. Tony tells us all about the history of the conference, and graciously answers a lot of questions about the process of becoming a speaker.

What does a typical talk-application look like? How are submissions reviewed by the FS team? What makes a great talk topic? And why would you even want to give a talk in the first place? Find out all this and more in this week's blithesome instalment of A Question of Code.

As an extra special treat for our listeners, Tony has also created a discount code for tickets to Future Sync 2020. Use the code AQUESTIONOFCODE for 10% off your ticket at checkout.

## Mentioned in this episode:

Tony Edwards on Twitter
Future Sync conference
Future Sync CfP
See Tony speak at Frontend Developer Love conference

45: Should you take a bootcamp?

Ed & Tom Hazledine — Mon, 13 Jan 2020 20:00:00 +0000

When you're pivoting to a career in tech, software bootcamps can seem very attractive. The idea that you can learn to code in three months, and have a guaranteed job at the end of the process sounds too good to be true. But is it? There are a lot of caveats and warning signs to beware of, but are bootcamps a valid option?

In this episode we discuss the specifics of coding bootcamps. Are they worth the cost (both in time and money)? What does Ed (a former teacher) think of the quality of teaching assistants at bootcamps? Does Tom think Income Share Agreements are a terrible idea? And what tricks do some disreputable bootcamps play to boost their "grads in employment" statistics? Find out all this and more in this week's awesome instalment of A Question of Code.

Mentioned in this episode:

44: What is the difference between a framework and a library?

Ed & Tom Hazledine — Mon, 06 Jan 2020 20:00:00 +0000

When coding, we often make use of external tools and snippets to make our life easier. Importing existing code into your codebase is a common occurrence. But what is the difference between code that adds missing features to the language you're using and code that changes the way you structure your application? The crucial difference is that the former are libraries (probably) and the later are frameworks (probably).

Are all libraries small? Are all frameworks huge? Where do we draw the line between them? And what even is jQuery, anyway? Find out all this and more in this week's amazing instalment of A Question of Code.

43: Yearly Themes: 2020

Ed & Tom Hazledine — Mon, 23 Dec 2019 20:00:00 +0000

Throughout 2019 Tom and Ed have both been applying a "Yearly Theme" to their lives. We've talked a lot about the concept of Yearly Themes before, but this episode is a deep-dive into the whole idea.

What were our themes for 2019? Do we think they were successful, and will we be carrying any aspects of them forward into the next year? And, most importantly, what are our Yearly Themes for 2020? Find out all this and more in this week's forward-thinking instalment of A Question of Code.

Mentioned in this episode:

42: What does a developer do all day?

Ed & Tom Hazledine — Mon, 16 Dec 2019 20:00:00 +0000

Every developer's average work day will be different, but there are habits and patterns that crop up all the time. If you're a developer, the chances are you'll have sat (or stood) through plenty of "stand ups" and one-to-one meetings. We've covered "How much time do you spending coding in a coding job?" before, but since then Ed's started his first programming job. Now that both of our hosts have experience of working in a professional coding environment, it's time to deep-dive into the subject.

Do they have regular working patterns? How do they feel about meetings? And how much time do they spend fighting fires in their codebases? Find out all this and more in this week's insightful instalment of A Question of Code.

41: How long does it take to get a job in tech?

Ed & Tom Hazledine — Mon, 09 Dec 2019 20:00:00 +0000

When you've decided you want to get a job as a professional programmer, it can be hard to know how long to expect the learning process to take. We only have two hosts, and while their stories are (hopefully) useful, it's only a small segment of a much bigger picture.

We polled our listeners to find out some of their stories, and specifically asked how long it took them to get their first coding job. Does it take everyone years? Or can it really be done in just a few months? Find out all this and more in this week's temporal instalment of A Question of Code.

The inciting Twitter thread with all the fantastic responses.

40: Can you trust recruiters?

Ed & Tom Hazledine — Mon, 02 Dec 2019 20:00:00 +0000

This week we finally get into a thorny issue that's raised it's head in several previous episodes. What do our hosts think of tech recruiters?

What do recruiters do? Are they useful, and should you use them? Can you ever even trust a recruiter? Are there red-flags you can watch out for? Find out all this and more in this week's engaging instalment of A Question of Code.

39: Do you have impostor syndrome?

Ed & Tom Hazledine — Mon, 25 Nov 2019 20:00:00 +0000

There comes a point in every developer's career when they're afraid of being caught out. Afraid their colleagues will discover that they're a fraud. Afraid that everyone will notice that they don't really know how to do their job - they've just been pretending this entire time. This phenomenon happens all the time, and it's name is "Impostor Syndrome".

So what is impostor syndrome? Should you pay attention to it? Should you be on the look out for it in others? It sounds bad - and it really can be! Find out how to recognise imposter syndrome (and how to deal with it!) in this week's authentic instalment of A Question of Code.

## Mentioned in this episode:

* Martin Shelton's "meta impostor syndrome" tweet

38: If it's not broken should you fix it?

Ed & Tom Hazledine — Mon, 18 Nov 2019 20:00:00 +0000

Every developers wants to refactor all the things all the time. But is it always a sensible decision? How should you deal with "not invented here" syndrome (as much as a problem for programmers as it is for builders and carpenters and plumbers)? And how do you fight the urge to spend all your time fixing old code at the expense of creating something new? Find out all this and more in this week's refined instalment of A Question of Code.

⚡️ Help us, listeners. You're our only hope

Ed & Tom Hazledine — Mon, 14 Oct 2019 20:00:00 +0100

We're hoping to do a "how long does it take to learn to code?" episode, but need more data points than just our own. With that in mind, we're inviting you to tell us your experiences. The best way to get in touch is through Twitter, where Tom has asked this question:

"Self-taught developers: how long did it take you to go from knowing you wanted to be a developer to actually starting work at your first dev job?"

37: When are you ready for a coding job?

Ed & Tom Hazledine — Mon, 07 Oct 2019 20:00:00 +0100

An oft-heard bit of advice is "apply as soon as you can, before you think you're ready". It's good advice, and it's advice we ourselves have given many times on this very podcast. But is it always the case? Can you be too early?

We think you can be. So where is the line drawn? How do you know when you know enough to have a serious chance of getting your first job in the industry? And how do these two conflicting pieces of advice manage to both be correct? Find out in this week's speculative instalment of A Question of Code.

Mentioned in this episode:

Episode 8: When should you quit your job?
Ericsson study: Deliberate Practice (a.k.a. "10,000 hours")
Backend and frontend web developer roadmap (flowcharts)
Baseline for frontend developers (from 2012, so caveat emptor)

36: How do you keep track of your knowledge?

Ed & Tom Hazledine — Mon, 30 Sep 2019 20:00:00 +0100

When learning to code, you need to remember an awful lot of new information. In fact, this is true for every stage of your career. Storing and recalling the things you've learned efficiently is a key skill. Can systems-thinking help with this process? And how do Ed and Tom tackle this particular challenge? At all Find out in this week's recollective instalment of A Question of Code.

35: Do you git it? (What is version control?)

Ed & Tom Hazledine — Mon, 23 Sep 2019 20:00:00 +0100

Ed's been finding something unusual is taking up most of his time at his new job. This week Tom and Ed discuss why you should be using version control everyday, as well as some tips for getting around the nitty gritty parts of git. Should you even be using version control? What does it mean when you add, commit, push and pull?

34: How do you learn a new programming language?

Ed & Tom Hazledine — Mon, 16 Sep 2019 20:00:00 +0100

Having started his new job, Ed has discovered he'll need to learn C#. He's already learned a few different languages, notably Python, and has dipped his toe into the world of C++. So how should he approach having to learn yet another programming language? It's something most developers have to do fairly regularly, so are there any techniques and tips and tricks to help make the process easier? Find out in this week's pedagogical instalment of A Question of Code.

Mentioned in this episode:

Episode 11: When should you change to your second language?
Ed's new keyboard: Filco Majestouch-2
Learn C++
Exercism.io

33: How much tooling is too much tooling?

Ed & Tom Hazledine — Mon, 09 Sep 2019 20:00:00 +0100

Now that Ed is a "professional" programmer, he needs to think seriously about his "tooling". And by that, we mean all the supporting technology that comes alongside actually writing code. Gear lik computers, screens, keyboards, and mice (mouses?) is important, but so is the more ephemeral side of things. Which project-management methodology your company uses has a big impact on what your programming-day looks like. And so to do the software tools you choose.

So how long should you spend automating your build process? How much tooling is too much tooling? At what point do your systems and processes get in the way of actually doing work? Find out in this week's automated instalment of A Question of Code.

Mentioned in this episode:

Automate the boring stuff with Python, book by Al Sweigart
Logitech MX Master mouse
The Agile Manifesto
The Agile Revolution, episode of the Command Line Heroes podcast
The Pragmatic Programmer book by David Thomas and Andrew Hunt

32: How do you prepare for a new job?

Ed & Tom Hazledine — Mon, 02 Sep 2019 20:00:00 +0100

So you've accepted an offer for your dream coding job. You start next week; what should you do between now and then to make sure you're as prepared as possible? There are plenty of options. Do some company research, take on more coding challenges, or commit to learning some new tech. But you've done the hard work already, so you could focus on some well earned R'n'R to make sure you're in the right frame of mind to face those first few days.

Should you set yourself some homework? Or is it better to just sit back and relax? Find out in this week's preparatory instalment of A Question of Code.

31: Should you pivot?

Ed & Tom Hazledine — Mon, 26 Aug 2019 20:00:00 +0100

This week Ed has some news that puts the future of this podcast in jeopardy (spoilers: not really). We talk about that, as well as the concept of "pivoting". What does a career pivot look like? Have Ed or Tom actually pivoted? What does pivoting look like? And how do you know when a pivot is a good idea? Find out in this week's existential instalment of A Question of Code.

⚡️ How much time do you spending coding in a coding job?

Ed & Tom Hazledine — Mon, 19 Aug 2019 20:00:00 +0100

In this lightning question Tom and Ed discuss the work:non-work ratio of coding for a living. When writing code is your job, how much time do you spend actually writing code? How much time gets eaten up by the "other stuff"? Is every non-coding minute a waste of time? How does this compare to other industries?

⚡️ How long should you spend on a take home coding challenge?

Ed & Tom Hazledine — Mon, 12 Aug 2019 20:00:00 +0100

In this lightning question Tom and Ed discuss take-home coding tests, and how much time you should budget for them. Most tech companies will set a challenge as part of their interviewing process. How long do they expect you to take? And is it a useful part of the process?

⚡️ Tabs or spaces?

Ed & Tom Hazledine — Mon, 05 Aug 2019 20:00:00 +0100

In this lightning question Tom and Ed discuss whether or not you should use spaces or tabs in your code. Spoiler alert: "spaces" is the only correct answer.

30: What do you get from going to a tech meetup?

Ed & Tom Hazledine — Mon, 29 Jul 2019 20:00:00 +0100

We often recommend that developers should attend tech meetups. But what does this involve, and is it useful for everyone? Should your level of professional experience effect whether you go to meetups or not? And is "networking" (shudder) the only reason to meet other developers? Is there any point in going to meetups if you're *not* job hunting? Spoiler alert; we both think meetups are great and that everyone can benefit from attending. But tune in to find out our details thoughts in this week's sociable instalment of A Question of Code.

29: What's wrong with developer culture?

Ed & Tom Hazledine — Mon, 22 Jul 2019 21:00:00 +0100

In general, developers are awesome people. Both our hosts have been helped and supported by some fantastically friendly and generous engineers. But there are some bad eggs. And given that we spend a lot of our time online, the nasty folk can be more vocal and more visible. And to make matters worse, we often see the bad characteristics excused by high performance. "A bad person can be valuable to your company if they're really good at code" is often said. But is it logical? Is it helpful to examine the idea of the "developer savant" who is excellent with computers but toxic with real people? Why on earth would you want to be a 10× engineer, if being a 10× engineer means you have to be a sociopath?! Find out all this, and more, in this week's infuriating instalment of A Question of Code.

Mentioned in this episode:

28: How do you stay motivated?

Ed & Tom Hazledine — Mon, 15 Jul 2019 20:00:00 +0100

July is a good time to revisit our yearly goals and motivational tactics. Hey, we're nerds; it's always a good time to talk about organisational systems! We first touched on this topic way back in episode four. Have our options changed since then? Have our opinions changed since then? And are we still finding the same time-management strategies and tactics useful? Find out all this, and more, in this week's motivational instalment of A Question of Code.

Mentioned in this episode:

27: How do you deal with crazy bugs?

Ed & Tom Hazledine — Mon, 08 Jul 2019 20:00:00 +0100

Boy, oh boy; bugs can be frustrating. A tricky bug can often make feel like a bad programmer, but fear not. Bugs happen to everybody. They're an unavoidable part of the coding process, and dealing with them is an important skill. Many coders think debugging is the most versatile and important skill you can learn. How do our hosts deal with their bugs? Are there strategies that help? Are there techniques you can learn to make your life easier? Find out all this, and more, in this week's buggy instalment of A Question of Code.

Mentioned in this episode:

26: What is functional programming?

Ed & Tom Hazledine — Mon, 01 Jul 2019 20:00:00 +0100

Tom is absolutely nuts about Functional Programming. He goes on about it all the time (mentioning it in almost every episode so far!) but Ed doesn't really know what it is. So what is this fancy programming paradigm that's got Tom so excited? And is he able to explain it clearly and succinctly? (spoiler alert: he isn't!). Will Ed be able to make any sense out of Tom's ramblings? We all know that a monad is just a monoid in the category of endofunctors, but do any of us know what any of those words mean? Find out all this, and more, in this week's functional instalment of A Question of Code.

What is functional programming?
Composing Software, book by Eric Elliot
Functional-Light JavaScript, book by Kyle Simpson
Fun Fun Function, YouTube channel by MPJ

25: Do you need to be good at maths to become a programmer?

Ed & Tom Hazledine — Mon, 24 Jun 2019 20:00:00 +0100

It's a common assumption that all programmers are maths wünderkinds. But is that necessarily the case? Many coders do come have a strong mathematical background, but does the correlation imply causation? What is like to learn to code when you've previously been a humanities specialist? Can you get by without any maths at all? Find out all this, and more, in this week's illogical instalment of A Question of Code.

24: Should you write about what you've learnt?

Ed & Tom Hazledine — Mon, 17 Jun 2019 20:00:00 +0100

An oft-heard piece of advice is to "write about what you learn". But what does that actually mean? And who are you supposed to be writing for; just yourself, or for other people in similar situations or following in your footsteps? Find out all this, and more, in this week's literary instalment of A Question of Code.

23: How do you write a good CV?

Ed & Tom Hazledine — Mon, 10 Jun 2019 20:00:00 +0100

A good CV is an important part of finding a job in any industry. But are there specific things you should do to improve your chances in the tech industry? Are there any parts of Tom's old resumés that he's ashamed of? What tricks and tips has he picked up over the years? And does any of Ed's experience carry over from the world of teaching? Find out all this, and more, in this week's educational instalment of A Question of Code.

22: Why should you write tests?

Ed & Tom Hazledine — Mon, 03 Jun 2019 20:00:00 +0100

Ed doesn't have much experience with automated testing for his code. This week he asks Tom about the principles behind testing, and some of the benefits and downsides. Does Tom think Ed should learn how to write tests ASAP? What kind of tests does he find are the most useful? And are there any downsides to writing tests for your code? Find out in this week's inspiring instalment of A Question of Code.

TalkPython podcast
Classic Computer Science Problems in Python, book by David Kopec
Boundaries, talk by Gary Bernhardt
Jest: testing framework for JavaScript
Test & Code podcast

⚡️ What does it mean to be a full stack developer?

Ed & Tom Hazledine — Mon, 27 May 2019 20:00:00 +0100

In this lightning question Tom and Ed discuss the term 'full-stack'. What does it mean and is it even possible for one person to do all the things?

⚡️ How closely should you match a job description before applying?

Ed & Tom Hazledine — Mon, 20 May 2019 20:00:00 +0100

In this lightning question Tom and Ed give you a quick overview of how many of your skills need to match a job description before you apply.

21: How do you get started with open source?

Ed & Tom Hazledine — Mon, 13 May 2019 20:00:00 +0100

Ed has found the world of open source software both intimidating and intriguing. Did Tom feel the same when he started out? What even is open source, anyway? And is getting involved useful for people just starting out on their coding careers? What are some good tactics for getting started? Find out all this and more in this week's enticing instalment of A Question of Code.

20: What's it like to attend a tech conference? (Live at Future Sync)

Ed & Tom Hazledine — Mon, 06 May 2019 20:05:00 +0100

In a new venture for the aQoC team, we took our show on the road. Future Sync is a tech conference keeping you in-sync with the latest digital trends. We attended for a day of talks, interactive exhibitions alongside plenty of networking opportunities throughout the event.

We were able to speak to a whole range of people and get to the bottom of why people attend tech conferences, and what they get out of them. Find out all this and more in this week's pioneering instalment of A Question of Code.

Dylan Schiemann, founder of SitePen web agency and TalkScript podcast. @dylans, TalkScript.fm
Dan Lewis, developer for ARM. @DanTheOrange
Toni Oatway, STEM ambassador. @ToniOatway, STEM Ambassadors
Edwin Love, developer for Headforwards. @edwinjameslove
Christopher Jenner, tech student. @chris_CBI
Ben Everard, co-founder and developer at The Idea Bureau. @_beneverard
Tom's talk: Creating a delay: recreating an analogue delay pedal using the Web Audio API
Paul Rowe, founder of Rowe IT. @roweit, Rowe IT
Toby Parkins, co-founder of software development outsourcing company Headforwards. @tobyparkins, Headforwards
Tony Edwards, Future Sync organizer. @tonyedwardspz, Future Sync

19: What's it like being a remote developer?

Ed & Tom Hazledine — Mon, 29 Apr 2019 20:00:00 +0100

This week Tom tells Ed what it's like to be a remote developer. They talk about accountability and motivation, as well as the importance of Gifs to a happy distributed workplace. Does Tom miss anything about working in an office? How correct (or otherwise) are Ed's preconceptions. Get the full low-down (warts and all) in this week's thrilling enticing instalment of A Question of Code.

18: What's the interview process for a tech job?

Ed & Tom Hazledine — Mon, 22 Apr 2019 20:00:00 +0100

In this episode Tom describes his most recent round of interviewing. What tasks and challenges did he find? How many rounds did he have to go through? And is any of this representative of interviewing in the wider tech industry? Find out all this and more in this week's thrilling instalment of A Question of Code.

17: How do you find a mentor?

Ed & Tom Hazledine — Mon, 15 Apr 2019 20:00:00 +0100

16: When should you specialise?

Ed & Tom Hazledine — Mon, 08 Apr 2019 20:00:00 +0100

When should you specialise in your career? Is specialising even necessary at all? The week Tom lays down some hard-earned wisdom (which Ed is smart enough to unpick and not take too seriously). Does Ed feel like becoming a "specialist" yet? And has Tom learned anything useful from his past (mis) steps? Find out in this week's illuminating instalment of A Question of Code!

15: What happens in a kick off meeting?

Ed & Tom Hazledine — Mon, 01 Apr 2019 20:00:00 +0100

Notion: https://www.notion.so/
Postman App: https://www.getpostman.com/
Our Notion board

14: How do you learn?

Ed & Tom Hazledine — Mon, 25 Mar 2019 20:00:00 +0000

Anki flashcard system: ankiweb.net
Exact Instructions Challenge - Dad makes his children write instructions for making a peanut butter and jam sandwich.
The Evil Genie

13: Project Introduction

Ed & Tom Hazledine — Mon, 18 Mar 2019 20:15:00 +0000

12: Should you get a CS degree?

Ed & Tom Hazledine — Mon, 11 Mar 2019 20:00:00 +0000

11: When should you change to your second language?

Ed & Tom Hazledine — Mon, 04 Mar 2019 20:00:00 +0000

10: Is coding less fun when it’s your job?

Ed & Tom Hazledine — Mon, 25 Feb 2019 20:00:00 +0000

Halt and Catch Fire TV show: https://www.theguardian.com/tv-and-radio/2017/oct/16/farewell-to-halt-and-catch-fire-the-best-show-that-nobody-watched
Startup Podcast: https://www.gimletmedia.com/startup
D3.js: https://d3js.org/

9: Where do you find jobs?

Ed & Tom Hazledine — Mon, 18 Feb 2019 20:00:00 +0000

Indeed: https://www.indeed.co.uk/
StackOverflow Job Board: https://stackoverflow.com/jobs
Joel Test: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/
CodePen job board: https://codepen.io/jobs
Angel list: https://angel.co/
West London Coders: https://www.meetup.com/West-London-Coders/
GitHub: https://github.com/
Future Sync conference: https://futuresync.co.uk/
Hired: https://hired.com/
Talent.io: https://www.talent.io/

@aQoCode

@edPython

@thomashazledine

8: When should you quit your job?

Ed & Tom Hazledine — Mon, 11 Feb 2019 20:00:00 +0000

Picobel audio wrapper: https://github.com/tomhazledine/picobel

@aQoCode

@edPython

@thomashazledine

7: Where do you learn?

Ed & Tom Hazledine — Mon, 04 Feb 2019 20:00:00 +0000

Refactoring UI, by Adam Wathan & Steve Schoger: https://refactoringui.com/book/
Automate the Boring Stuff, by Al Sweigart: https://automatetheboringstuff.com/
CSS Tricks: http://css-tricks.com
Stack Overflow: https://stackoverflow.com/
Medium: https://medium.com/
Flask Mega Tutorial, by Miguel Grinberg: https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-i-hello-world/
CS50: Introduction to Computer Science: https://online-learning.harvard.edu/course/cs50-introduction-computer-science
FunFunFunction with MPJ: https://www.youtube.com/channel/UCO1cgjhGzsSYb1rsB4bFe4Q
Level Up Tutorials: https://www.leveluptutorials.com/
Dan Abramov on Egghead.io: https://egghead.io/courses/getting-started-with-redux
Michael Kennedy's Talk Python Training: https://training.talkpython.fm/
PyBites: https://pybit.es/pages/challenges.html
Kyle Simpson's You Don't Know JS: https://github.com/getify/You-Dont-Know-JS)
Software Cornwall: https://www.softwarecornwall.org/
London Python Coding Dojo: http://ldnpydojo.org.uk/
Exercism.io: https://exercism.io/

6: What tools do you need?

Ed & Tom Hazledine — Mon, 28 Jan 2019 20:00:00 +0000

VS Code: https://code.visualstudio.com/
PyCharm: https://www.jetbrains.com/pycharm/
iTerm 2: https://www.iterm2.com/
Prettier: https://prettier.io/
Vim: https://www.vim.org/
- Vim talk: https://www.youtube.com/watch?v=wlR5gYd6um0
Moom: https://manytricks.com/moom/

5: Which language should you learn first?

Ed & Tom Hazledine — Mon, 21 Jan 2019 20:00:00 +0000

Import antigravity https://www.xkcd.com/353/ ‘it just works’
Node_modules meme: https://www.reddit.com/r/ProgrammerHumor/comments/6s0wov/heaviest_objects_in_the_universe/
Laravel: PHP framework https://laravel.com/
Gatsby: React static site generator https://www.gatsbyjs.org/
JS frameworks and libraries
- React.js: https://reactjs.org/
- Vue.js https://vuejs.org/
- jQuery (rest in peace, old friend): https://jquery.com/
Code Combat: https://codecombat.com
freeCodeCamp: https://www.freecodecamp.org

@aQoCode

@edPython

@thomashazledine

4: How do you manage your time?

Ed & Tom Hazledine — Mon, 14 Jan 2019 20:00:00 +0000

Cortex podcast: https://www.relay.fm/cortex
Toggl time tracker: https://toggl.com/
#100DaysOfCode: https://www.100daysofcode.com/
Todoist: https://todoist.com/
Omnifocus: https://www.omnigroup.com/omnifocus/
Todo MVC: http://todomvc.com/
Tom’s bullet journal blog post: https://tomhazledine.com/bullet-journal-revisited/
Triggers by Marshall Goldsmith: https://www.amazon.co.uk/Triggers-Creating-Behavior-Lasts-becoming-Person/dp/0451497864/

@aQoCode
@edPython
@thomashazledine

3: Freelance or full-time?

Ed & Tom Hazledine — Mon, 07 Jan 2019 20:00:00 +0000

This week Tom and Ed get to grips with freelancing and working full time. What are the pros and cons of each? Which is the best way to start a career? Is working for yourself necessarily better than working in a big company? Ed finds out which he’s going to aim for first.

2: Frontend or Backend?

Ed & Tom Hazledine — Mon, 31 Dec 2018 20:00:00 +0000

Bootstrap - https://getbootstrap.com
Web developer roadmap: https://github.com/kamranahmedse/developer-roadmap

1: Why are you learning to code?

Ed & Tom Hazledine — Mon, 24 Dec 2018 20:00:00 +0000

Tom on Twitter: https://twitter.com/thomashazledine
Ed on Twitter: https://twitter.com/edPython
A Question of Code on Twitter: https://twitter.com/aQoCode
Python: https://www.python.org/
Book: Godel, Escher, Bach: An Eternal Golden Braid by Douglas Hofstadter https://www.amazon.co.uk/dp/0465026567
Book: Flow: The Psychology of Happiness by Mihaly Csikszentmihalyi https://www.amazon.co.uk/dp/0712657592
Course: Harvard CS50x: Introduction to Computer Science https://www.edx.org/course/cs50s-introduction-computer-science-harvardx-cs50x

Trailer: A Question of Code

Ed & Tom Hazledine — Mon, 24 Dec 2018 19:00:00 +0000

Why should you listen to our podcast? Check out our trailer with Tom and Ed!