Senior software engineer · Healthcare
Systems that keep working when things go wrong.
I'm Nate Parker. For the past five years I've built and defended the platform at a healthcare software company — mostly Elixir and Ruby on Rails, with a security practice running underneath all of it.
Currently
Senior engineer at a healthcare startup, where I've spent five years on the same codebase — long enough to have opinions about what actually keeps software alive. Right now I'm the primary engineering resource on our push toward a top-tier healthcare security certification, which is turning out to be less about documentation than about engineering.
Outside of that: CTFs, reverse engineering, and a homelab that mostly exists so coding agents have somewhere to work while I sleep.
Writing
3 recentHerdr and the overnight homelab
Coding agents are useful right up until you close your laptop. Here's how I gave mine somewhere to live, and the guardrails I put around them first.
What AI is actually good for in security research
I used an AI agent to audit a widely-used open-source library and it found a real credential leak. The finding was the least interesting part. Here's what the model was good at, where it lied to me, and the harness that kept it honest.
Replacing Clockify with 200 lines of Elixir and a SQLite file
A self-hosted Clockify replacement in Elixir and SQLite — and why the single-running-timer rule lives in the database, not the application.