Web development is more than code, it is my way of creating art.
I’m Diego Zepeda, a Fullstack Developer, Software Engineer and Computer Science graduate from Tecnológico de Monterrey.
I specialize in responsive, end-to-end web products: clear screens, simple flows, and, when the project needs it, APIs and services that match what the UI promises.
JavaScript and TypeScript are what I know best (browser apps and Node-style backends). I also use Java, Python, Rust, Go, and other languages when the job calls for it, and I learn new stacks fast when a team works differently from what I’m used to.
Underneath the API layer, I try to match the database to the problem instead of forcing one pattern everywhere. Relational SQL fits structured, table-shaped data with clear constraints. MongoDB or Firebase fit when documents or a managed backend are the simpler path. Neo4j is what I reach for when the product is really about relationships-graphs, not rows. Whatever the store, the goal is the same: a clear model, and endpoints the UI can trust.
I care about speed, code that doesn’t turn into spaghetti as the product grows, and keeping patterns consistent so the rest of the team can move.
Whether it’s a marketing page, a dashboard, or an internal tool, I focus on solid UI basics layout, loading and error states, basic accessibility, and wording that matches what the app actually does so people can finish what they came to do without getting lost.
How I started coding
At 13, my brother introduced me to HTML and CSS, laying the foundation for my coding journey. I independently pushed into advanced CSS and animations, then React and the surrounding tooling. That early focus on how things look and behave still shows up in how I work today, together with APIs, real world limits (time, performance, legacy code), and whatever language the project uses.
View PortafolioMy traits
I’m organized and I like to work in small steps: split a big task into pieces I can finish and show soon, get feedback, then keep going instead of hiding work until something huge is “done”.
When requirements change, I keep the UI and the backend in sync (for example, matching API shapes and screens so nothing breaks quietly). I improve performance when it’s actually slow for users, and I clean up code or tooling when it’s clearly slowing the team down.
I learn new codebases and business areas quickly, and I’m used to code reviews, planning meetings, and owning a feature with others instead of working in a silo.