Back to Blog
About•8 min read•

Who Is Eric Jokl and What Does He Do?

A comprehensive guide to Eric Jokl: his background, skills, projects, and approach to digital building. From CS50 to CT Party Bus to Next.js SaaS—here's the full story.

Who Is Eric Jokl and What Does He Do?


I'm Eric—a web designer and developer based in the U.S. working remotely. I help startups and small businesses build websites that actually work, whether that means more conversions, clearer messaging, or just getting things built without the usual tech headaches.


How I Got Here


I spent a lot of time the usual way: learning by doing. Recently, I went through Harvard's CS50x course, which was genuinely challenging and really filled in gaps in how I think about systems, algorithms, and the fundamentals underneath everything I build.


It reminded me how much I still don't know, which is probably healthy.


What I Actually Do


I'm not purely a designer or purely a developer. I kind of fall in the middle, which means I think about how something looks, how it works, and whether people will actually want to use it.


Most of the work is:


  • Building websites that perform well and don't feel bloated
  • Helping people figure out what their site actually needs to do
  • Writing clean code that doesn't need constant hand-holding
  • Making sure things load fast and rank decently in search

    • I started CT Party Bus as a side project years ago—it's a pretty simple site, but it works well and keeps generating revenue without much fussing. That experience taught me what matters and what doesn't when you're actually running something.


    Why I Call It "Digital Building"


    Honestly, the job titles are all kind of weird. "Designer" sounds like you only care about how something looks. "Developer" sounds like you're deep in code. "Entrepreneur" sounds pretentious.


    What I actually do is think about the whole system. How does it work? Who uses it? What breaks first? How do we iterate based on what we learn?


    The best digital products aren't beautiful or technically impressive—they solve problems clearly and reliably. That's what I aim for.


    How I Work


    I'm probably best when I understand what you're actually trying to accomplish, not just the feature list. That conversation often reveals that half the features don't matter, and the real problem needs a different approach entirely.


    I use modern tools that make sense: Next.js, React, TypeScript, straightforward hosting. Nothing exotic, nothing that'll be obsolete in two years.


    Timeline-wise, it depends on scope, but I believe in shipping things quickly and refining based on real feedback. Most projects are in good shape within 4-8 weeks.


    What I'm Still Learning


    CS50 reminded me that computer science fundamentals matter, even if you're not writing C every day. I read a lot. I build things constantly. I pay attention to how real products work and why people actually use them.


    The tech industry moves fast, but most of the core ideas are older and more solid than the hype suggests. I try to focus on those instead of chasing trends.


    If You're Thinking About Working Together


    Feel free to reach out. I'm interested in projects where the thinking is clear and the outcome matters. Not necessarily big projects—sometimes the best work is helping someone get unstuck on something specific.


    I'm also happy to chat if you're just curious about building things online or how this whole web development thing actually works.