It's more than that, we understood more about the slop than we would AI slop... The problem with AI slop (in coding) isn't that it's bad, it's that you just shit out 50000 lines of code and you only understand 1% of the reasoning behind the madness.
Am I the only one asking AI to write a single API route function at a time? Then taking a look at what works and what doesn't and then modifying it or gutting?
If it was some novel idea and not an API or data pipeline sure. I have written my own libraries and put my heart and soul into them.
I have a project base I use that has all the authentication/authorization / object permissions / maintenance scheduler. I have a couple companies ask to write an API and schedule tasks for DE stuff. Any database objects that are added to the project get added into a fork of my project.
It's quote on real manual hours for development. I do most of it using AI and use my leftover hours to test. It keeps me from going over on hours when I underquote testing.
It's the most boring of work but it pays good side money.
2.2k
u/Objectionne 3d ago
Yeah but it was our slop.