sbrown12

100% agree the first step is discovering what exists. Our goal is to make that discovery less intimidating by automating as much discovery as possible.

When a user connects their email address we automatically search for 70 categories of critical documents & bills (ex: property tax, homeowners insurance, life insurance, etc...) so all they have to do is click yes to confirm instead of trying to remember what's important and where it's stored.

The next step is series of simple yes/no questions to help folks remember what critical documents/contacts exist.

If you have other suggestions to make the process less stressful, we definitely want to hear them.

That's a solid approach. I've heard of folks creating a google doc, a password vault, even a binder that's in a safe deposit box. The real challenge is just that so many of us procrastinate and do not invest the time to gather all this information and make sure family know how to access it. That's what inspired me to build LastShelf - to make the process less intimidating and more accessible.

We definitely do not intend to replace estate lawyers or executors who create these documents and manage their execution. Our goal is just make it easier to gather all the critical documents, contacts, bills, etc...and share clear instructions for what to do when so families know what exists and what next steps are during a stressful time.

Hahah, great minds think alike :)

Those are good suggestions. Thanks for sharing.

In our earliest versions we experimented with a dead mans switch, but feedback was that folks would forget to reply to the monthly keep alive and we'd risk triggering too many false alarms. So we opted for picking trusted family members who you grant ongoing read only access. That way in an emergency, they already have the access they need to act.

We're 100% open to the idea of a dead man's switch, just want to find a way to avoid triggering too many false alarms. Any ideas on how to do that?

Guilde (https://guilde.ai) | Staff Engineer + Senior Engineer | Full-Time | Remote (Americas & Canada)

Do you run multiple Claude Code sessions simultaneously, constantly tinker with new prompting techniques, and juggle a half dozen side projects? If you want to live AI all day, every day and build software you actually want to use, join us. We're four repeat founders who previously built StrongDM ($150M from Sequoia). Guilde transforms the firehose of new techniques, tools & models into the future of SDLC.

I'm Schuyler, one of the founders. If you'd like to join us, email hiring [at] guilde.ai with "HN: Staff SWE" in the subject line

What you’ll tackle: * Agentic workflows: deterministic orchestration with retries, audits, and cost controls.

* Eval & policy systems: golden datasets, regression baselines, policy-as-code gates.Integrations: Linear, Datadog, and other developer tools.

Full job description: https://docs.google.com/document/d/1CwaUxALaRYgrxlyqE3CXVIU-...

Thanks for the tip. I’ve been trying to add folks as they arrive in the waiting room. Sorry if I missed you when you were joining!!

Guilde (https://guilde.ai/) | Staff Engineer & Sr Engineer | Full-Time | Remote (US Time Zones)

We’re building the most profound expert in data models. If you’re a Full Stack Engineer who enjoys dogfooding every day, we should talk. Our team will be on this Zoom room from 10:30AM-3PM PST today. Drop in to say hi, see a demo, and learn more about life on the team: https://us06web.zoom.us/j/82464106025?pwd%3Davp2pW8wNeeum1Xs...

We’re a senior team of 3 repeat founders, backed by a dozen CTOs who live this problem daily and want to help build the future. To apply, email: hiring [at] guilde.ai

The details: - Hiring (1) Staff Engineer - Hiring (1) Senior Engineer - Geography: Fully remote in North or South America. - Tech Stack: Golang, Postgres, MCP servers

Some attributes we feel are important: - Bias towards shipping - Creative, optimistic, curious, rigorous, diligent, grit - Must have backend experience operating at scale

Responsibilities: - Creating agentic workflows using our proprietary frameworks & LLMs - Internal tools to extract value from LLMs - Feature development (ex: leveraging SQL AST systems to provide tools to LLMs and users, GitHub code checks for Postgres) - Integrations (ex: Datadog, Slack, etc...)

For anyone interested in trying a bastion host approach, here's a step-by-step guide to spin up a bastion host and enable ssh logging: https://www.strongdm.com/bastion-hosts-with-audit-logging-pa...

Hiya Kevin. I wrote that Inc article. I feel you. How many times have you seen one (or all of these)...

-credentials shared across teams -database credentials stored in plain text config files -unsecured mongodb clusters

I used to think that none of this stuff would change until people were held accountable. Imagine if a data breach at work meant that I had to pay a fine so steep that I had to declare personal bankruptcy...bet that might get people's attention, but I doubt there's the political will to pass laws like that.

Instead, I've spent my time trying to tackle it from the other end of incentives- how do we make security tools easier to adopt than the alternative? The SSO guys have done a great job, but there's plenty more to do.

*Full disclosure, I founded a data security company