{"id":10535,"date":"2025-04-22T15:57:08","date_gmt":"2025-04-22T19:57:08","guid":{"rendered":"http:\/\/parmaks.com\/Resources\/technical-debt-and-ai-slop\/"},"modified":"2025-04-22T15:57:08","modified_gmt":"2025-04-22T19:57:08","slug":"technical-debt-and-ai-slop","status":"publish","type":"post","link":"https:\/\/parmaks.com\/Resources\/technical-debt-and-ai-slop\/","title":{"rendered":"Technical debt and AI slop"},"content":{"rendered":"

\"Profit<\/a>
\n<\/p>\n

\n

Technical debt is easy to incur. It\u2019s unnecessary added features, undocumented code, support for outmoded interactions and anything that slows down your ability to update and upgrade your work. Tech debt is the combination of doing what feels right at the time, in a hurry, and then having to maintain it and understand it going forward.<\/p>\n

Vibe coding, which is a rising trend, pairs a human programmer with an AI like chatGPT. The AI is doing most of what a human used to do, and generating far more lines of code per hour than a person might. The problem is that often, no one knows exactly how the code works, which means it\u2019s going to be difficult to fix when it breaks or needs an upgrade.<\/p>\n

And as AI starts to create data sets (by reviewing, for example, response rates to emails or designs), those data sets are going to be so multi-dimensional that only an AI will be able to make sense of them.<\/p>\n

The end result will be as the end result often is\u2013the first one now will later be last. The shortcuts might not be the best way to get to where you\u2019re going.<\/p>\n

Get the system architecture right first. Document it, streamline it and test it. Then divide the components into small pieces and let AI finish the work. Fixing a defective brick is far more cost effective than re-architecting an entire building.<\/p>\n

\n\t\t\t\tApril 22, 2025<\/span>\n\t\t\t<\/p>\n<\/p><\/div>\n