It's a $600,000 car. I don't think they're widening access.
12,215 karma · joined March 28, 2007
Passion Project: SeekHiFi.com, BuildHiFi.com
LinkedIn: linkedin.com/in/wademeredith
d13b2ac1c6b22c9a1557ee5a5dd4f41855f65133
Many of them orchestrated the situation.
I like this analogy, but I'll be replacing Honolulu with The Moon when I steal it in the future.
We build the market-leading SaaS platform for the home care industry: scheduling, billing, payroll, CRM, and clinical documentation for agencies across all 50 US states and 6 countries. ~10,000 baby boomers turn 65 every day; the agencies using our software help them stay in their homes.
We're are small, fast teams that have gone deep on AI-augmented development. Not as a talking point; as the actual way we work. We prototype aggressively, put working software in front of stakeholders before a traditional process would finish a PRD, and iterate from there. We're looking for engineers who already work this way: driving agents on real codebases, maintaining quality when the machine is doing the typing, and knowing when to throw the output away.
Stack: PHP (backend), React + TypeScript (frontend), MySQL, RESTful APIs, AWS. You'll work across the full stack.
Senior (5+ yrs): Product-minded, systems-thinking engineers. You'd lead 1–2 engineers while still taking substantial features from concept to production solo. You mentor others in code design, systems thinking, and driving AI agents effectively.
Mid-Level (2+ yrs): This is a senior-track role. You'll ship real features with mentorship from senior and staff engineers who are deeply invested in your growth. We want engineers who see where things are heading and want to get ahead of it; going deep on architecture, design, and understanding the problems, not just writing the code.
Both roles: We want concrete evidence you use AI as a real tool, not a novelty. Push the tools until they fail, then tell us about it. We care about quality software that's easy to change, clear writing, and engineers who get curious about the customers, not just the tickets.
Compensation: Salary TBD based on experience. Medical/dental/vision covered in full for the employee. Company-provided equipment.
Apply with a brief resume and a cover letter (written or video — video goes to the front of the line). The cover letter matters; we read it first. Tell us what you've built, how AI has changed the way you work with specific examples, and why this team at this moment.
Candidates only, no recruiters. Feel free to reach out directly via email to wademeredith [at] axis care [dot] com if you have questions. Apply through the website.
What? In my experience people who are good at their job can get it done in a reasonable amount of time. Working 12 hours a day is obsession, no competence. There can be overlap, but there is no causation.
On one hand I intuitively think this is correct, on the other hand these very concerns about technology have been around since the invention of... writing.
Here is an excerpt of Socrates speaking on the written word, as recorded in Plato's dialogue Phaedrus - "For this invention will produce forgetfulness in the minds of those who learn to use it, because they will not practice their memory. Their trust in writing, produced by external characters which are no part of themselves, will discourage the use of their own memory within them. You have invented an elixir not of memory, but of reminding; and you offer your pupils the appearance of wisdom, not true wisdom"
Most certainly not. The hollowing out of classifies by Craigslist in 2000s is what killed most local newspapers.
I've wanted this for a long time, so I finally started building it. I've had a lot fun!
- Graph-based signal flow: Products become nodes, connections are edges inferred from port compatibility (digital, analog, phono, speaker-level domains)
- Port profile system: Standardized port definitions (direction, domain, connector, channel mode) enable automatic connection inference
- Rule engine: Pluggable rules check completeness, power matching, phono stage requirements, DAC needs, and more
This series of articles is gold.
Unsurprisingly, writing good software with AI follows the same principles as writing it without AI. Keep scopes small. Ship, refactor, optimize, and write tests as you go.
I feel like this is the real key. LLMs are good at some things and bad at others. Deterministic logic (e.g. don't ever do "x") is not one of them.
From the Show HN rules: "Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs. Make a regular submission instead."