Prime example of AI being a shitty software architect.

Just add another field for a second wallet, bro.

If you need a third wallet, add a third field.

🥴

Yo, use an array. It's 2025 and we have moved on with our data structures, ffs.

nostr:nevent1qvzqqqqqqypzqgxjnqgddf0e9vz94hszawadeypk6aquc6rtqpq4cs45ydh7ftf0qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyphg20q5433ds5jng37hzppl88u4s74s75j7n4y4mhac39krmvch5pdg02x

Reply to this note

Please Login to reply.

Discussion

This is my biggest disappointment with AI. It is nice of it can auto complete for me, but I really need help with simplifying project architecture, but whenever I ask it for help it comes up with awful architectures that *might* work but are far more complicated than what I am trying to do.

I made the mistake of asking it to simplify the relay utilities, on Sunday. It's now Tuesday, and I still have a blank screen and an infinite loop, as an app. *sigh*

Nevermind, roll it back. 🙄

Roll back complete. And now I have an excuse to implement profile event editing, since I have to redo it all. 😁

Didn't like the way it was built, anyway. Very organic-grown, instead of sensibly-planned.

What about read only nwc strings to receive zaps?

I haven't even looked at NWC, yet.