Originally posted on Hatch Blog
Year 2 for the Hatch Engineering team is already in the rear-view mirror and work on feature/2020 has begun. We gained a new engineer, Steve, said goodbye to our Product Manager, John, and made strong progress on our 2019 focus; here are the highlights and what we want to focus on this year.
- Grew the engineering team to 4 with the hire of Steve
- Got very close to removing our legacy app Choo (2 views to go!)
- Made great progress on our 2019 goal of Product Engineering. Engineers are participating much more in design and discovery
- The investment in our design language paid dividends, improving the efficiency of front-end work as well as allowing design to hand over rough sketches for engineers to build .
- Transitioning to React hooks
- Our processes are always being retro’d and improved but we feel we have found a good balance of planning, rituals and GSD.
- Breaking apart our code bases into packages of a Lerna monorepo to aid in build times and code sharing between projects (api-client!!)
- The entire happy path journey is in now in product (for company users and students).
- Now that we have the happy path journey in product we have a much better understanding of what the journey looks like, as well as a lot of history of what our unhappy paths look like. This learning will help us to improve our modelling of the process to better facilitate future changes as well as facilitating the manual processes for our unhappy paths. These changes will also help reduce the complexity of the system.
- At the moment we have a monolith API project and a monolith App project. CI build times are 13 minutes for the app (15 minutes to fully deploy) and 6 minutes to build the API (30-40 minutes to fully deploy due to deploying and running e2e tests). We have laid the groundwork converting them to Lerna monorepos and hope to reduce the build times (especially locally) by separating out packages in both projects.
- As the team grows focusing on maintaining developer productivity is crucial. A few pain points we know about and will work on are: our test data for the service tests, re-working code to the current standard and paradigm if we touch it in a meaningful way.
- With flexible work a continuing mega-trend this decade, we want to make sure remote working is built into our culture. Whilst we aren’t remote first Hatch does embrace flexible working (work from home Wednesday!) and a number of the engineering team are planning remote work trips this year. Whilst internally we are comfortable working together remotely, we want to lean into ensuring our remote practices and interactions with the wider team are equally as second nature as it is internally.
- More blogging!!
Most excited for in 2020
- 2020 is all about growth at Hatch and we are super excited about helping our new marketing team crush their growth goals!
- As we transfer our matching learning into more robust systems we are starting to integrate our data science code into our primary code bases. This adds interesting and new technical challenges as we embrace polyglot code bases.
- From a technical perspective, automating our back-office integrations in 2020 is an exciting new challenge.