We're looking for a backend-leaning fullstack dev. You will be one of the first engineers outside of the founding team. Here is a bit more about us: We're a seed stage AI startup backed by top tier investors. We're on a mission to ensure every patient gets covered for the care they need and every doctor gets paid for the work they do.

We’re building deep, vertically integrated technology systems to solve fundamental problems in US healthcare - the biggest market in the world ($5T). We use AWS, K8s, React, and Rust but there is no requirement to have prior experience with them specifically. We'll teach you!

We are a founding team made up of ex-YC, Amazon, Meta, Microsoft, and Harvard Business School with previous successful exits.

You’ll own entire product areas and be expected to play a true full-stack role, with the ability to go from customer need to end-state product. You’ll work directly with the CTO at the edge of what's possible with LLMs and agentic systems applied to a hard domain. You'll contribute to technical strategy, make real architectural decisions, and write vast amounts of production code with AI first developer workflows. Most importantly, the technology you build will have real impact on real people - clinics staying open, clinicians getting paid, patients getting care.

This is an opportunity to work in a fast paced, high ownership environment while solving real problems in healthcare.

We're happy to share more details on the role in person/on zoom. Please fill out this form if interested!

https://wgwx7h7be0p.typeform.com/to/LV0t8OjI

> Wang was brought in 9 months back to lead the Meta's SuperIntelligence Lab, but now looks like Zukerberg is building a parallel lab called "Reality Labs" with Bosworth

Reality Labs is there AR/VR play, no?

I love the expressivity of Rust, but compile times are a problem.

Someone with some sway, please convince a hyper-scalar to support something like https://borgo-lang.github.io/. I think it may be the AST that we all need.

I have churned from CC in favor of codex until the scrolling bug is fixed. There is no set of features that will convince me to switch back until they fix their broken UI.

I haven’t dug into the JS code base but I imagine they will have a hard time matching the performance of the rust based codex.

Would be cool if I could somehow constrain a chord to a key then enumerate the scale degrees that I want so I can make some real funky sounds that don't fit the standard Chord Qualities.

The pattern I keep seeing is that I ask it to iterate on a design document. It will, but then it will immediately jump into changing source files despite explicit asks to only update the plan. It may be a gemini CLI problem more than a model problem.

Also, whoever at these labs is deciding to put ASCII boxes around their inputs needs to try using their own tool for a day.

People copy and paste text in terminals. Someone at Gemini clearly thought about this as they have an annoying `ctrl-s` hotkey that you need to use for some unnecessary reason.. But they then also provide the stellar experience of copying "a line of text where you then get | random pipes | in the middle of your content".

Codex figured this out. Claude took a while but eventually figured it out. Google, you should also figure it out.

Despite model supremacy, the products still matter.

Nice to see them support it officially; however, OpenAI has officially supported this for a while but, at least historically, I have been unable to use it because it adds deterministic validation that errors on certain standard JSON Schema elements that we used. The lack of "official" support is the feature that pushed us to use Claude in the first place.

It's unclear to me that we will need "modes" for these features.

Another example: I used to think that I couldn't live without Claude Code "plan mode". Then I used Codex and asked it to write a markdown file with a todo list. A bit more typing but it works well and it's nice to be able to edit the plan directly in editor.

Agree or Disagree?

We're looking for a backend-leaning fullstack dev. You will be one of the first engineers outside of the founding team. Here is a bit more about us:

We're a seed stage AI startup backed by several top tier VCs. We're on a mission to ensure patients get the coverage they deserve from their health insurance.

We’re building deep, vertically integrated technology systems to solve fundamental problems in US healthcare - the biggest market in the world ($5T). We use AWS, K8s, React, and Rust but there is no requirement to have prior experience with them specifically.

We are a founding team made up of ex-YC, Amazon, Meta, Microsoft, and Harvard Business School with previous successful exits. We have a 6+ month customer waitlist and growing insanely fast.

We're hiring our first engineer outside the founders. You'll work directly with customers to understand their needs, design the right solution, and build from zero to one. You'll own entire parts of the roadmap and tech stack while wearing multiple hats. Most important characteristics are resilience, work ethic, and curiosity. We care about slope, not where you are today.

This is an opportunity to work in an insanely fast paced, high ownership environment while solving real problems in healthcare. We're happy to share more details on the role in person/on zoom. Please fill out this form if interested!

