One of my first jobs as a college graduate was writing Robotic Process Automation (RPA) workflows using Leapwork. I was able to automate several repetitive, time-consuming tasks, which gave me a deep appreciation for the power of engineering.
RPA involves using software “bots” to mimic human interactions with digital systems. These aren’t physical robots, but rather modular software programs designed to perform tasks like data entry or web scraping.
In the programming world, there’s a rising trend some call vibe coding — a term popularized by Andrej Karpathy, meaning you let AI agents write all the code for you, blindly, without personally reviewing or understanding it. You just “vibe,” prompt after prompt, never stopping to check, learn, or correct the output yourself.
Let me be clear: I’m not talking about using LLMs, RAG, or prompting to assist coding, generate snippets, or look up APIs.
I’ve been coding for nearly a decade, and I still enjoy writing code — across different languages, for different problems. But one thing that’s always bugged me is the community.
Don’t get me wrong: coding communities can be amazing, helpful, and generous. But they’re also filled with ego battles — endless fights over which language is “better,” which one makes you a “real” programmer, and why you’re somehow lesser if you’re using that language instead of this one.