What advice would Eric have for non-technical folks trying to become more technical through tools like Clay and LLMs? Vibe-coding advice?
The biggest advice that I could possibly give anyone trying to become more technical is that creativity is your greatest strength. It’s funny, because traditionally non-technical roles (i.e. marketing, brand, etc) are traditionally seen as the creative ones, but in my experience, my creativity is how I’ve been able to really build my own engineering knowledge. In this sense, what I mean by creativity, is that there’s tons and tons of different ways to build a workflow in Clay, there’s tons and tons of different ways to prompt an LLM to answer a question, don’t be afraid to experiment, to get results wrong, to ask AI to cite its sources so you can learn. Also don’t be afraid to ask this community, linkedin, etc for guidance while learning. In the world of AI, engineers are becoming product people, so what really matters is your ability to think about problems differently from those around you. For vibe-coding advice, I’d say that the biggest thing is to come to the AI with as detailed a plan as possible, or even use it to help write your plan. Ask it what you may not be thinking of in your current spec, and use it as a thought partner, because those answers will help it gain context as well.