Sign In

Jeff Whelpley

Co-founder/CTO and Google Developer Expert

Jeff Whelpley is a reputable professional with a diverse background in technology and leadership roles. He currently serves as the Co-founder and CTO at GetHuman. Jeff is a Google Developer Expert in Web Technologies, along with being certified as an AWS Professional and a Google Cloud Architect.

With a strong educational foundation, Jeff studied at Delbarton School and holds a Bachelor of Arts in Computer Science from Boston College. His academic background complements his practical experiences in the tech industry.

Over the course of his career, Jeff has been actively involved in various organizations, showcasing his skills and expertise. He has held key positions such as Co-founder and CTO at Swish.com, CTO at MESH01, and Director of Software Development at Wells Fargo. Additionally, he has contributed significantly in roles like Project Manager, Tech Lead, and Software Developer at Tallan, Inc., and as an IT Intern at John Hancock.

Jeff Whelpley is well-recognized for his contributions to technology, particularly as the co-creator of Angular Universal, a server rendering solution for Angular 2+ applications. He is also involved in community building as a co-organizer of the Boston Angular Meetup and the Boston AI Meetup. Jeff's expertise extends to the speaking circuit, where he frequently presents at local meetups focusing on Angular, Node, and AI, as well as prestigious conferences like ng-conf, AngularConnect, AngularU, ng-vegas, and NativeScript Dev Days.

His influence transcends traditional boundaries, as Jeff has been featured as a guest and panelist on podcasts such as AngularAir and Adventures in Angular. This breadth of experience demonstrates Jeff's commitment to advancing technology and sharing his knowledge with the broader community.

Highlights

May 14 · twitter

The more I get Claude Code to walk me through nearly every planned change, the more I am annoyed at myself that I ever allowed CC to just do a bunch of changes without careful review.

The issue isn't necessarily that coding agents get things wrong per se (but the obviously do sometimes). The bigger issue is that we almost never give coding agents enough context up front no matter how hard we try.

And...I would argue that it's a fool's errand trying to do everything up front anyways because you don't know up front how much the underlying model will actually be able to figure out on their own.

So, IMO the winning approach is to do a decent job of up front context and direction before you ask the agent to come up with an implementation plan. Then have the agent walk you through the plan in detail one thing at a time. If you use agentic code reviewers have them at the plan and again have your main agent walk you through each suggested change one by one in detail.

This approach does take longer than accept all YOLO, but this is the way to get the best end result. Otherwise, the actual implementation will not be exactly what you really want and will be rife with bugs/issues that are hard to fix and get worse over time.

Jun 25 · twitter

Just listening back to this for the first time and I love how well it came out. It was a lot of fun talking to Brian, Jan, and Chau. We got really deep into the core topic and I would highly recommend you listen.

Thanks to Lara and Jean for helping to set this up.

Jeff Whelpley
Add to my network

Location

Malden, Massachusetts, United States