A little about the person behind the pixels
I'm DP.
Doctor by training.
Developer by curiosity.
I work at the intersection of medicine and technology — building useful digital tools, solving real problems, and learning by making things.
Scroll to get to know meTwo worlds.
One curious mind.
My name here is simply DP. I’m a doctor, and I’m also someone who enjoys understanding how things work — then building something better when I can.
Medicine teaches you to pay attention to people, evidence, detail and consequences. Software gives you a way to turn ideas into tools that can be used, tested and improved. I’m interested in what happens when those perspectives meet.
I keep my personal and professional identifiers private online. The work can speak for itself without publishing my full identity, workplace or college.
Care for people.
Care about how things work.
Different disciplines, connected by the same instinct: understand the problem before trying to solve it.
THE CLINICIAN
Medicine keeps me grounded.
Working as a doctor means dealing with real people and real-world constraints. It shapes how I think about usefulness, clarity, responsibility and the cost of getting details wrong.
THE BUILDER
Development lets me make.
I design and build websites, data-driven tools and small applications. I enjoy the whole loop: identifying a need, exploring an approach, writing code, fixing what breaks and making the result easier to use.
SO, WHY drdp.dev?
A small name
for a broad workbench.
Dr. reflects my medical background. DP is the name I use here. .dev is the place where the building happens.
Put together, drdp.dev is my corner of the internet for experiments, practical projects and tools that are worth sharing.
It isn’t a large company or a faceless product studio. It’s an independent space where I can follow a problem from first idea to a working release — and keep improving it over time.
From a real-world friction
to something that works.
I’m interested in practical outcomes more than technology for its own sake. My process is iterative, hands-on and rarely finished after the first version.
Notice
Find a recurring problem, an awkward workflow or information that should be easier to use.
Understand
Break the problem down. Check assumptions, data, constraints and what a useful result would look like.
Build
Turn the idea into a working tool, with attention to its interface, reliability and the details people actually use.
Refine
Test, listen, fix, simplify and repeat. A useful product gets better through deliberate iteration.
Principles over
personal branding.
I don’t need the internet to know everything about me. I want it to be clear what I build, why it exists and what you can expect from it.
Useful beats flashy
Good design should make a tool easier to understand and use — not distract from its purpose.
Clarity is a feature
Explain what a project does, where its information comes from and what its limitations are.
Build in the open, protect the person
Share the work, ideas and learnings while keeping personal identifiers and workplace details private.
Keep learning
Every project is a chance to understand a new problem, improve a skill or discover a better approach.
THE WORK CONTINUES
Curiosity is good.
Making something from it is better.
Explore the projects, see what’s useful, or get in touch with a question or suggestion.
A doctor who builds.drdp.dev