September 21, 2026
•
3 min
😷 Doctor: “I don’t need to reinvent the wheel. I follow the latest medical guidelines, developed by thousands of researchers before me.”
🤓 Developer: “Why would I build a login system from scratch? There’s already a package that has been doing it securely and thoroughly tested for years.”
Both professionals build on the work of others rather than starting from scratch every time. Doctors rely on published guidelines and years of clinical research. Developers rely on open-source packages and tools that have already been used and improved by thousands of others.
The problem arises when a developer simply adopts functionality from a package written by unknown developers somewhere in the world. Or when developers routinely add packages without realizing that healthcare requires an extra level of care. Not every library is built with medical safety and privacy in mind.
The power lies in reusing critically: relying on proven building blocks, while always assessing them within the context in which they are used. Just as a doctor doesn’t blindly follow a guideline, but considers whether it is appropriate for a specific patient.
That’s why care is essential when developers choose which tools and packages to use, and why evaluation is just as important as it is for a doctor assessing a new guideline before applying it.
🟢 TodayTomorrow creates human-centered technology for the healthcare of tomorrow. In the Developers & Doctors series, we share fascinating insights into our collaboration with healthcare professionals.