From iPhone games to Scott Logic
My interest in software development started when I was at school writing games for the iPhone. I’ve always enjoyed problem solving and maths, so for me it was a logical step to study computer science at A Level and university, taking part in multiple hackathons while I was there. I came across the Scott Logic graduate developer programme through the Newcastle University career website. It was evident the company had a strong network with local universities and meet-ups. After going through the interview process I was delighted to be offered a graduate developer role as part of the August 2016 cohort, once I finished my degree.
I enjoy my role at Scott Logic; each morning there’s a 15 minute stand-up to discuss current progress and any blockers that we have (but of course the first port of call is the coffee machine!). The rest of the day is usually a mix of writing code, debugging and researching anything I‘ve not come across before.
I enjoy working in an Agile way as the team remains in constant communication. This allows everyone to work effectively and not step on each other’s toes during development. I also like working in pairs, as this allows me to see how others approach and think about a problem, which I may be able to apply to my own thinking.
Since starting my role as a graduate developer I’ve enjoyed constant learning, not just of the newest technologies that we use, but also new development patterns that help me write cleaner and more maintainable code. Everyone I’ve worked with has been helpful and supportive, allowing me to grow as a developer.
I think the DRY principle (Don’t Repeat Yourself) is probably the most valuable thing I’ve learned so far, which has greatly improved the quality of my code. By restricting the amount of repetition in a project, you create more readable and easier to navigate projects, as well as forcing yourself to use better practices. This principle can be applied to almost any part of the project (class structure, data storage etc.).
Coming from university with no other industry experience, I quickly realised the quality of the code I was writing wasn’t production standard. By learning from others during code reviews and talking through problems, this quickly improved. But I had to be willing to accept advice from others. There were also a lot of technologies that weren’t discussed at university that make development a much nicer process, so a willingness to learn is essential to quickly get up to speed.
Read more software stories here, or visit our careers blog here.