No one sets out to write bad code, but bad code does exist.
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.
A newbie coder and a seasoned veteran discuss the questions that always come up when someone begins learning to code.
Ed is looking at getting a career in programming and has been learning to code for just over a year. During this time he’s been building up a stack of questions that keep coming up from other newbie coders. Luckily, he’s got someone he can ask for help: Tom. Tom’s a seasoned coder, having worked in the industry for a few years now and has all the answers Ed needs, or does he?