Like myself, my code is thoughtful and thorough. I’m a little obsessed with keeping elements readable, flexible, and bullet-proof. I also possess the ability to interpret and (in most cases) improve the final deliverable if the comps are incomplete / inconsistent.
The part of the job that changed the most. I don’t use one agent, I run a crew: fanned out, verified, and gated wherever a human has to sign off. Most of what matters here isn’t the model. It’s the context you hand it, and the guardrails around what it’s allowed to finish on its own.
I’ve worked in everything from hacked websites to state/school intranets, startup prototypes, and enterprise apps. I love everything about programming and the processes that support it. I’m also a read (and write) the docs kinda guy.
Building healthcare software means the regulation isn’t a checklist at the end. It shapes the schema, the roles, and the audit trail from the first commit. PHI sets the floor, payments add PCI on top, and most of the real work is deciding what data we refuse to hold in the first place.
My roots stem from a background in traditional offset printing. I’ve moved well beyond the mindset of print media, but still love a letterpress piece when I see it. I understand the differences between themeing a marketing site, and building components that make up a software UI. I’ve shipped hundreds of deliverables in every form one could think of.
I’ve worked remote since 2009, so distributed work isn’t a policy I adapted to. It’s the only way I’ve ever done this. These days the job is more hiring, 1:1s, and defending a roadmap than it is writing code, but the habits are the same: async by default, written down, and disciplined, honest, vanish-proof™.
I depend on these tools daily. Some are kinda ugly (but super useful), and most are stunning & fun to use.
I love tech, but it doesn’t take much to keep me happy. This is my standard issue when i’m in (and out of) the office.