Meet the Team: Danny – Our Developer Placement Student
Get to know the team behind DriveWorks.
The DriveWorks team is rapidly growing, from being a small three man team 14 years ago, we are now outgrowing the biggest building on our Laskey Farm site and moving into the surrounding buildings!
DriveWorks wouldn’t be such a great place without the people that make up our team.
In this series of Meet The Team blogs, you’ll meet the people behind our company, including lots of new team members joining us very soon…
Next to give their story is Danny, a Junior Web Developer at DriveWorks.
Danny has been part of the DriveWorks team for a year now.
Danny was looking for a placement role for the sandwich year of his BSc Web Technologies degree at Huddersfield University when he came across the opportunity at DriveWorks.
So let’s meet Danny…
Huddersfield, West Yorkshire, home of the greats.
I love all things gaming and computers. I own around $3500 worth of PC games and slightly love my mechanical keyboard.
Playing games on PC/PS4, listening to metal and chillstep, cooking, being attached to some sort of technology 24/7 and coding cool stuff for the web.
Three words your friends would use to describe you:
Time at DriveWorks:
Best thing you have done in that time:
Made some fancy custom software for the brilliant DriveWorks Kiosk. It was great to see so many people enjoying using it! Sampling some fine food and booze at the DriveWorks summer party was also a highlight.
What do you enjoy about DriveWorks?
Everything! Everyone is super knowledgeable and passionate about providing the best product they can to make people’s lives easier. It’s a great atmosphere full of friendly people who work hard whilst still taking the time to have a laugh. I’m constantly working with new technologies and learning every single day.
Developer Placement Student
Favourite DriveWorks 12 feature:
Every single thing that went in, because I saw how hard everyone worked on it all!
Favourite overall DriveWorks feature:
The Rules Builder! It’s like code, but inside DriveWorks… mmm code…