5 top tips for aspiring software developers

The Engineering team at Salable build a product specifically for entrepreneurial SaaS developers—so, in addition to being developers themselves, they're pretty well-versed in the world of coding careers. We asked Jay, Salable Engineering Team Lead, and Coner and Luke, Senior Software Engineers, what advice they'd give to up-and-coming developers, and we've distilled their wisdom into these five essential points.

Whether you're just starting out or looking to refine your skills, these tips will set you on the right track to success.

Mastering the basics is vital for any aspiring software developer. While it's tempting to jump straight into trendy frameworks or cutting-edge technologies, a solid understanding of core programming concepts will serve you well throughout your career.

As Jay explains: 'Don't just become a framework developer! It's great to see a new generation learning React, but I worry that some don't know where to start with just sending some data over the internet or writing vanilla JavaScript. The development landscape is constantly changing, and it's impossible to stay on top of absolutely everything, but understanding the basics makes picking up new tools and languages so much easier. When hiring, I don't necessarily look for people who know the exact set of tools; I want people who are just good engineers and have the fundamentals—because then you'll always be able to adapt.'

There's no substitute for hands-on experience. The more you code, the better you'll become. Be curious, start with small projects, and try more ambitious ideas as your skills improve. And don't be afraid to make mistakes—it's all part of becoming a more proficient developer.

Coner says: 'I think this ties in with learning the fundamentals. For me, the best way to do that is really just to build a lot. Avoid getting stuck in "tutorial hell"—what I mean by that is it's far better to come up with a project idea and start experimenting rather than just following a step-by-step that someone else has put together. Honestly, it's a lot more fun that way, and you learn so much more from when things go wrong!'

Debugging is a skill that separates good developers from great ones. It's not just about fixing errors; it's about understanding how your code works—and why sometimes, it doesn't! Familiarise yourself with debugging tools and techniques, and develop a systematic approach to problem-solving.

Coner believes this is only going to become more important: 'Everyone is talking about AI's growing code capabilities, but you can't rely on that without a solid knowledge of how to debug. The joke is you can write the code in three minutes using AI, then spend three hours debugging it!'

Jay adds: 'Exactly. Sure, AI can spit out some code for you pretty easily, but actually understanding it and being able to debug, tweak, optimise, and scale it? That's the skill you need.'

On that note, it's crucial not to rely on AI as a crutch. It's a tool like any other, and all tools have their uses—AI can be helpful for suggestions and speeding up certain tasks—but it isn't a replacement for a well-rounded coding skillset. The most valuable developers are those who understand the 'why' behind every line, and that's something AI alone can't provide.

Luke cautions: 'In some ways, I think overreliance on AI is just a more insidious version of tutorial hell! Tutorials are by definition limited in scope, whereas with AI, you can flex it a bit, so maybe you feel more like you're progressing and learning new things. But it's not actually made you a better engineer when you take away the AI "training wheels", because it isn't helping you to truly understand what you're building.'

Whether it's creating a game that fills a gap in the market, building a website for a cause you support, or developing an app to solve a personal problem, working on projects that genuinely interest you makes everything easier and more enjoyable. This applies when you're just starting out and when you're job hunting further into your career.

Luke summarises his approach: 'Engage more with the product side of engineering. Writing code with a purpose makes the work more rewarding. Don't get me wrong, I enjoy writing code in itself, but if you see your job solely as moving tickets from the "to do" to the "done" column, there's really a ceiling on how enjoyable that can be. When you're more personally invested in a product, and understanding your users and what they need, seeing your work deployed and actually making the product better feels a lot more fulfilling. So, find something you're interested in working on—it doesn't necessarily have to be something you'd use yourself. Just find something where you think "That's a problem worth solving, and I can be part of solving it".'