scottishbee

Yes. There was a massive hand-wringing about cable TV for instance. And cordless phones (much less car phones!).

Build user-facing prototypes with your real data.

Every startup/company I work for I've had to jury rig ways to get new product ideas in front of users. Google sheets, Grafana boards, Chartio (RIP), etc all to go "SQL query" -> "user-accessible website". For some reason Retool doesn't have a "make externally available to these people".

So I'm playing around with how to build a generic interface between db and user access panel.

27. I don't think you do disagree. Read point 29: Hire and rely on product engineers. They have full-stack technical skills needed to build a product along with customer obsession. Yes, this means they need to talk to users, do user interviews, recruit tests for new features, collect feedback, do support, and respond to incidents.

Ornaments? Parents keep asking for my kid's to "create" an ornament. The fun of doing on paper is obviously great, but it'd be neat to convert it into something more durable too.

That...is not how mortgage servicing companies operate.

I think your question is really: "how do I find people to interview?"

First, find out where your prospects actually spend time. LinkedIn is garbage for a lot of industries. Most doctors don't change jobs much or building "personal brands", so they're not scanning LinkedIn often. Reddit can also be often a better community.

Second, don't cold message people. Put out HELPFUL (not clickbait) content. It can be as simple as a question ("hey, I'm wondering how people solve X?"). Let the community come to you. Then follow up with the people that engaged with your content. They've shown an interest in your topic AND a willingness to engage.

At the end of every call, ask two questions: can you follow up with them with further questions and is there anyone they can think of that would be helpful to learn more? For that second question ask them, IN THE CALL, to write an intro email/message connecting you. Social validation is critical.

Finally, actually follow up. 1-4 weeks later message an update, thank them for their perspective and connection, and again ask if there's anyone they can think of to learn more from.

Neat-o. We're standing up a standard sandbox and something like this would be helpful. Lots of...interesting data types (Tolkien quotes?). What's it like adding some custom data types (eg domain) and getting them anonymized?

> can we show your production average latency comparies to other applications?

This is pretty standard: many companies explicitly add contract language to NOT be included in these benchmarks. The reasons should be obvious, offering these benchmarks on increasingly narrow segments walks right up to betraying competitive information.

source: I work at another observability company where we DON'T share our customers information with each other