Tom Elliott

  • A tale of two alerting mediums

    When creating alerts, there are many factors to consider. What metric will be alerted on? At what point do you trigger an alert? How long should the metric be outside of the alerting range before de-escalating. But until recently, I’d not put much thought into where the alert is sent....

  • Introducing Edward

    Developing a set of microservices applications can be complicated. A lot of attention is paid (rightly) to the deployment process, but getting your development workflow right can be just as important in the context of enabling rapid iteration. One problem we’ve faced at Yext is getting a working environment running...

  • Going all-in with Go for command-line applications

    At Yext, we’ve been using Go for server-side applications for some time, and over the past year we’ve been exploring using Go for building command-line tools as well. In this post, we’ll be exploring what made us adopt go for command line applications, some of the packages that we’ve found...

  • Yext's Road to Continuous Delivery

    As we grow both our client base and our product line-up, the stability of our platform becomes more and more important. But as we grow our engineering team, more frequent commits add greater challenges to maintaining this stability. A reactionary solution would be to add more stringent QA requirements to...

  • Demystifying 'typechecking loop' errors in Go

    A recent addition to the Pages product, Screens is a mobile store locator SDK with a server-side API written in Go. In keeping with our philosophy of full-stack teams, this gave me an opportunity to branch out from the mobile side of things and get my hands dirty with a...