Watch on YouTube ↗Harvard CS50
A broad, rigorous introduction to computational thinking and programming. Use it as a course, not background entertainment.
A lot of people ask how do I balance medicine with tech? But it doesn't actually requires much effort, with consistency and discipline anyone can absolutely do it.
For apps and websites, learn basic programming and product design. For research and clinical data, begin with Python, statistics and data analysis. For digital health strategy, study how technology is evaluated, regulated and introduced into clinical systems.
Medical school remains the priority. Reserve two or three focused sessions each week for technology. Consistency beats an intense two-week sprint followed by months of silence.
A revision tool, resource directory, call-duty calculator or student communication workflow is a stronger first project than copying a generic tutorial. Solve something you can test with classmates.
Learn enough to communicate clearly, prototype ideas and understand trade-offs. Then work with designers, developers, researchers and clinicians whose strengths complement yours.
Explain the problem, users, decisions, constraints and what changed after feedback. In health technology, thoughtful problem definition is often more valuable than technical spectacle.
A common mistake we all make is telling ourselves we will become rich from doing tech, but that is not something guaranteed for every tech bro. Money matters, but growth, skill, consistency, and problem solving matter first. Focus on becoming valuable, and the income will eventually flow
Watch on YouTube ↗A broad, rigorous introduction to computational thinking and programming. Use it as a course, not background entertainment.
Watch on YouTube ↗Python is useful for automation, research, data and backend development. Follow along and change the examples.
Watch on YouTube ↗Technology is wider than writing app code. Learn how roles differ before choosing where to invest your time.
Watch on YouTube ↗A deeper look at how programs work. Valuable when you are ready to understand more than framework syntax.
Do not aim to “enter tech.” Aim to build one useful thing for one real person, then learn what the next version requires.