Clinical software is where a provider's time goes to die. We are building Axo to make the software layer as invisible and ambient as possible, letting clinicians direct 100% of their attention to patients rather than screens.
Our first market is orthotics and prosthetics (O&P), the field designing braces and artificial limbs that restore human mobility and underserved by the tech sector. We're building a foundation designed to eventually scale across thousands of providers and multiple medical specialties.
You’ll join as a founding engineer working directly with myself (Xoogler SWE) and my co-founder (one of the US's best known O&P clinicians), and a new engineer. You will own massive surfaces end-to-end, making the foundational architectural decisions for our entire platform. We have clinics using our suite and already saving hours a day, but we've got a massive pipeline ahead and need your help to build it. And we participate in humanitarian missions to expand prosthetic access in critical parts of the world like Ukraine.
- The Stack: C#/.NET, contract-first gRPC, SolidJS/TypeScript, and PostgreSQL, built with strict domain-driven design and rigorous testing.
- How we work: We have total flexibility on your workflow. Love AI-assisted speed coding? Go for it. Prefer to write by hand because your mental model is faster than prompting? Perfect. We only care about delivering safely and quickly.
- Requirements: Senior-level depth with production systems, a strong habit of domain modeling, and a philosophy that defaults to simplicity. Strong UI/UX experience with an obsession for user simplicity is a must.
To apply, email me directly at [email protected] with a short story about a favorite technical challenge you solved end-to-end. Please put "HN" in the subject line!
Liked this post a lot, well done! Definitely appreciated that it was a site that actual has a unique design, and isn't just another Medium article...
A book on a similar subject that I don't see mentioned very often but which I quite enjoyed as "Tough Things First" by Ray Zinn [0]. Not the most popular one, but really down to earth and approachable ideas. Kind of like PG's "do things that don't scale," just applied on a broader timescale.
It really was/is a gem of a museum, very fun to visit and quite approachable. We went a couple times, once when they had some fly-ins that made it extra special.
This. I definitely agree with this statement at this point in AI-assisted development. This gets at the "taste" factor that is still intrinsically human, especially in software engineering. If you can construct and guide the overall architecture of an application or system, AI can conceivably fill in the smaller feature bits, and do so well. But it must have a strong architecture and opinionated field in which to play.
I've had at least 256GB on my phones for the last couple of generations after having had to deal with storage issues beforehand, and it's been much nicer.
But I picked up a 16e for my son a few months ago, with 128GB, and yes, we're running into issues with storage space when it comes time to do an OS update. Between local music and photos storage, base storage, and the image for the new update, two or three times now we've had to delete stuff temporarily in order to get the update going. So I'm happy the new base is 256GB, at least that will probably last us a couple more generations before ~~640KB~~ 256GB is enough for everyone.
I’d love to see an article about designing for agents to operate safely inside a user-facing software system (as opposed to this article, which is about creating a system with an agent.
What does it look like to architect a system where agents can operate on behalf of users? What changes about the design of that system? Is this exposing an MCP server internally? An A2A framework? Certainly exposing internal APIs such that an agent can perform operations a user would normally do would be key. How do you safely limit what an agent can do, especially in the context of what a user may have the ability to do?
Anyway, some of those capabilities have been on my mind recently. If anyone’s read anything good in that vein I’d love some links!
Xoogler here (so I can’t help with any changes or feature requests now unfortunately) but yes, all of Google runs on Gmail. The amount of email I got as a software engineer there was crazy voluminous. I and most Googlers around me made heavy use of filters, labels, and all the text search operators available (see https://support.google.com/mail/answer/7190?hl=en&co=GENIE.P...). I also learned to operate Gmail purely via the keyboard with the built in keyboard shortcuts.
I’d occasionally have the frustration of not finding what I was looking for, but usually if I combined a search with at least one other operator (who it was from, what label it might have received, etc.) I almost always found what I was looking for pretty quickly.
And as for the signature image attachments thing, I think that’s actually an artifact of how the sender compiles the email, not Gmail. The “has:attachment” operator is one I use a lot and is usually quite reliable.
Hey @code_brian, would Tavus make the conversational audio model available outside of the PALs and video models? Seems like this could be a great use case for voice-only agents as well.
Just a plug for the book this content is derived from, Noam Wasserman's "The Founders Dilemmas." It lays out so many facets of startup decisions that deserve thought from the outset to prevent issues. It also strikes a good balance IMO between being based in statistics and research, and including anecdotes from actual experiences that bring the statistics full circle. I'd highly recommend it.
I’ve never been on the Spotify train, but with an all-Apple household, including HomePod Minis in multiple rooms, I’ve been stuck in iTunes/Apple Music land. We own our music, which is nice. And I dutifully pay the $24.99 per year for iTunes Match so that I can tell Siri what to play on HomePods, but I will be 0% surprised when they deprecate that service.
Anyone have a good non-Apple way of getting Siri to play songs from a personal music collection on HomePods? My kids use it most.
Clinical software is where a provider's time goes to die. We are building Axo to make the software layer as invisible and ambient as possible, letting clinicians direct 100% of their attention to patients rather than screens.
Our first market is orthotics and prosthetics (O&P), the field designing braces and artificial limbs that restore human mobility and underserved by the tech sector. We're building a foundation designed to eventually scale across thousands of providers and multiple medical specialties.
You’ll join as a founding engineer working directly with myself (Xoogler SWE) and my co-founder (one of the US's best known O&P clinicians), and a new engineer. You will own massive surfaces end-to-end, making the foundational architectural decisions for our entire platform. We have clinics using our suite and already saving hours a day, but we've got a massive pipeline ahead and need your help to build it. And we participate in humanitarian missions to expand prosthetic access in critical parts of the world like Ukraine.
- The Stack: C#/.NET, contract-first gRPC, SolidJS/TypeScript, and PostgreSQL, built with strict domain-driven design and rigorous testing.
- How we work: We have total flexibility on your workflow. Love AI-assisted speed coding? Go for it. Prefer to write by hand because your mental model is faster than prompting? Perfect. We only care about delivering safely and quickly.
- Requirements: Senior-level depth with production systems, a strong habit of domain modeling, and a philosophy that defaults to simplicity. Strong UI/UX experience with an obsession for user simplicity is a must.
To apply, email me directly at [email protected] with a short story about a favorite technical challenge you solved end-to-end. Please put "HN" in the subject line!