https://wgwx7h7be0p.typeform.com/to/LV0t8OjI

We're looking for a backend-leaning fullstack dev. You will be one of the first engineers outside of the founding team. Here is a bit more about us: We're a seed stage AI startup backed by several top tier VCs. We're on a mission to ensure patients get the coverage they deserve from their health insurance.

We’re building deep, vertically integrated technology systems to solve fundamental problems in US healthcare - the biggest market in the world ($5T). We use AWS, K8s, React, and Rust but there is no requirement to have prior experience with them specifically. We'll teach you!

We are a founding team made up of ex-YC, Amazon, Meta, Microsoft, and Harvard Business School with previous successful exits. We have a 6+ month customer waitlist and growing insanely fast.

We're hiring our first engineer outside the founders. You'll work directly with customers to understand their needs, design the right solution, and build from zero to one. You'll own entire parts of the roadmap and tech stack while wearing multiple hats. Most important characteristics are resilience, work ethic, and curiosity. We care about slope, not where you are today.

This is an opportunity to work in an insanely fast paced, high ownership environment while solving real problems in healthcare.

We're happy to share more details on the role in person/on zoom. Please fill out this form if interested!

https://wgwx7h7be0p.typeform.com/to/LV0t8OjI

No dogma. If you want an error per module that seems like a good way to start, but for complex cases where you want to break an error down more, we'll often have an error type per function/struct/trait.

A few questions:

On your site it says, "MindFort can asses 1 or 100,000 page web apps seamlessly. It can also scale dynamically as your applications grow."

Can you provide more color as to what that really means? If I were actually to ask you to asses 100,000 pages what would actually happen? Is it possible for my usage to block/brown-out another customer's usage?

I'm also curious what happens if the system does detect a vulnerability. Is there any chance the bot does something dangerous with e.g. it's newly discovered escalated privileges?

Thanks and good luck!

I acknowledge your bear case and hear the possibility that it's all hype and the aggregate value of all generative AI (measured in dollars) will be worth less than e.g. the market capitalization of a single company like Uber.

BUT, hear me out. Forgive me, as I fallback to healthcare... The US spent ~$4.9 trillion on healthcare in 2023 alone (according to CMS). That cost is spread out across a lot of things, some of which is work that things like AI can help make more productive, some of which is not applicable to AI. When we are spending nearly ~$5 trillion dollars a year, it does not take a lot on a percentage basis to start seeing really significant dollar values in savings.

It's a story of death by 1000 cuts. I suspect it won't be a big magical fix all at once where AI magically solves healthcare. But we will optimize 1% here and 1% there using focused solutions that actually solve pain points. If someone improves productivity in healthcare by even just 1%, one-time, then we are talking about savings of ~50bn per year.

For example, I work in healthcare and its difficult to over-exaggerate how much time it can take to do the most basic things. The people that are tasked with doing those basic things are often highly-educated, highly-skilled, and highly-paid; and it still takes a long time.

I suspect there is an unreasonable amount of cost to shed from doing simple things. Things like:

1. Reading, reasoning over, and copying structured data from lightly-structured, highly variable documents like PDFs.

2. Reducing the amount of time a human sits on hold on the phone. I'm of the opinion the AI doesn't even need to do the talking to deliver huge amounts of value. Just help me help my highly-skilled employees move from high-value task to high-value task without the tedium in the middle.

3. Login and copy basic details from any of the 1000s of healthcare specific websites, each of which does more or less the same thing, slightly differently. RPA has always been so costly to build and maintain. The high variation fan-out just got a lot easier.

In the short term, I'm most bullish on AI to solve these low-value, highly-variable, highly-annoying tasks. I'm also reasonably confident that the AI we have today is already good enough to do it.

Give it time and we'll start to see companies operate at margins that were previously impossible in industries that we thought were near-impossible to make more productive.

With that said, there is undoubtedly still room to innovate on the long-tail of RPA. In the healthcare domain, for example, there are 1000s of sites that might need to be scraped occasionally, somewhat transactionally as e.g. a new patient comes in. However, there are other sites that need regular attention and even the smallest of errors can be catastrophic.

The combination of browser-use & workflow-use seems like a really natural fit for such use cases. Nice work!

