Make the problem visible
Good delivery starts before the first component. I name the users, constraints, and decision that matters.
About
Understanding the problem matters as much as writing the code.
I’m Jackson Ochoa. I’m a fourth-year Medicine student, and in parallel I work across software engineering, bioinformatics, and operating systems.
Medicine trains you to read a system you did not design — a body, an incomplete clinical history — and find what is wrong with partial information. I bring that same discipline to software: before touching code, I understand the domain, the data available, and what is at stake if I get it wrong. The stack changes with the problem; that discipline does not.
Keep complexity useful
Architecture should make the next change safer, not turn today’s work into a ceremony.
Prove the edges
Tests, accessibility, security, and honest content are part of the product—not cleanup after it.