Our monthly Hack days are such a great initiative at Secret Escapes. So, having recently changed to a more technical role, I jumped at the chance to take the reins and participate in our May Hack day (my first) alongside other members of the SE Tech team.
I saw this as a great opportunity to try out a new challenge. Plus, as you have to present your findings back to the team at the end of the two day event, it’s also a good way to get more experience presenting to a wide ranging technical audience.
My feelings before Hack day…
Having never done a Hack day before, I was a bit apprehensive about what to expect.
Initially, I was a little nervous about what the scope of my proposed project to tackle should be, with only two days of hacking to crack it (technically a day and a half, as the second half of day two, is presenting your findings back to the business!)
I was also a bit concerned about potential blockers I might encounter, but overall I was quite excited to have the freedom and flexibility to shape the project as I liked and take some time away from the day to day to explore and play around with new tools.
Prepping for Hack day…
The project I chose to work on was around experimenting with different data diagramming tools to see if they would be fit for the current data landscape at Secret Escapes.
We are currently upskilling, as well as hiring more analysts within the business, and I thought having some clear annotated diagrams of our datasets for new starters would be a great resource to give a basic overview of the data landscape.
1) I selected the dataset to use
2) I decided upon some success metrics with these tools which I could then use to score each tool I tried against
3) I did some research on the tools out there, read some blogs and from this decided on which tools I was going to try out
So, how did it go?
All in all, a really good experience! At first, it felt a bit alien to be extracting myself from the regular day to day project/backlog work and look into something completely new.
I particularly enjoyed being able to determine the scope of work. If I ended up being interested in a specific aspect of a tool I could spend more time investigating this further, while at the same time if at first glance I knew a tool wouldn’t be suitable for SE I could write up my findings quickly and move on.
I spent the most time looking into the first tool just to get familiar with the dataset and how to navigate the process, but once I got going I ended up looking at more tools than I expected. Not all of them worked and some of them worked very differently from what I’d read but I enjoyed the discovery component.
Presenting back to a Technical audience was interesting as it’s not something I do very often (I usually present to either non-technical stakeholders or within my own Data team). Overall, I received positive feedback on my approach and presentation.
In terms of the next steps, I’ll be kicking off wider discussions within the team as to whether we look into using any of these tools to improve our documentation.
What I learnt…
- Prep is key – If I hadn’t made those decisions upfront, I probably would have used up a lot of the first day working through these.
- Stuff won’t work – One of the tools I was looking at that I thought was quite promising tried to overwrite our current setup in the backend – not my intention at all!
- You need to make quick decisions – you’re working on a tight schedule so you don’t have time to sit around and deliberate. For example, in one tool I was trying to work out how to connect Snowflake directly to a system to import the table DDLs, but after 30 mins with little success, I decided to park it and moved on to the next tool.
Would I do it again?
I would 100% do it again, and I’d encourage anyone else who is thinking about it to give it a go!
It was quite empowering to be given the freedom and flexibility to pick and run a mini project outside of the day job to work out.
The experience will definitely stand me in better stead to have more informed and confident conversations on the tools out there.
And, it was pretty fun to try out some new tech too!
Want to join our Tech Team? Find your next opportunity now!