What I learned from six months of being stupid on purpose · WVEZ Solutions

Feeling stupid often, and in new ways Me I graduated from Loyola U Chicago back in May of this year (2026) with a degree in Finance. I also spent four different summers working at a large healthcare company as a Financial Planning and Analysis Intern. Despite how amazing those experiences were, they also made me feel like my fate had already been decided, fostering an unhealthy perspective where careers outside of my “one-way path” were a waste of all the time I had invested. However, that short-sighted mindset rapidly changed within my final semesters of school and blossomed into what I’d call a major pivot for the better - all because I started teaching myself a software I’d never touched in my life. Who tf is JSON? I’ve been an entrepreneur for as long as I can remember, with random side-hustles ever since I was in elementary school. From sneaker reselling, dropshipping massage guns, rug tufting, rainbow-loom bracelets, you name it, I’ve probably done it. The newest one I stumbled into during my final semesters at Loyola was workflow automation in n8n. That was the first time I truly flexed the stupidity muscle, activated by operating outside my ol’ reliable set of finance/quant knowledge that I frequently relied on and rarely had the courage to step away from. I’d heard about the software from social media, fellow entrepreneurs, and other productivity creators I follow. All were saying the same things: it improved business processes, multiplied productivity, offered passive income opportunities (the classic), and more. So like any easily influenced college student, I jumped on the hype train. My original plan was to just automate the tasks that felt redundant in my schoolwork, career search, investment research, and basic day-to-day tasks. Then, I’d later pair my automations with the analytical capabilities of AI agents once I first felt comfortable making workflows that didn’t involve AI - all with hopes to create the foundation of a decent business. I signed up, opened it, and was met with a blank canvas with access to hundreds of random nodes, triggers, and inputs to choose from that I had no idea how to use. Starting with that blank canvas after being bombarded with colossal workflows that took up entire canvases made me question my limited skill-set and if it was even possible for me to do the same thing with no technical experience of any kind. These were a few of the questions I asked myself after opening that first canvas and wondering if it was even possible for me to catch up to those that had been working with the system for YEARS: What’s an HTTP node for? Are “AI Agents” all everyone makes with this? Why does everything need an API key? WHAT IS an API key? Is coding my biggest bottleneck? And most importantly: “How do I not know what to do already?” Just Quit Tomorrow “Wow, I’m stupid” is what I told myself, all because I didn’t miraculously know what to build first, or what workflow could “revolutionize my productivity” like forum writers and “experts” had claimed. As silly as it sounds, I felt pretty down during my start because it completely exposed how little I knew about basic topics in the technical world. Especially ones that were considered second nature to those more experienced than I, and frequently used in workflows I’d seen. Even with the fact I was just starting out - I, for some reason, still expected myself to figure it all out then and there. I realized in that moment and admitted to myself: This wasn’t a part of my pre-programmed script. My first instinct was to quit and cancel the subscription to save myself from the disappointment, but I replaced my desires to quit with the mindset: “shut up and try to figure it out.” This was my own little way of creating a wake-up call to remind myself I was fully capable of building something useful and had the ability to do exactly as I had planned as long as I put in the work. Quick nod to some stuff that always gives me an extra push: “Quit tomorrow” “TONY STARK WAS ABLE TO BUILD THIS IN A CAVE, WITH A BOX OF SCRAPS” “Does Jeff Hardy ever climb down the ladder when already halfway up?” Blocking Noise I spent weeks scavenging Reddit posts, Medium articles, and reviewing YouTube guides to learn as much as possible from those that knew more than I did. But looking back, I honestly have regrets with how much time I invested in doing that. I learned that there’s only so much I could gain from just watching videos and reading before getting stuck in what I call tutorial limbo - where I’d spend never-ending amounts of time watching others and researching random questions instead of actually doing. I feel that tutorials and informative reading are always good starting points for getting down the basics of a skill. However, I realized getting to a point where you reap the benefits from what you’re hoping to learn requires you to do it yourself and fail. A lot. This naturally resulted in me feeling stupid a lot. Limbo I’ve been a victim of tutorial limbo myself because it honestly feels amazing to think you’re learning a new skill. The dopamine rush from all things shiny and envisioning yourself replicating content you’re reading/watching - it’s addicting. Regardless, the heartbreaking reality is that it’s rarely ever productive. I’m still learning to avoid falling into that void to this day. The most damaging action, though, was actively exposing myself to the best outcomes the skill had to offer that were only possible with months or even years of experience. While in the process of learning, it’s by far been the biggest trap and motivation killer I’ve experienced. It’s fine observing what’s possible with a skill, but never overdo it to the point where you paralyze yourself with doubt like I did. Especially in the age of social media larping, you never know who’s just straight up lying for attention, profit, or in an active hunt for new victims to buy their snake-oil-esque course. What I’ve found to actually be productive was starting small and “just doing.” Specifically, seeking out mistakes within MY way of work to actually learn what worked for ME. Furthermore, reminding myself that the ability to even start was an accomplishment in itself. Many never make it out of the limbo loop in the first place, so starting has always been a win in my book. So many past interests of mine carry hours that went into googling and asking people “how do I get better at ___,” instead of actually doing what it took to figure it out for myself. Wasted potential survives and feasts on those stuck in the limbo loop. Baby Steps Nobody comes out of the womb sprinting full speed (hats off if you did). You need to learn to crawl first, and my first time crawling was a simple workflow that sent me a Slack notification when I received an email response about a job I applied for at Google. Can this easily be done by setting up notification preferences in the careers page? Absolutely. But who cares? The point was to start and make something that worked - and this workflow did exactly that. I got the notification of my rejection to the job in a timely fashion to my Slack with green execution signals next to it.

Success.