So you iterated on the design but not on the code? You have to do with the code what you did with the design. Review, adjust (or ask AI to adjust), rinse, repeat.
I've found that Claude can write code that's on par with what an average SE can produce, but you have to guide it. Write instructions, but also ask it to propose and assess multiple options, even ask it to run a code review and refactoring every so often.
Yes, the code is unlikely to be approved by Linus Torvalds, but so is the code that's made by many humans that is still merged and shipped.
Similarly naive outsider, but I've read things here and there. My understanding is that they should have declared mayday (emergency) and landed (potentially at another airport, potentially in the middle of nowhere) _way_ before so that when they have landed they still had 30 minutes or more of fuel in the tanks.
As a vinyl enjoyer, the sound quality is absolutely not why I buy it. I also use film cameras, and image quality (meaning, definition, color accuracy, etc) is definitely not why I use it.
There definitely are those that fit your description, but they are a minority.
Serious question — is there a way to defend from this "stealing the API" thing? E.g. building an authentication of some sort and then including a key with your app?
I've found that Claude can write code that's on par with what an average SE can produce, but you have to guide it. Write instructions, but also ask it to propose and assess multiple options, even ask it to run a code review and refactoring every so often.
Yes, the code is unlikely to be approved by Linus Torvalds, but so is the code that's made by many humans that is still merged and shipped.