keccers
@keccers.eth
I have full faith coding agents will be able to completely nuke entire classes of employees after using them. I mean, that's the goal right? Joblessness? That said, they are also capable of creating unholy messes in your code base, true monsters that seem touched by Satan himself — that are also totally functional and work as intended to the user. But then again who among us has not handwritten some ghetto code? And does it matter when you can double back and have an AI unfuck it, anyway? I am so close to the finish line on a project and staring at a beautiful monster.
10 replies
4 recasts
51 reactions
sean
@swabbie.eth
I actually lost a few months of development attempting to build this way. After trying to allow Cursor / Cascade to just do its "thing", it just builds spaghetti code with inconsistent patterns and once it can't hold the entire project in memory at one time, it ends up just running itself in circles when trying to edit or add more later. I've found that the best way to leverage AI editors at their current technology is to: - have a conversation about app goals and decide best app structure and patterns - have AI create a markdown file detailing goals, app structure and patterns - have AI create a single domain / section using stated pattern - run tests & verify pattern with AI recommendations and update structure document - methodically add domains / sections regularly reminding the AI to reference the structure document to keep the patterns in memory - always test new code and double-check all AI generated code - constantly ask the AI why it made deviations, if any For now, coding is still very hands-on
4 replies
0 recast
18 reactions
ᒍEᗰ ᔕOᑭᕼIᗩ
@jemsophia.eth
yeahhh this is it
0 reply
0 recast
3 reactions
