Jeremy King is a seasoned software architect working remotely near Raleigh, North Carolina. Jeremy is a well respected career technology consultant who grew from a junior Perl programmer to a senior commerce Lead Engineer, and more recently into a Managing Delivery Architect. With decades of experience as a software engineer and architect, his professional journey has revolved around technical leadership, but hands-on coding has largely moved out of his day-to-day role.That all changed when Jeremy started exploring AI-powered coding assistants, seeking ways to bring efficiency - and joy - back into his personal development projects.

Jeremy’s background in Java, passion for efficiency, and curiosity about AI brought him to experiment with various cloud agents, Copilot, and coding automation tools. When he discovered cto.new through an AI newsletter, it immediately grabbed his attention: finally, a “big boy” AI-coding platform with robust integrations and a refreshing price point (free!) that was impossible to ignore.

From Spreadsheets to Full-Stack with AI

Jeremy’s AI journey started in a familiar place: “I run a Masters pool with friends and wanted to automate my Google Sheets scoring.” After dabbling in Apps Script automation, a friend encouraged him to take it further-so he built Leaderboard Fantasy, a golf fantasy web app, determined to launch it by the British Open. “It’s all me - front end, back end, security, the whole nine yards. And it’s all vibe coded… just me and my agents.”

More recently, Jeremy started another project: TutorPro, a tutoring platform built for his wife-a teacher who also tutors after hours. “I thought about a platform to help educators manage their tutoring relationships, focusing on trusted, experienced teachers doing the tutoring.” With cto.new and AI tooling, Jeremy could push far beyond single-stack limitations, exploring Firebase and Google Cloud, even in areas outside his prior expertise: “The nice part about all these AI tools is I can work in tech stacks I’m not that familiar with.”

cto.new, Flexible GitHub Integration, Speed and Scale

Jeremy’s development workflow is highly personal, shaped and optimized through experimentation with the latest tools. “I work almost entirely out of GitHub. I don’t use the cto.new web interface at all - I initiate from GitHub and assign issues directly to cto.new,” explains Jeremy. His process blends the best of multiple AI agents: Claude for writing and refining specs, cto.new for implementing features, and GitHub Copilot for rigorous code review.

“I’ve found this sweet spot: if a feature story is too big, all the agents choke, time out, or deliver garbage. So I split them up into four-to-eight-hour chunks for maximum AI performance. My spec writer generates GitHub issues, I assign them to cto.new, and it does its thing - often overnight. In the morning, it’s like opening presents: there’s a pull request waiting.”

What’s remarkable is the sheer scale cto.new enables. “I’m doing the work of an entire dev team, and I love that cto.new is a big part of the picture,” Jeremy says. “While I’m not 100% using cto.new for everything, it’s become a major contributor.” For routine code review and improvement, Copilot pitches in. “If I could get cto.new to fix its own code after Copilot’s feedback, that would be ideal. Maybe I’ll try tagging cto.new on my next PR review.”

Pushing the Boundaries: Experimentation and Efficiency

Jeremy’s insatiable drive for efficiency keeps him experimenting relentlessly. “Just in the past month, I started really pushing work off my machine and into these cloud agents.” Alongside cto.new, Jeremy actively tests Cursor, Claude, Copilot, and others, paying close attention to API limits, model updates, and pricing shifts. “I spend a lot on these services - but I love that cto.new is free.”

These tools let Jeremy balance depth and speed across multiple projects, using the right agent for the right job-whether it’s building new features for his fantasy sports app, developing a robust tutoring platform in an unfamiliar stack, or rapidly iterating on user feedback. “As I get more mature in my AI usage, I’m moving from back-and-forth prompt engineering to more deliberate planning and documentation before delegating to cloud agents.”

Real Results: Developer-Grade Output for Builders

Jeremy’s daily workflow with cto.new is practical and relentless:

• Writes and refines specs using Claude and custom slash commands

• Breaks tasks into right-sized GitHub issues

• Assigns issues directly to cto.new for implementation

• Receives working pull requests, often overnight

• Runs PRs through Copilot for additional quality assurance

• Maintains a full development pace usually reserved for a dedicated team

The outcome? “I’m doing the work of an entire dev team,” Jeremy reflects. “It’s made solo development not just possible, but scalable - and fun.”

Going Beyond: Feedback and Community

Jeremy values the responsive support and community he’s found with cto.new: “I’m in the Discord - very responsive team.” He doesn’t hesitate to provide candid feedback, like advocating for GDPR-friendly one-click delete capabilities.

Asked about cto.new’s future in professional team settings, Jeremy is optimistic: “I’d recommend it for clients. There are huge companies moving slowly - if they embraced cloud agents and automation, they’d leap ahead.” For now, Jeremy’s focus remains on what he can achieve himself - and perhaps, someday, closer to code in a professional role once again.

Conclusion

Jeremy King embodies a new generation of developers: empowered by AI, working across stacks and roles, blending hands-on technical excellence with a relentless drive for efficiency. With cto.new, he has transformed from a solo architect into a one-person development powerhouse, orchestrating “the work of a thousand people” seamlessly from his remote base. You can find more about Jeremy’s work and services at https://jeremyronking.com.

For anyone looking to accelerate their development process, cto.new proves it’s possible to move faster, smarter, and with a level of output previously restricted to fully staffed teams. As Jeremy puts it: “I love that cto.new is part of the picture. It’s fantastic. It reinvigorated me.”