Open in app
Sign inGet started
Top lessons to learn from refactoring code with a headless CMS

Top lessons to learn from refactoring code with a headless CMS

Case Study of a codebase refactor with DatoCMS. Learnings for Engineering teams partnering with Product Managers and stakeholders.
Go to the profile of Gary Butler
Gary Butler
(Forge) Bridge over troubled water

(Forge) Bridge over troubled water

When we used to think about the process of going from digital design to a fully functional webpage, the word “handoff” frequently came up…
Go to the profile of John Price
John Price
Why and how we migrated from Mocha to Jest as our client-side test runner

Why and how we migrated from Mocha to Jest as our client-side test runner

Building reliable and scalable services and applications takes skills and dedication, and we have always had the best intention when…
Go to the profile of Xifeng Jin
Xifeng Jin
Traditions — Sprint Reviews

Traditions — Sprint Reviews

Teams all over the world demo their products everyday. Engineering teams, marketing teams, product design teams, a picture speaks a…
Go to the profile of Showie
Showie
Engineering Traditions

Engineering Traditions

Lately I’ve been thinking a lot about traditions in engineering. Why engineering teams do the things they do. In life, we are members of…
Go to the profile of Showie
Showie
Planning Harry’s 2019 Hackathon

Planning Harry’s 2019 Hackathon

In December of 2019 Harry’s held its annual Hackathon. The two-day event has become a much-adored tradition that enables us to live some…
Go to the profile of Showie
Showie
The Forge: Harry’s approach to the multi-brand component library

The Forge: Harry’s approach to the multi-brand component library

Most component libraries share an origin story. If a company wants to scale, its applications need to start sharing code.
Go to the profile of Mae Capozzi
Mae Capozzi
About Harry's EngineeringLatest StoriesArchiveAbout MediumTermsPrivacyTeams