Pharmacy by school, software by conviction

People ask me when I'll pick one: pharmacy or software. The question assumes the two are competing for the same slot. They're not. Pharmacy is my school, software is my conviction, and the combination produces things neither half would on its own.

What pharmacy gives that bootcamps don't

Precision under consequence. In a dispensing lab, a decimal point is a patient. That habit — verifying twice, respecting exactness — shows up in everything I build: schema design, payment flows, data migrations. I treat a production database the way a pharmacist treats a prescription.

Systems that must not fail. Medicine is the study of what happens when things fail. Pharmacy drilled into me that every system needs a failure mode designed on purpose, not discovered by accident.

A different network. Most developers know developers. I know pharmacists, doctors, health businesses — people with problems software can solve but usually doesn't reach.

What software gives pharmacy

The ability to actually build the fix. Health systems around me run on paper, WhatsApp, and hope. Understanding both worlds means I can see a broken workflow and construct the tool that repairs it. Knowing-only-one-side can see or build — not both.

The conviction part

Software is the conviction because it's the transferable half: whatever I practice, wherever I end up, the ability to build tools compounds. The degree grounds me; the craft carries me. Neither is a hobby. Neither is a backup. They're the same career, seen from two windows.