We've also experimented with the self-healing ideas you are playing with here. In our case, we wrote a chrome extension that connects to an LLM of your choice as well as a process running locally on your machine. You write a description of the job to be done, click around the browser, and then click "go". The extension grabs all the context, asks the LLM to write a typescript program, sends that typescript program to the local process where it is compiled & type-checked against our internal workflow harness, and then immediately allows you to execute the program against your existing, open browser context.

We've found that even this basic loop is outrageously productive. If the script doesn't do what you expect, there is a big "FIX IT" button that lets you tweak and try again. For the record, we're not a competitor and have no intention of trying to sell/offer this extension externally.

I suspect one of the harder parts about this whole ordeal will be how to integrate with the rest of the workflow stack. For us, we've really appreciated the fact that our extension outputs typescript that seamlessly fits into our stack and that is more easily verifiable than JSON. The TS target also allows us to do nice things like tell the self-healing bot which libraries will be available so that e.g. it can use `date-fns` instead of `Date`. We've also thought about adopting more traditional workflow tools like Temporal to manage the core workflow logic, vending out the browser connectivity remotely. Curious how you guys are thinking about this?

Rooting for you guys, we will be sure to keep an eye on your progress and consider adopting the technology as it matures!

PS. If you like things like this, want to work at a growing health-tech startup, and live in Boston, we're hiring! Reach out here: https://wgwx7h7be0p.typeform.com/to/LV0t8OjI

We're looking for a backend-leaning fullstack dev. You will be the first engineer outside of the founding team. Here is a bit more about us:

We're a seed stage AI startup backed by several top tier VCs.

We're on a mission to ensure patients get the coverage they deserve from their health insurance.

We’re building deep, vertically integrated technology systems to solve fundamental problems in US healthcare - the biggest market in the world ($5T). We use AWS, K8s, React, and Rust but there is no requirement to have prior experience with them specifically. We'll teach you!

We are a founding team made up of ex-YC, Amazon, Meta, Microsoft, and Harvard Business School with previous successful exits. We have a 6+ month customer waitlist and growing.

We're hiring our first engineer outside the founders. You'll work directly with customers to understand their needs, design the right solution, and build from zero to one. You'll own entire parts of the roadmap and tech stack while wearing multiple hats. Most important characteristics are resilience, work ethic, and curiosity. We care about slope, not where you are today.

This is an opportunity to work in an insanely fast paced, high ownership environment while solving real problems in healthcare.

We're happy to share more details on the role in person/on zoom. Please fill out this form if interested!

https://wgwx7h7be0p.typeform.com/to/LV0t8OjI

One project I’ve seen that I don’t think is particularly active but that I really like the ideas behind is borgo. It compiles to go (thus GC) but is decidedly more rustacean.

Check it out. I hope someone makes something like this wide spread.

https://borgo-lang.github.io/

PS. I have no affiliation with borgo, just an online fan.

We're looking for a backend-leaning fullstack dev. You will be the first engineer outside of the founding team. Here is a bit more about us:

We're a seed stage AI startup backed by several top tier VCs.

We're on a mission to ensure patients get the coverage they deserve and providers get paid fairly! To do so, we're debugging core problems in the US healthcare system with a modern tech stack and AI. We use AWS, K8s, React, and Rust but there is no requirement to have prior experience with them specifically. We'll teach you!

We are a founding team made up of ex-YC, Amazon, Meta, and Harvard Business School with previous successful exits. We also have a 6+ month customer waitlist!

We're hiring our first engineer outside the founders. You'll work directly with customers to understand their needs, design the right solution, and build from zero to one. You'll own entire parts of the roadmap and tech stack while wearing multiple hats. Most important characteristics are resilience, work ethic, and curiosity. We care about slope, not where you are today. This is an opportunity to work in an insanely fast paced, high ownership environment while solving real problems in healthcare.

We're happy to share more details on the role in person/on zoom. Please fill out this form if interested!

https://wgwx7h7be0p.typeform.com/to/LV0t8OjI

My first foray into using MCP was via Claude Desktop. Would be great if you packaged your tool such that one could add it with a few lines in their ‘~/Library/Application Support/Claude/claude_desktop_config.json’

A good problem to solve when you need to, but for many of my projects, which admittedly don’t grow into big organizations, I find myself valuing the simplicity of the reduced toolkit.

Will definitely check this out.