Who would have guessed that the guy who once struggled to figure out WordPress (and still is…) would now be delving into the realms of GitHub Copilot and ChatGPT to tackle the modern enigmas of programming? Embarking on this journey, I found myself increasingly reliant on AI tools like GitHub Copilot and ChatGPT, particularly for understanding the cryptic messages spat out by my terminal and for navigating the vast documentation of new technologies. My react and c sharp project, infused with TypeScript, Mapbox, and Chart.js, would’ve been a harder nut to crack without these AI companions.
However, this reliance on AI hasn’t been without its hitches. While GitHub Copilot has been akin to a sage, guiding me through the labyrinth of npm and Docker errors, I’ve learned to take its wisdom with a grain of salt. It often spits out incomplete or wrong information. ChatGPT, on the other hand, has been a reliable ally in deciphering TypeScript conundrums and terminal tantrums, breaking down complex documentation into digestible insights.
But here’s the rub – I often find myself questioning the veracity of the code solutions proposed by ChatGPT. There’s a part of me that remains skeptical, refusing to simply copy and paste without understanding the underlying mechanics. This skepticism isn’t born out of disdain but rather a desire to truly grasp the intricacies of my craft. It’s crucial, especially when AI, with all its intelligence, sometimes hallucinates solutions that are more fantasy than reality. This is why I try to use AI tools more as an explainer or oracle to ask questions about current code I have written, instead of a code generator.
Despite these challenges, I cannot overlook the tremendous benefits these tools have offered, particularly during the SQL course office hours I lead. Juggling multiple student queries about SQL MariaDB errors would have been a Herculean task without the swift assistance of ChatGPT.
So, has this AI integration made me a better programmer? In a way, yes. It’s forced me to be more critical, to question and verify before implementation. It’s taught me that while AI can be an invaluable resource, the final arbiter of any solution should be my own understanding and judgment.
Reflecting on my journey from a music teacher who once performed piano for elementary students with “The Itsy Bitsy Spider” to now navigating the complexities of software development, it’s clear that growth comes in many forms. Just as I learned to manage a classroom full of eager eyes and curious minds, I’m learning to navigate the evolving landscape of technology with a healthy dose of skepticism and a relentless quest for knowledge.
In conclusion, while the AI tools at my disposal have undeniably enriched my programming endeavors, they’ve also underscored the importance of critical thinking and a deep, personal understanding of the code I write. Perhaps, in this digital age, that’s the most valuable lesson of all.
