Joshua Bates was a late addition to the Turinglab delivery team. He joined after the BJSS Academy recognised that his skills in Angular were suited to the Turinglab learning platform and that the engagement would be valuable to his development.
He had previously worked on a similar stack, so without even touching the platform, Josh had a good idea where everything was. “It was a good transition,” he explains. “I could get stuck in right away without having to learn where everything was. I had used this stack before – but on a much smaller scale than the Turinglab platform.”
While Josh was fortunate to have previously worked on a similar stack, he is still learning new things. A massive learning experience came in the form of Cross-site request forgery (CSRF). Having never heard of the term before, Josh had to read up and learn how to do it. CSRF is a type of attack that happens when a malicious website or email causes a browser to perform an unsolicited action on a trusted site. “It isn’t really a massive issue on the application,” he explained. “But it could become a problem in the future, so we thought it best to resolve it at this early stage of the project.”
This is a BJSS delivery, so there are standards and tools that were deployed to benefit the project and to maintain our strict quality standards.
“The first thing I did when was to roll out coding standards to the code base,” said Josh. “Standards are important because they tell the developers how they must write their code instead of leaving it them to interpret themselves. With coding standards, everything is formalised.”
He added: “Some of my team have also been working on guidelines for Continuous Integration (CI). It’s a development practice that requires developers to integrate our code into a shared repository several times a day. It means that what we create is tested on an environment other than our computers.”
When asked what the delivery team was doing to improve the application, Josh described that the best applications are coded accurately. While this might sound like an obvious statement, it means that the code shouldn’t only do its job well, but it should also be also easy to add to, maintain and debug. The Turinglab delivery team is applying BJSS best practices to make sure that this is the case.