The team at AppLearn.
Tuesday
Two new hires joined us last week, so this morning I’m holding the first of many architecture sessions to prepare them for their engineering teams in a week or so. We’ll meet back periodically for the first few months to ask questions and transfer as much domain knowledge as possible. They are both Manchester-based, so today was a good opportunity to be in the office and meet in person. Working over Teams is great, but face-to-face workshops give a little something extra. You really feel part of something exciting!
Analytics are a huge part of our product, whether it’s showing dashboards for execs to review the adoption of their latest tech rollout or being consumed as part of our automatic guide generation machine learning. This afternoon I’m meeting with our Wonderlytics crew of data engineers and scientists. They have an upcoming feature which will double our data ingest, so we are designing optimisations to our data pipeline to handle the load.
This evening will be spent in my garage workshop where I make big pieces of wood into smaller pieces of wood and then stick them back together to make big wood again – you guessed it, I love woodworking! I’m currently building a pair of hardwood obelisks for my wife to use with climbing plants in the garden.
Wednesday
I join our retrospective meetings every two weeks where we reflect on any challenges, and fine tune our processes to improve. These meetings can be a shock to new engineers, but they are highly constructive. It’s where you best see our amazing team work. Total honesty is needed and leaving your ego at the door is vital to us recognising weaknesses and improving.
We are having lunch today at Rudy’s in Ancoats. I love these opportunities to get to know the new members of the team and solidify existing relationships. Rudy’s is a firm favourite in the office, but with so many great restaurants in Manchester, deciding the venue can end in lively debate.
This afternoon I’m writing design documentation, the bread and butter of any Software Architect. Everything must be documented with good context so that engineers in the future know why we did something, and often more importantly why we didn’t do something.
As well as general woodworking, I’m also a walking stick maker. Next week I have an exhibition to attend, so my evenings this week will be spent making sure my stock of beautiful handmade walking sticks are in tip top shape.
Thursday
This morning I have a catchup with our SVP of Technology & Architecture, we’ll discuss progress on ongoing projects across engineering and our longer-term roadmap. We’ll also discuss areas such as recruitment and product. I look forward to these sessions as they are perfect for airing any concerns and for getting advice on my personal development.
I’ve been asked to help with some issues a colleague is having with an AWS service. I have a lot of experience working with this service, so of course I’m happy to lend my expertise. Helping teammates is one of the highlights of my day, it’s great to pair up on a problem and get to the bottom of it.
We are heavily invested in AWS, the breadth of which can seem overwhelming, so I hold regular training sessions to up-skill engineers. This afternoon we’re diving deep into DynamoDb. This is an advanced session, so we’ll dig into topics like partition design, relational data modelling, fine grained access control, and streams. These sessions are a goldmine, the back-and-forth conversation and inevitable brainstorming of domain application, can lead to unexpected discoveries on both sides.
This evening, more walking sticks!
Friday
I’m reworking some architecture around our tenant configuration for features in our strategic roadmap. It’s exciting to be able to look at our existing design, that whilst well considered, was based on different requirements. I’ll strip it back to first principles and then reimagine it as a new design that we can build on for another 5 years. There’s no guarantee we’ll need to make this change, but it’s important to be prepared with some speculative designs, keeping our north star up to date.
I’m working with our Product Owner on an upcoming feature to make sure it’s ready for an engineering team to work on. We’ll explore different implementation options and discuss how they impact the product and the merits of each. High level estimates and identifying risk allow us to build the most important micro features first so that they can be validated by customers and inform the final feature.
I’m spending the afternoon collaborating with colleagues on pieces for our AppLearn Engineering blog. I find writing hard, the words don’t come easily, but it’s super satisfying to refine my thoughts sufficiently enough that I can effectively communicate them.
No walking sticks this evening, as soon as my wife is home from work, we’ll head out to our local for a drink and then maybe something to eat.
