When I code my self I can remember how it works for years but with vibe coding it is different, I started to forget it easier even if I could understand the PR and the commits.
How I personally solved it was to first iterate and extract methods into smaller pieces and make it testable following SOLID/KISS principles and write the unit tests for it without vibe coding.
Curious how other do it, any ideas?
Yoko (@stuffyokodraws)
작성자는 'vibe coding'에 대한 논의가 많지만 소프트웨어를 진정으로 민주화하는 방법에 대한 논의는 부족하다고 지적하며, @venturetwins의 글을 추천합니다. (vibe coding과 소프트웨어 민주화 관련 논의 촉구)
◢ (@joemccann)
작성자는 @venturetwins의 통찰을 소개하며, 'vibe coding' 분야의 큰 승자는 기술·보안 문제를 완전히 추상화해 일반 사용자(노미즈)가 쓸 수 있게 만드는 서비스들이 될 것이라고 분석합니다. 인프라 제공자(예: Vercel)는 제외된다고 언급합니다.
Expensively Quadratic: the LLM Agent Cost Curve https://lobste.rs/s/0stawc #vibecoding
https://blog.exe.dev/expensively-quadratic
AI Hallucination Squatting: The New Frontier of Supply Chain Attacks (instatunnel.my)
https://instatunnel.my/blog/ai-hallucination-squatting-the-new-frontier-of-supply-chain-attacks
C'est prouvé : Le vibe coding va tuer l'open source
https://fed.brid.gy/r/https://korben.info/vibe-coding-tue-open-source.html
How #VibeCoding Is Killing #OpenSource
« If we consider this effect of ‘AI-assisted’ software development to be effectively the delegating of the actual engineering and development to the statistical model of an LLM, then it’s easy to see the problems here. The LLM will not interact with the developers of a library or tool, nor submit usable bug reports, or be aware of any potential issues no matter how well-documented. »
› https://hackaday.com/2026/02/02/how-vibe-coding-is-killing-open-source/
Le vibe-code de mes deux est en train de tuer l'open-source. Les sites d'entre-aide comme Stack Overflow voient leur fréquentation fondre rapidement.
https://hackaday.com/2026/02/02/how-vibe-coding-is-killing-open-source/
Le sous-texte de tout ça : les gens s'enferment avec leur ai, plus d'échange d'info, plus d'entraide, plus de communauté autour de nouveaux projets.
#ia #ai
#NightmareOnLLMStreet
#Noai
#VibeCoding
#Tech
#OpenSource
Join the Hype-Train: OpenClaw and Moltbook -
...yes! AI-Bots founded an own social network! Only bots allowed to post.
https://nodeponds-nerdletter.de/join-the-hype-train-openclaw-and-moltbook/
#Internet #Ai #Creepy #Documentary #Netart #Tool #Vibecoding
Spectacular!
Full text of Wiz write-up here:
https://www.wiz.io/blog/exposed-moltbook-database-reveals-millions-of-api-keys
It's really fun how you can easily vibecode apps using Mastodon's APIs to analyse, summarize your timeline, lists etcetera For personal use i made an app to summarize the last 48 hours of posts in a specific Mastodonlist. Really useful/timesaver.
#vibecoding #mastodon #API #AI
Vibe Coding a Flickr Export Tool with Google Gemini
Reading Time: 3 minutesRecently I decided that I would backup my Flickr library locally despite having over a year left on my pro account. In so doing, when the decision comes whether to dump, or keep using flickr, I will know that my data is safely backed up locally. Of course I decided to play with the archive but came upon a snag.
E6 Microdegrees
That snag is that Flickr uses the E6 Format, also known as Microdegrees. With Google Takeout, when I exported photoss I used the exiftool to add metadata to photos and it worked fine. Because it worked fine I then moved photos to Photoprism and Immich without issues. With Flickr photos using the E6 Microdegrees format photos displayed as being taken in the middle of the Atlantic near the coast of Africa rather than the canton de Vaud.
With a few iterations Gemini finally figured out the issue and divided exif data by a million. To correct this error Gemini and I exported the proper geodata to a CSV file, before then adding it to the exifdata of photographs.
Re-Use Flickr Metadata Added Over the Years
This morning I decided that I wanted to add the tags, titles, and other metadata back into the exif data so we created a new iteration of the CSV file.
Re-naming files With Their Creation Date
After several iterations I decided to rename files using their title when they had a human readable title, rather than the number given by Flickr's tools. I then decided that since we're renaming the files anyway we might as well add original creation date of the files to the filename. They now use the yyyy-mm-dd-filename.jpg convention.
A Folder Hierarchy
Since we've added the metadata to the photos, and renamed the files to display their creation date without opening individual files it made sense to go an extra step by creating a folder architecture by year/month/day. In so doing it becomes easy for an individual to look for, and find photos, without the use of a CMS.
TLDR of Steps According to Gemini
Pair Flickr JSON metadata with original images.
Extract and convert GPS from E6 to decimal.
Sanitize titles into safe slugs using the re module.
Build a hierarchical Year/Month/Day folder structure.
Implement a 'Smart Migration' script with space checks and progress bars.
Execute a bulk copy to rename and organize 78,000+ files.
Verify integrity by matching file counts.
The Rational Behind Backing Up
Flickr is a great community for photographers to share beautiful photos but its free tier has shifted. It went from 200 public photos, up to 1TB, and then back down to 1000 photos max. the price per year went up so it became more interesting to pay for two years, rather than one at a time.
For a while I downgraded to the free tier, expecting that my photos would be deleted from flickr. They weren't. I stopped paying because I expected Flickr to be mothballed and eventually vanish. It currently looks alive and well. I believe that's why I decided to pay for another two years at the time.
An Export Worlflow and a Reason to Stick With Flickr
My experiment, over the last two days has strengthened the use case for Flickr Pro as a cloud backup solution. If like me, you have a work flow in place to download and process Flickr Export zip files, then within a day or two you can re-create your library locally.
A simple "for each loop" can download your zips in the background once the backup is ready.
And Finally
Years ago I exported photos from Google Photos via Takeout and from Flickr via Flickr Export but I didn't know how to re-combine the data from the json files into photo exif data. Over the last week, through experimentation. I have been able to export photos from Google Photos and Flickr, and recover them, for ingesting into Photoprism and Immich.
Without Gemini I would need to spend hours reading the documents and through trial, and error get it to do what I want. With Google Gemini it does the RTFM part (read the fabulous manual), and I ask it for help.
Now I'm on the cheapest iCloud tier, I can downgrade to a cheaper Google One tier, I can dump Swisscom MyCloud and I can re-think how I use Flickr.
I have been using Gemini as a tutor.
#AI #exiftool #flickr #Python #vibeCoding
I’m curious to know whether people who use #LLMs to code experience the same profound sense of satisfaction when they successfully achieve their goal. I’m not a professional coder, but when I do code, the sense of accomplishment is the best part of the experience. I think if my workflow were just writing what I wanted and then saying “it doesn’t work” until it works, it would cheapen the experience. It’s the effort (and increased understanding) that makes it worthwhile. #vibecoding
OpenAI Codex arriva su Mac e cambia le regole: ora puoi modificare progetti Xcode senza aprirlo. 🚀 Il #vibecoding promette di accelerare lo sviluppo e democratizzare la creazione di app. È la fine della programmazione tradizionale o solo una nuova era? 🍏💻
https://www.melamorsicata.it/2026/02/03/openai-codex-mac-vibecoding-sfida-xcode/
VS Code × Cline × OCI GenAIで"コピペバイブコーディングを卒業"
https://qiita.com/itokazu/items/28042d9285ffbfed9da8?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Hacking Moltbook: AI Social Network Reveals 1.5M API Keys https://lobste.rs/s/xyrr0q #vibecoding
https://www.wiz.io/blog/exposed-moltbook-database-reveals-millions-of-api-keys
I'm shocked, really shocked, really really shocked...
Note: sarcasm was used in this post
If you "vibe code" by writing a specification, then
1. either: you write down what is important to get secure code output
2. or: your IDE adds what is important to get secure code output (I don't know the level of prompt magic Cursor / Claude Code / ... add)
3. or: your LLM automatically knows what is important to generate secure code (unlikely)
4. or: you're f..ked
As you typically don't know 2, and 3. is not reliable, if you don't want 4., do 1.
Since we’re all #vibecoding with #claudecode - here’s the public feed from the #forkiverse turned into stats - including the ever important cats vs dogs, and “one hit wonder” of the week.
Coded completely from my phone using Claude code for Web via the Claude code App.
@Casey @kevin And @pj you built a great new home for cat pics it seems.
"Huntley thinks he has stumbled upon an idea that can change software development, and perhaps entire industries.
"Developers, he argues, should now spend more time thinking about writing loops that drive coding assistants to produce better output, rather than persisting with code reviews.
"Agile and standups doesn't make sense any more," Huntley said. "The days of being a Jira ticket monkey are over."
"He also thinks that Ralph poses a profound challenge to any business. "Companies have a brand that can't be cloned and goodwill that can't be cloned," he told The Register. "But product features can now be cloned."
"Huntley therefore expects that startups will use Ralph to clone existing businesses – especially SaaS outfits – and undercut the prices they charge because they can afford to do so using agentic coding that costs $10 an hour instead of having to pay a full staff of human coders."
#LLM #AI #vibeCoding
https://go.theregister.com/feed/www.theregister.com/2026/01/27/ralph_wiggum_claude_loops/
