I recently played around with Cursor to spin up a basic .NET project and publish it to GitHub. The code was trivial, but honestly, I just couldn’t be bothered to type it out myself. Cursor happily pushed everything into a shiny new repo while I sat back feeling… hmm… productive?
Now, I know my way around CI/CD, but GitHub workflows in YAML? Absolutely clueless. So, I did the obvious: let the AI handle it. First attempt failed. Second attempt failed. By the fourth prompt/commit, the pipeline was finally running. Success! Or at least, that’s what I told myself.
Here’s the catch: even with a working pipeline, I still had zero idea how GitHub workflows actually function. YAML, triggers, conditions? They’re all still a mystery. AI got the job done, but it sure didn’t make me any smarter.
And that’s the ugly truth nobody wants to admit: AI doesn’t really teach you anything. It doesn’t build skills. It just hands you results while you pat yourself on the back for “being efficient”. What it actually builds is dependency. You’re not learning, you’re just outsourcing your brain.
Sure, that’s efficient, AI will happily solve your problems. But do we really want to become button-clickers who nod along while machines do the “thinking”? That’s where this road leads. If you think that’s “The Future of Work”, congratulations: you’ve just been promoted to button-clicking-supervisor.
For the curious, here’s the full solution the AI spilled out.
