Not necessarily related to this or the author, but with all the supply chain attacks going on this year I sadly lost all trust in running something from a new GitHub repo that doesn't come from some trusted person/entity.
Love the idea btw, reminds me of a similar app that added xmas light to the dock.
Yes, the terrible urge people have to publish the results of their vibecoding is the problem - it’s why itch.io and steam and GitHub are overflowing with slop projects.
I love seeing that someone built a thing like this! It’s a fun idea, and it is inspiring to see what kind of thing it’s possible to code up with AI assistance!
But be honest, it’s not ship-ready. You aren’t going to handle bug reports and maintenance long term - it’s a toy you built that you’ll bore of and cast aside in a few weeks. You don’t want other people installing it and using it and bugging you to modify it.
Share that you did it. Share what it looks like. Share some of the story of how you prompted it into existence. But don’t publish it as if the result is some sort of product.
LLM-generated or not, I think anybody should be free to publish source code that they have no plans to maintain, although it would be better if clearly stated. I have found great value in abandoned repositories over the years.
All fair points, this was a completely new experience for me. I’m a product designer and wanted to see if Claude/Codex could help me make this real;
I posted about it on X (https://x.com/saragordic/status/2098916110787916219?a=sJ1QQB...), and so many ppl liked it that I just wanted to open-source it immediately. It’s not a polished product, but I use it every day and I’m still fixing things when I can. And it made a lot of people happy + I met so many amazing people because of it!
Love the idea btw, reminds me of a similar app that added xmas light to the dock.
I love seeing that someone built a thing like this! It’s a fun idea, and it is inspiring to see what kind of thing it’s possible to code up with AI assistance!
But be honest, it’s not ship-ready. You aren’t going to handle bug reports and maintenance long term - it’s a toy you built that you’ll bore of and cast aside in a few weeks. You don’t want other people installing it and using it and bugging you to modify it.
Share that you did it. Share what it looks like. Share some of the story of how you prompted it into existence. But don’t publish it as if the result is some sort of product.
> The more an article would benefit from photos, the less likely it’ll have them.
a bit of context: I’m a product designer, and this was my very first open source project. I made it purely for fun, here’s where it started: https://x.com/saragordic/status/2098916110787916219
screenshots: I added the little video now; you can see many more screenshots on X, a lot of ppl shared their own
trust: totally fair; if you’d rather not run my binary you can build it yourself with the steps in the README.
the “send it to your coding agent” install line: that’s for ppl like me :D
I’ve learned a tooon by open sourcing this; thank you all for the feedback!!
Also, excellent quick reaction posting the video, it was a great addition to have in the README to show it off
https://aurora.radiantmachines.com/
Whats next? Folder mittens?
Lazy and wasteful. Why do this when the process is running two commands?
> brew trust saragordic/tap > brew install --cask saragordic/tap/window-sweaters
What is the point here? This just seems like virtue signaling.