Joined 10 years ago
The promise of really cheap AI sounds amazing and is amazing. People will happily accept and engage with "free stuff"; but, I presume you are not starting a business to give away free stuff. Unless you have some model that let's you capture value some other way. e.g. Meta just gave everyone a small computer for free with Muse. Or have some sustainable price advantage on the underlying compute e.g. you are nvidia and make it yourself at scale.
I think you deserve to be compensated for your work! It's hard to make a sustainable business when selling something that costs $5 a month to developers (just seeing your calculator). There aren't that many of us, and AWS/GCP/Azure/Cloudflare have our credit cards already. If it were me, I'd be trying to figure out how to charge more and sell the value of the work you are enabling your customers to accomplish, not the cost of the underlying electrons.
Keep it up!
You guys are operating in a very competitive space. This stuff is fun to build, so a lot of engineers will end up building it. Not to discourage you, but I suspect it will be difficult to capture much value selling this offering as its going to be race to the bottom against very well funded alternatives that can sell these features at a loss in order to get you to use their databases and other offerings that are higher margin and stickier.
As you guys learn more about how to take this sort of technology to market, you may consider trying to get closer to the actual work that people actually need these agents to do. What can you do better because you have this technology? For example, I work in healthcare administration and we have built our own agent sandbox infrastructure on top of firecracker microvms that solve similar use cases as Agent37. We will never sell it. It's part of our competitive advantage for doing healthcare tasks.
Food for thought! Good luck!
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!
I mean this question fairly as I am curious how you think about the trade-offs on the way to your moral choice. Not trying to manufacture a “gotcha” or anything.
Based on your response, I am inferring and assuming that you think electric vehicles are a net positive for society when compared to internal-combustion-engine cars (I was afraid to type ICE as to not accidentally upset some other political dispositions).
I am also assuming: - Tesla’s are high quality EVs - Tesla’s are amongst the most widely available and affordable EVs in the US, the worlds second largest car market
Then a bit more speculative but I’d also argue that Tesla is somewhat responsible for bringing forth the EV transition around the world as I don’t think the other manufacturers would be there had it not been for Tesla going first (but who knows).
And lastly would callout that Tesla is a large 20+ year old organization with thousands of people who have worked there and contributed to their success and proliferation of EVs.
So, given all this. How do you consider the trade-offs that lead you to say that the moral choice is to shun Tesla as a whole because of the actions of a loud, politically-decisive CEO?
At which level of political involvement does the CEOs actions weigh more than the collective contributions of the rest of the organization?
What would you say if EV adoption as a whole takes a huge long-term hit because people stop buying the most well known EVs available in the US for political reasons? I do frown a bit when thinking that one man’s politics will cause a large tribe to change their actions in such a way that we fail to reach the end state that we claim to value.
Essentially, I’m curious how you weigh “I really don’t like the CEOs politics” with “I more or less agree with the mission of the company” and how that leads you to your perspective on the moral choice.
PS. I am not a shareholder of any musk properties, mostly because I avoid meme stocks, and do not nor have ever worked at his companies. In general, I feel pretty neutral towards the whole ordeal.
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!
> 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!
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!
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!
