What is technical debt? I'm not sure a complete answer exists, but here is a story I've been telling in job interviews of a canonical example of tech debt. A couple of years ago on my now-laid-off team, we reworked our flagship feature, moving from version 1 to version 2... Like many web apps, ours has a front end and a back end, with an API that sits between them. We completely reworked the UX on the front end, and in the process we also made big improvements to the front end API client.

What is Selenium? Doing some job interviews I'm surprised more test folks don't know what Selenium actually is, or what it actually does or how it does it, so here is a little thread. First, Selenium is a World Wide Web Consortium (W3C) standard. That means that if you are a browser vendor (Google, Microsoft, Apple, Mozilla, Opera) and you want to comply with web standards...

I kind of want to do a thread about build-test-deploy pipelines and why automated end-to-end tests are a critical part of the process. So... First you have to write some code. You'll do whatever you do to make sure the code itself is sound. This is usually some combination of code review and unit tests. Your pipeline starts with running those unit tests.