The code examples are full of variables like "q" "a" and "v" -- it slows down everything as we must grok the surrounding statements like some kind of Rosetta Stone to interpret what "a" could possibly be in this context.

Please fix it.

There. Fixed that for you.

They have this great feature to help you ensure the correct size based on othe brands+sizes you already have.

That one feature alone helped me gain confidence in a buying decision I otherwise would not have made.

And we have consensus on this?

Otherwise they're just making accusations without any defense from repudiation.

I know just the person...

Dead. All dead.

So unless you spend all day writing compilers from scratch or calculating Pascal's Triangle, please stop with the ridiculous CS questions in interviews.

Software Engineering is more of a trade, and requires vocational knowledge and experience. A mountain of theory may not always be required to Get Shit Done.

One thing that I use MailCatcher for is its REST API. I can easily check for new messages from tests (eg: Cucumber).

I don't see anything about that for MailHog on its github page.

Also, I'd like to share my favorite email-related development tool, MailCatcher [0]

Running these kinds tools as part of a docker-compose setup locally makes a huge difference, especially for end-to-end testing.

[0] https://mailcatcher.me/