I don’t believe “that’s just how it is” is a good enough answer.
I’m Ryan Weinstein, a future aerospace and computer engineer from Mesa, Arizona. I’m drawn to difficult systems, the people inside them, and the small decisions that make something feel trustworthy—or frustrating.
Not to be difficult for the sake of it. I want to understand the choices underneath what people experience—and whether those choices still deserve to be accepted.
I believe good engineering starts with respect: for the problem, for the constraints, and for the people who have to live with the result.
These are not steps in a process. They are the standard I try to bring to every system, from a school day to an aircraft.
1 / 4
The school-day problems behind Bell Logic and Homework Hero mattered because I was living them too. That keeps the question honest.
A clear answer is only useful if it respects the people, timing, and tradeoffs that make the problem real.
I care about work that helps someone move forward without needing a manual to understand it.
These started as problems close enough for me to feel personally. Building them made the questions concrete—and gave me a way to do something about them.
Students do not need another place to collect assignments—they need a realistic way to decide what to do next. I built Homework Hero around planning, recovery, and the messiness of an actual school week instead of an idealized schedule.
Built with Svelte, Cloudflare, and a focus on student feedback.See Homework Hero ↗
A bell schedule should not make students work to understand their own day. Bell Logic turns a confusing, exception-filled system into one clear answer, while keeping the experience grounded in the rhythm of student life.
Built with TypeScript, Cloudflare, and Firebase.See Bell Logic ↗
Most social feeds are designed to keep attention moving. Still Social makes a different tradeoff: no algorithms, influencers, or endless scrolling—just a calmer way to stay connected with the people who matter.
Built with React, TypeScript, Next.js, and Supabase.See Still Social ↗I have not followed one straight line. Each experience has widened the kind of problems I want to understand—and given me another way to practice the same way of thinking.
Seeing turbine systems and analytical work up close showed me that engineering is a team discipline: decisions carry through many connected parts.
Competing in Season 10 of the Air & Space Forces Association program made systems thinking concrete. A mission is never one decision; it is a chain of tradeoffs made together.
It gives me room to move between engineering, design, data, cybersecurity, and the questions that connect them. In April 2024, I earned Autodesk Certified User certification in Fusion.
With 15+ hours logged toward a Private Pilot License, I am learning to make deliberate decisions with incomplete information, changing conditions, and no room to lose awareness of the larger system.
Engineering is the path I know is right for me. Some answers will be technical. Others may require advocacy, leadership, or bringing people together around a better direction.
I want to spend my career on problems large enough to matter beyond the room they start in—systems that earn trust, expand what people can do, and keep getting better at scale.
Whatever the setting, I want people to have a better experience because I was there.I’m interested in ambitious engineering, consequential problems, and people who care enough to follow through.