RxSharp

Dev journey

Building in Public:
Why I'm Documenting This

I'm a pharmacist. I manage an infectious disease infusion clinic. I did not go to school for software development, and until recently, I had no real reason to think I would be building websites, games, or anything that required me to stare suspiciously at HTML files.

Then I started building Dosecraft.

Dosecraft began as a way to make infusion education feel less sterile and less forgettable. Patients are often handed information in the least human format possible: dense paperwork, medical jargon, and a quick explanation while a lot is already happening around them. I wanted to see whether some of that education could be made more interactive, more visual, and maybe even a little fun without turning it into a gimmick.

That simple idea dragged me into the web development swamp.

Not a bad swamp. Interesting swamp. But still a swamp.

Why write about it?

Mostly accountability.

It is easy to tinker forever. Rename things. Redesign things. Switch tools. Start over. Convince yourself you are still planning when really you are circling the same idea again.

Writing makes that harder. It forces me to explain what I am building, what broke, what I learned, and what I am trying next.

There is also something worth documenting about learning software development as a clinician. Most beginner coding content assumes the goal is to become a developer. That is not really my goal.

The goal is not to become a programmer. The goal is to build useful things around healthcare, pharmacy, patient education, and the weird little systems that shape how care actually happens.

What this site is for:

RxSharp is my personal and professional home base. It is part bio, part project hub, part public notebook, and part experiment in learning how the web works when you actually own the domain and the files underneath it.

For now, I expect to write about building Dosecraft, learning web development, pharmacy workflows, patient and caregiver education, and ideas that are too early to be businesses but still worth exploring.

That last category matters. Not every idea needs to become a company. Some ideas need to sit on the workbench for a while. Some need to be written through. Some need to be tested in small, low-pressure ways before they deserve a logo, a domain, or another monthly subscription quietly nibbling at my bank account.

This site gives those ideas somewhere to live.

What I am not pretending:

I am not pretending this is a polished portfolio. I am not pretending I know exactly what RxSharp becomes. I am definitely not pretending that learning to code with AI tools is effortless. It can be helpful, but it can also feel like having a very confident assistant who occasionally hands you a map to a city that does not exist.

The point is not perfection. The point is to keep building, keep learning, and keep turning vague ideas into something visible enough to judge.

More soon.

← All posts