This post is about things I wish all eval tools provided (but many don’t).

Over the last couple of years, I’ve used several different eval tools, from home-grown and pre-release products, to open source and startup-built tools with wide adoption. Most of them had inconsistent features at best, and glaring omissions for what I thought were obvious features, at worst.

Now, to be fair, what I’m asking for from an eval tool is kind of a lot. I want something that can

Recently, I’ve been surprised to note how many companies aren’t just returning to offices (ugh, open offices are the worst!), but are still actively unwilling to do remote work well.

Here are some hints for things that I’ve learned can be helpful, after working remotely for a few years at a variety of companies - some that were remote-first or remote-only, and some that didn’t have mature practices around it:

Some folks love doing demo days, but I find it sometimes gets in the way of actual work, creates more work in the long run, and/or can be downright demoralizing (especially to backend teams). Here’s why.

What is demo-driven development?

• Building something specifically to be able to show it off

• Rushing to get stuff in before an arbitrary deadline

• A way to get people motivated by an audience (positive) or shame (negative)