Merge branch 'antigravity'
This is Google Antigravity fixing up my visualization tool (which was
also generated with help from google, but of the normal kind).
It mostly went smoothly, although I had to figure out what the problem
...
I'm not gonna waste the remainder of my SN editing window on tweaking this formatting. DYOR etc
thanks; that suggests that maybe he's compartmentalising the vibecoding to the language with which he's less familiar.
I had begun skimming the sources before I reviewed the commit message history, and didn't find any mention of vibecoding in the comments of e.g. util.c, which he might even just be pasting from well-tested reference libraries.
Also note that the python visualizer tool has been basically written by vibe-coding.[...] It started out as my typical "google and do the monkey-see-monkey-do" kind of programming, but then I cut out the middle-man -- me -- and just used Google Antigravity to do the audio sample visualizer.
I fear that this is going to be woven into every narrative of anyone looking for a billion dollar runway now, lol.
Yup haha
Everyone can code and make apps!
please list your evidence for calling it "vibe coding"?here we go:
Commit: 93a7256
Merge branch 'antigravity' This is Google Antigravity fixing up my visualization tool (which was also generated with help from google, but of the normal kind). It mostly went smoothly, although I had to figure out what the problem ...I'm not gonna waste the remainder of my SN editing window on tweaking this formatting. DYOR etc
my original comment:
all I see so far:
AboutAbout
DocumentationDocumentation
the README and LICENSE were added together, in the latest commit with a comment that actually reads like Linus
SourcesSources
nothing obviously vibe-coding-related in the filenames
Is there some fingerprint or "code smell" that you recognize, from your familiarity with vibe coding?
start of last paragraph from the readme:
thanks; that suggests that maybe he's compartmentalising the vibecoding to the language with which he's less familiar.
I had begun skimming the sources before I reviewed the commit message history, and didn't find any mention of vibecoding in the comments of e.g.
util.c, which he might even just be pasting from well-tested reference libraries.https://github.com/torvalds/AudioNoise/commit/93a72563cba609a414297b558cb46ddd3ce9d6b5