It was the first year at Hatch for the entire engineering team as we took over the reigns to build out the MVP into a mature product. We’ve merged the 2018 pull-request and have already started work on the feature/2019 branch. Here are some highlights and struggles from our 2018 retro.
- Launched the Hatch API
- Migrated the Company User side of the product to React
- Converted the front-end projects from Flow to Typescript
- Added lights to all the hardware 😉
- Laid a solid foundation for the Hatch Engineering Culture
At the beginning of 2018 we pushed a little hard on shipping product which led to some quality issues both in the code and for the customer. A team focus for 2019 is ensuring we are leaving the code better than we found it and improving the effectiveness of our code reviews.
At Hatch we have an amazing cross-functional team that focuses on user-centred design. All engineers at Hatch are Product Engineers and in 2019 we want to get better at that.
Specifically we want to
- improve the communication with design, partly by focusing on our design language
- increase our interaction with our customers
- improve how we break down and understand the complexity in our epics