Personally, I don't broadcast it, but if anyone asks I'm completely honest. I've got one project written in Swift that's up to nearly 50k lines of code and it's taken months to do from spec'ing it to debugging it to hand cranking all the CI/CD release process. A graphical MacOS native app isn't easy for me to craft prompts for and LLMs can't SEE what I'm trying to describe to it. I'm also learning Swift as I go. So quite proud of it AI or not.

I increasingly describe AI as part of the workflow, not the author of the work.

Just be up front about it; these tools are a simple reality at this point. Own the usage, own the output, take responsibility for the totality of what you’ve birthed into the world. If it’s some one-shotted trinket, don’t pretend it isn’t. If it’s some 5000-commit battle-tested magnum opus that you happened to spend a year driving an LLM to create, own that too. IMO it doesn’t matter if you dug the hole for your Olympic-sized swimming pool by hand with a shovel or using heavy machinery, I’m more interested in the quality of the final product.

AI does not remove authorship if you are still making the architectural decisions.

i dont mention AI b/c people already know i used it without saying. if anything its the opposite - i have to highlight that smth is hand made when i want to look crazy

[dead]

[dead]