frequently
asked
What do you build?
Full-stack products, design systems, and engineering infrastructure. Currently focused on AI-powered tools and creative workflows. I ship fast and iterate based on real user feedback.
Are you available for freelance work?
Selectively. I take on projects that align with my interests in product engineering, design systems, and emerging tech. Reach out via the contact page with details about your project.
What's your tech stack?
React, Next.js, TypeScript for frontend. Node.js, Python for backend. Postgres for data. Tailwind CSS for styling. I prefer tools that ship fast over perfect architecture.
Do you write about your work?
Yes. I document learnings, failures, and insights on this blog. Categories: WORK (engineering, products), LIFE (philosophy, productivity), FUN (photography, books, hobbies).
How do you approach design systems?
Design systems are social contracts between designers and engineers. They're the agreed-upon physics of your digital world. I build them to reduce entropy, not to satisfy perfectionism.
What's your philosophy on shipping?
Shipping is the only metric. If it's not live, it doesn't exist. Your V1 should be embarrassing. If you aren't embarrassed, you launched too late. The market doesn't care about your clean architecture.
Where are you based?
Chicago, IL. Building lots of stuff. Always open to connecting with other builders, writers, and product people.
How can I stay updated?
Subscribe to updates via the button in the header. I send occasional updates about new projects, blog posts, and thoughts on engineering and product development.
Still have questions? Get in touch.