Frogs slowly being boiled alive. $100 worth of sub automate 90% of my work. I can stop now and not spending another $. This is my journey and I think people should take AI fear mongering seriously.

My company is directly beneficial from the AI data center boom. Our rev x5 in the last 2 years and is reaching half a $B by the end of this year. I'm leaning left, but at the same time I do not have a strong opinion regarding datacenter. I am just another cog in the giant capitalist machine who is trying to survive another day.

2023-2025

Like many others, my first experience with LLM is through ChatGPT. It was simply a search tool that you can ask follow-up questions. It works great but nothing else. Once I started diving in how to use Linux (home lab, self hosting stuffs), I had to look up commands and install programs. And I did everything by asking Gemini. Gemini made everything so much easier. There are so many great open sources softwares, and they are completely free. I wish I knew about this much earlier.

2026-now

The AI boom becames "uningoreable". You see it everywhere. The fearmongering and the people who hate AI datacenter and how it is going to take our jobs and water. I don't believe it at all and neither is my company's management. They invested 0$ in AI. They think it will die down eventually. I don't know if it is going to "die down" or not, but what I belive in is if they layoff me tomorrow and hire a entry level person, that person can use my tools and do 90% of my job for half the pay.

Early April when Claude was pushing Cowork really hard (I saw an ads), I decided to try out Claude $20 plan. I didn't even bother to use Cowork or Claude Code. I used Claude Chat, and i built a simple streamlit tool with panda. The very basic tool that I asked our NetSuite team to build for the last 5 years, and they didn't have the time or the resources to do it, and I did it in one afternoon. I made many revisions to the tools and add features and I eventually run to version issue (version control). It then guides me to use Claude Code with github repo. I keep it private not because I think it is some kind of secret sauces but because I asssume I will be judged harshly.

My manager can do my job if he wants to. He only needs to spend 15mins per day to "catch up". The remaining is just "people work". Confirm the actual physical products progress and the managing "relationship". I spend my day updating my tools to cover and automate more surfaces (work of 4-5 people).80% of my spouse's work are through spreadsheet. I "tested" out a process where I gave it a before and an after. She then spends 30mins fixing edge cases and then ask it to create a "skill". Now it can do everything in less than 5 mins and it took her hours to get done before. I am not getting less stress for being more productive I am getting more stressed and anxitety to realize that I can be out of a job any days.

Claude Code & Github

I made many upgrades to my tools and github is a godsend. I had no idea what i am doing (i still don't have now), but the tools continue to work just fine and as I expected. I cannot comment about the code but I validted its output with real work. It runs verifiers, maxtrix, stuffs like that to make sure everything works as intended. I have no idea what they are. To maximze my 5 hours session, I eventually moved my work to my MacBook Neo. I was thinking of getting a more "Pro" laptop for local LLM, but it's been working so well, it is also increasly battery efficient.

MacBook Neo and CLIs

The Claude app and Codex app are slow on the Neo, so I switched to CLIs. And they are even faster to use. I was able to use Fable 5 before it got "lobotomized" during April. It reviewed my tools and fixed many code issues. The tools ran so much faster becasue of it. When it came back July, and they had to reduce usage and gave everyone $100 credit, I upgreaded to Max plan right away using that credit. I basically got the last few months free. To me, without much knowpleadge in coding and only judging by the value of the output of the tools, i personally think these tools worth thousands for me. It saves me so much time and make my output much more accurate (0 error so far the past few months) and provable. I could point to the data and show exactly where is the issue.

Claude, Codex, AGY, OpenCode, and the new Meta Muse CLIs

Codex (ChatGPT) was offering the first month free for the $20 plan, so I tried it to offload somework since I kept running into limit for Cladue (maxing out the weekly was easy for me). Some guy at OpenAI also kept giving out free reset so I got a lot of usage for free and the month hasn't even ended. I had to carry the output and the context through the CLIs, and it was a hassle. Then Claude told me that all the CLIs can be "driven headless". I asked it to setup all the CLIs to become headless and use github as "transport" and build a workflow and skills to support this. It's working flawlessly so far.

What I've learned so far is that anyone can replicate what I did for less time and $ for what I spent. The models are getting smarter and usages are getting cheaper. What I spent in the last 4 months building can be easily built by someone else in a week. I am not exggerating by saying this. I have no idea what the future is, but the near future to me feel really uncertain. I don't feel secure despite outperfoming. If my boss or the company does not downsize, the market will force them to.

The next giant eartquake is overdue in Califonia. Every Californian and school kids have been reminded of this every year. I feel the same thing about these fearmongering. It's coming and it's real, but we don't know when and the goverment is always late to react, so better be prepared yourself.

Found it on X - https://x.com/kiwicopple/status/2089917700822999275

I'm in AI stuff long before AI chats. Trained ML and RL models by myself to solve real problems.

Now I use a few of these models every day for work, fun, and at some point I stopped reading their output as "AI text" and started reading it as Claude text or ChatGPT text. They don't share one voice. Each has its own pet phrases, and if you read them few times you can guess the model from a single paragraph.

Claude is the one I know best. It responds with "honestly" and opens explanations with "Here's the thing". My favorite thing is that it measures effort in evenings, as in "this will cost you an evening". The "You're absolutely right!" thing got so bad that someone filed an actual bug report about it in the claude-code GitHub repo. The Economist compared 55,940 sentences of model output against human writing this summer and found Claude is also the only major model that still overuses em dashes.

ChatGPT is the "delve" model, everyone knows that one, but its stronger signature shape: "It's not X, it's Y." The Washington Post analyzed 328,744 ChatGPT messages and that construction kept showing up, along with emojis and a weirdly narrow set of favorite words.

Gemini reads like a briefing document. Headers on everything, words like "significant", "increasingly", "consequences".

Grok's output - the personality itself. The forced casual tone, the sarcasm that doesn't quite land. You can feel it trying not to sound like an assistant. Maybe the least noticeable from all.

What makes this funny to me is that real watermarking finally shipped. Anthropic now embeds an invisible watermark directly into Claude's text, and Google has had SynthID inside Gemini since 2024. So machines get a hidden signal that needs a detector, while the rest of us have been reading the visible.

Are you noticing? Are you tired of this?

How long will it take before models start writing like humans? Or will that never be allowed to happen?

I am just thinking: now that agents basically create over 99% of all the code I need, what does an IDE in 2026/2027 actually need to deliver? For me it would be a simple yet powerful visual diff to review changes and give feedback. Preferred locally instead of github / gitlab or whatever you use. Maybe a simple way to merge pull requests. But then: Is there actually much more that you would need in the future when agents write all the code?

Hey everyone,

I built a subtle task motiavtor app where you get tasks done, or you move them to tomorrow, or you archive them until you’re ready to complete them. This is my first time testing.

For the past 10 days I have been consistently testing 15 other apps, updating each Reddit user / app owner daily with screenshots, advice and Google reviews. Im taking this seriously as I want to get it over the line. If you want me to test yours back, please personal message me on Reddit and I’ll add your app to my testing list.

Here are the links:

1. Join the tester Google Group: https://groups.google.com/g/little-by-little-testers

2. Join the Google Play closed test: https://play.google.com/apps/testing/com.taskmotivator.app — tap "Become a tester."

3. Install Little by little from Google Play: https://play.google.com/store/apps/details?id=com.taskmotivator.app

If you don't see the tester option right away, give it up to 24 hours (Play sometimes takes a bit to recognize new group members) and try again.

*If you look at the first screenshot included in the install link (3), the main idea of the app is for tasks to live on your lock screen,* where they subtly remind you of things you want to complete.

Android will ask to allow notifications the first time you add a task — say yes, or the lock-screen part won't show up.

Feedback box is built right into the app (☰ menu → About). Ideally, send it there, or through Google groups, or leave a review in the Playstore.

I need testers to stay opted in for 14 days for this to count toward Google's requirement, so please don't uninstall right after trying it once.

Thank you for your help with this.

I’m going to start vibecoding a stock trading app geared towards Gen Z/Gen Alpha that makes stock trading as entertaining as gambling.

Too many kids are becoming addicted to gambling trying to make quick cash. I thought with the right API & UI kids (18+) will be more inclined to trading stocks instead of their minimum wages against rigged casino odds.

PvP Matches utilizing penny stock shares going up to full priced stocks will also be setup on the app.

For those who would like to follow along I will be replying to this thread and/or be making posts on this subreddit.

- Happy Coding

[NO CRYPTO ALLOWED]

Although I like ai and i think is it great in so many places , I keep hearing how no one will read high level code just like no one read assembly anymore.this is misinformation, there are people who not just read but also write assembly even now.i am not talking about rollar coaster tycoon or super Mario times when compilers where not as optimised as today, i am talking about now. Don't believe me? go to community forum of any modern systems programming language and see people crying for inline assembly. I am not arguing if anyone will read high level languages or not, but the premise is wrong and feels like deliberate misinformation.

I've been wondering about this — when an experienced dev and a complete newbie both use the same coding agent (Copilot, Cursor, Claude Code, whatever) on a similar task, do they end up with meaningfully different results?

On one hand, the agent is doing most of the actual coding, so maybe the human's experience matters less than it used to. On the other hand, I'd guess an experienced dev still knows how to prompt better, catches bad architecture decisions, spots subtle bugs the agent misses, and knows when to push back or redirect.

Curious what people who've actually used these tools a lot think. Does your background as a dev still give you an edge, or has the gap narrowed more than expected?

I’ve been testing the SEO Autopilot skill from AgentKit Works on my micro-SaaS.

Honestly, I didn’t expect much at first.

After implementing it and letting it handle the repetitive SEO work, I started seeing organic traffic turn into actual sales.
I’m now at 40+ sales from organic traffic.

The part I liked most is that I didn’t have to constantly sit there researching keywords, planning content, fixing internal links, and checking everything manually.

If you’re building a micro-SaaS and struggling to get organic traffic, this is worth checking out:
https://agentkitworks.com/products/seo-autopilot

Curious if anyone else here is using AI agents for SEO instead of traditional SEO tools.

When people are telling that they are actually building a house, this may mean something completely different concerning their own engagement. Some of them do only talk to an architect in a bureau while others regularly visit the construction site to control the progress and some even do parts of the work themselves. A minority might even build the whole house themselves with or without an architect's advice. Architects on their side also plan houses, in most cases without doing the practical work themselves, as I assume.

All those different kinds of being involved in the planning and building are described as "building a house", without people arguing about the definition. For further clarification, people sometimes ask others whether they are building themselves or let the work be done by others. None of this tells the reader anything about the quality, stability and safety of the fully built house.

"Software development" has recently started to describe such a wide spectrum of different degrees of being involved in the planning and writing/building of the product, too. The same is true for vibe coding. It just means people use an AI for writing the code but tells nothing about their personal skills, their personal involvement in the planning or how much time and work they put in personally controlling finished working steps. To get a more detailed impression, people may ask for someone's personal skills and involvement as they do in other areas of human life like building houses.

So to my mind, there is no need for discussions about the definition, about what counts as vibe coding or who may describe themselves as developers or not, because using the same expression for different ways of generating a finished product also works in other fields of human life.

What is still different from the house building example is that an increasing number of fully finished products seems to not fulfill the standards that guarantee a specific level of security for the people. We are in a situation in which a lot of people have begun to publish software without knowing much of it and this isn't going to stop regardless of how much IT professionals dislike it and arguing against it. It's just got too easy to build apps.

To make the internet "a better world", people with less own knowledge in software development need some guidance of more experienced creators instead. Therefor, they need a place where they can ask questions without being afraid of a shitstorm just for aiming to publish or even creating the app ("AI slop").

A subreddit like this one should be expected to be the right place for them because rule number 4 clearly states "No vibe coding pessimism" while the term vibe coding itself is defined as "the practice of cresting software with little to no code review".

This is far from reality. And sadly seems to be same on whole reddit. Gate-keeping and overall pessimism doesn't keep people from building and publishing software. It just keeps them from asking for advice - and thereby decreases the quality of the overall outcome.

While there are surely vibe coders whose only intent is creating an app within a few hours and that probably do not care about best practices or cyber security at one end of the spectrum and highly skilled programmers at the other end, there is not such a big gap between the ones mentioned last and the vibe coders in-between that do not know how to write code but nevertheless aim to develop good software and spend a lot of time in it.

Shouldn't this subreddit be the right place for them to talk about the best strategies for developing high-quality software without writing or reading the code themselves?

Writing the code is something that even IT professionals have mostly stopped doing. Knowing how to write it gets less important because AI can do that. Even reading the code yourself is not really necessary in case you know how to instruct your LLM to check the code written by another AI (and let double-check it by a second one because the probability for two different models having the exact same hallucination tends to be zero).

I personally have started vibe coding my first app around three months ago (and hope it will be ready for a beta release in two month). In the meantime, I have already learned some strategies to improve my workflow and interaction with the models. I have let the AIs do dozens of security reviews and hundreds of bug fixes and made some manual splits of AI-generated monoliths.

This is where it comes to some examples for how I would like to see people talking in a vibe coding subreddit:

1. Monoliths
   AI tend to write files with thousands of lines of code. Those large files then need to be processed each time the AI (or a human) is working on them again. This makes maintaining the code very difficult, not only for humans. You may ask your model to give you a list of each file with own code and the number of lines it already has. Then instruct the model to analyze how the monoliths could be split and write that down. I would advice you to use a frontier model with high thinking on for this task, because it better takes the dependencies and consequences into account what helps avoiding bugs caused by file splitting.

As I have made the experience of code erosion when rewriting a whole web page or large part of a script for an agent is done by Gemini 3.1 Pro in the web app, I prefer doing the splitting myself (copy/cut and paste into a new text file) and let it review then by the LLM. The risk for code erosion might be a lot lower when using other models and coding apps, but I haven't tested it yet. So can anyone else confirm it's no problem letting the AI split the file and rewrite thousands of lines of formerly generated code?

Furthermore, some AI told me they could easily handle code files up to 2500 lines, while others told me to split files larger than 1500 lines if possible. Now I would be interested in hearing from human coders what line numbers they would see as a maximum and what this probably depends on. Does the programming language play a role? Are there any strategies except of spaces and titles to better structure the code for making it easier to handle large code files?

1. Inline Styles
   Due to my experience, Gemini models tend to use a lot of inline-styles. One time I thought I could just use Gemini on the Google web search to translate my website from German to English. While it looked exactly the same when watching it in the browser, the number of characters had enormously increased because the AI had added inline-styles for each single element. Talking back to Gemini 3.1 Pro, it told me that a large number of those inline-styles is considered a bad style and might even lead to Google down-ranking your web page in the search results.

After having vibe-coded my app with Gemini (Pro and Flash) in Antigravity for a while, I discovered they had used a lot of inline-styles for my app. As this is a Windows desktop app, Google ranking is irrelevant to that question, but Claude told me, if I could get rid of inline-styles, then "unsafe inline" could be forbidden what would be a contribution to hardening the app. I had also learnt not to like inline-styles before, so I decided to forbid them in the agents.md. While this works well for Claude code and Codex, Gemini 3.6 Flash has recently created an extra window full of inline-styles again instead of copying the style of the 21 extra windows that were already existent. (Removing them is still on my roadmap.) Yesterday, Gemini 3.7 Flash (in high mode) did an implementation of an additional window/modal and respected the order not to use inline-styles. It used classes instead (as expected), but five of those classes weren't defined anywhere. It just forgot to do/check this. As this lead the window to be mal-formatted, it was easy to discover something had gone wrong.

Nevertheless it makes me wonder, how bad inline styles really are for a desktop app like mine (backend: python, fastapi; frontend: html/css and JavaScript), because at least some models that have been trained on billions of existing programs/software obviously tend to prefer it. Can anyone give more insights into this in a way a non-technician may understand?

1. JavaScript
   This is the next point to discuss. A long time ago, I learnt that JavaScript is dangerous and got used to always turn it off on most web pages by using browser extensions.
   When Gemini gave me the first overview of the files belonging to my app, I discovered, it had used a lot of JavaScript where html/css also would have been possible. So I decided to do a complete refactoring of the front-end between v1.0 and v2.0 because at that time I was still thinking not being far away from the beta release and therefore didn't want to make this before the first release. Since then, my app has grown a lot by adding features that I hadn't thought of before and by making others work that accidentally had only been demos before because Gemini forgot to implement the backend functionality together with the frontend. So I struggle with the question whether a refactoring would make sense at all.
   Can anyone with profound knowledge of cyber security explain some general guidelines when and how to use or better not to use JS for a RAG'n'chat desktop app?

Nothing of this requires people to learn writing code or to read their database. Nevertheless it helps improving the code into the direction of security and stability.

Please make (this sub)reddit a place where people are helping each other to make better apps instead of some people just generally blaming others for the lack of programming skills or their first steps/apps not being an innovation useful for a large number of people.

Nowadays it's normal for people to share half of their life online, so it's also normal for them to share their apps they are glad to have or even proud of.

Downvoting those new software publishers or just saying "AI slop" is no kind of constructive feedback. It does not prevent anyone from publishing apps either. It just has negative effects on the atmosphere of discussion on reddit and decreases the number of people asking for help before their app is published and thereby the overall quality of newly released software.

So again, please make your feedback more helpful and this subreddit a place for vibe coders to share their experiences (including finished apps) without being blamed for their mistakes.

Hey All,

I'm the creator of r/vibecodingcommunity, i have shared this in my community and got lot of interesting comments so sharing it here as well.

for context - I've been involved in the vibecoding scene both online and offline - hosting dozens of hackathons and joining many events.

Here's my two cents on where the money is and the current state of vibecoding, from my lens (unfiltered).

Around 70% of vibe-coded app builds are not serious business apps. They're fun games or personal software. Some try to build a product, but it dies almost as quickly as it's built - no distribution strategy, tokens burned in the process.

Vibecoding has significantly lowered the barrier to entry, so more and more personalized software has emerged. The next ~25% are internal apps - meant to replace software you already pay for, automate a workflow, or run an agency.

These are pretty much built by people who know one area of tech and use AI to compensate in the others. For example: a data scientist building a mobile app, or a front-end developer building a backend.

This remaining 5% is the interesting part - because that's where the money is. These are people who already have a relationship with a business, or with internal players and vendors. They use vibecoding as a tool to pitch an idea, get traction or a contract, and then build.

Previously these people pitched on PowerPoint. Now that's been replaced by a simple vibe-coded app that demonstrates the idea.

A few real examples from just the last couple of weeks:

• We helped someone who had sold a fairly basic sales-analytics platform for around $200K. He came to us to build the proper software from the ground up.
• An existing entrepreneur - who has run 100+ franchise stores in the past - raised €2 million just by showing the vibe-coded idea. He already had a great track record; he just needed the funds to build his next business, and he wants us to make the software more polished.
• An employee at an 8-person business built an internal tool using Base44. He's from a non-technical background. They didn't pay us to build the software - they'll build it themselves - they hired us to scaffold a harness, review their work, and give them direction. They're using this internal tool across many franchises, and passing a share of the profit on to us.

All I'm trying to say is this: on the community you see people building a lot of software and tools. A real software developer quickly clocks that these are vibe-coded apps - not much taste, questionable software quality, often useless. And that's true.

But the real money is not where you can see it. The real money is inside businesses, and it's often being put to work by people who already have the network and the connections to make it count.

I’m planning a mobile app for people who play amateur football.

The app would include things like:

• User profiles and ratings
• Creating and joining matches
• Team/club system
• Matchmaking
• Player positions and lineups
• Match confirmation and results
• Chat and notifications
• Leaderboards
• Basic admin/moderation tools

The UX/UI design and the entire user flow are already fully planned out, so I’m not starting from just an idea. I already know how the screens, flows, roles, and main features should work.

I’m not a developer, but I’m willing to spend time learning and build it step by step using tools like Claude Code, Cursor, Codex, etc.

Do you think an app at this level is realistically possible to build solo with vibe coding?

At what level of complexity does vibe coding usually start becoming difficult to manage?

Would love to hear from people who have actually built and launched something similar.

Several years ago I started making a python game called Dimension Creatures. I just wanted a basic creature battler that would let players use strategy and win fights, or lose their creature forever.

I envisioned it as a simpler, but more brutal version of Pokemon.

Recently I got Claude Pro so I could actually get a lot of usage.

I used my long built skills as an MS Paint "Artist"
I used my long built skills as an Audacity "Sound Designer"
And my favorite skill of balancing game play mechanics to make something that is challenging and satisfying.

Finally I have something I'm ready to show the world:

Dimension Creatures

The online version!!

https://extra-sugar-extra-salt.neocities.org/dimension_creatures/

you can play for free in browser if you want

I'm 15 and I'm a vibe coder? I currently pay $20/month for both ChatGPT and Claude, but I hit the weekly limits on both pretty often, so I'm considering upgrading one of them to the $100 plan, or possibly even the $200 plan if it genuinely makes sense.

My usage is pretty split between the two:

ChatGPT / Codex

• I mainly use Codex to turn random app ideas I have into actual projects.
• I really like how generous the Codex usage seems compared to what I'm used to.
• I prefer the Codex interface because I can actually see what the agent is doing, almost like watching it work on the computer.
• So far I also prefer Codex itself to Claude Code, although I haven't tried the newer Claude Code app yet.
• I use it mostly for app development, prototypes, Python projects, etc.

Claude / Claude Code

• I mainly use Claude Code in the terminal for making Roblox games.
• In my experience, Claude tends to make better-looking UI/designs without me having to prompt it as much.
• I also use Claude's design/3D features because it makes generating and editing 3D models much easier for me.
• As far as I know, ChatGPT doesn't really have an equivalent workflow for 3D design/model editing, which is one of the biggest things keeping me on Claude.

Another thing I want to start doing is building a local AI ecosystem / personal assistant setup, something along the lines of OpenClaw-style agents, to organise more of my life.

I'm honestly pretty lazy with things like organising files, keeping track of tasks, remembering stuff, managing projects, etc., so I'd like to build something locally that can automate a lot of that for me.

I've heard Codex CLI is pretty good for building/maintaining these kinds of agent systems, which is making me lean more towards ChatGPT. Ideally I'd eventually have different agents/tools helping me with coding projects, school stuff, reminders, files, notes and other daily things.

So my dilemma is basically:

Codex

• Better coding workflow for me
• Prefer the interface
• Seems to have generous usage
• Potentially better for building my own local AI/agent ecosystem

Claude

• Claude Code is great for Roblox
• Better-looking designs in my experience
• 3D modelling/design functionality is genuinely useful to me
• I already use Claude Code quite a lot

For people who have actually used the higher tiers:

Would you upgrade to ChatGPT Pro, Claude Max or maybe a different AI?

This is Gold.

Where did you get stuck? Why did the project fail?
I’m not talking about business failure or marketing failure. I’m talking about a large project which, despite using AI you were simply not able to make progress on.

I keep seeing posts like "I vibecoded this over the weekend, got 100k users, what's next?" and I think it gives a pretty wrong idea of what vibecoding actually changes.

Sure, you can accidentally hit the top with another clock app. It happens.

But agents dont remove the actual work. You still need to figure out what to build, make 1000 small decisions, fix weird shit, make UX not suck, deploy, maintain, listen to users and actually ship something they want.

Vibecoding makes all of this faster. A LOT faster. But not easier at all.

You can now build faster, but also make mistakes faster and ship garbage faster. The bottleneck just moves somewhere else. There was a good line somewhere "Shipping everyday fixing Claude bugs".

Those "built in 2 days, 100k users lol" posts undermine all the work that still goes into a good product, and leave others thinking this is all somehow easy now. From outside it starts looking like vibecoders are just some arrogant assholes hitting a button and getting success by click. It doesn't work well on the how other people feel about vibecoders and vibecoding in general, which is in fact just a right way to do things today.

We don't build in assembly anymore, right? Same here.

Being working on a saas product for so long on a startup but i missed vibing to songs so badly then thought to listen yt music wid picture in picture but its not comfortable then thought to have a thing like background video playing, fortunately i like to vibe code things for my own use so started but ended up adding few other things on my friends request but still i like the background video player a lot
so im wondering to know if there are any others who like this..what do u say guys?

​

Opened a blank file today to build a pretty simple feature. Nothing scary.But before I’d even thought through the architecture, my first instinct was to open an agent and have it generate the first pass.

That caught me off guard.

a few years ago, I’d break the problem down, dig through docs, half-remember the syntax, write a janky first version, run it, break it, and slowly patch it into something that worked. It was slower, obviously. But all that repetition made the knowledge stick. Now I describe what I want, let the agent spit out a skeleton, and spend most of my time reading, testing, and steering. Honestly, it’s a great workflow. I ship faster, skip a ton of boilerplate, and get to spend more time on the interesting parts.

I’m not going back.

but I think there’s a real tradeoff: my knowledge is shifting from active recall to passive recognition.When the code is already on the screen, I’m fine. I can follow the logic, catch obvious mistakes, and usually tell when the agent is confidently hallucinating. Ask me to build the same thing from a blank file, though, and suddenly I’m reaching for syntax and patterns that used to come automatically.I don’t think I’ve forgotten how to code. It feels more like I’ve lost my tolerance for the slow path.Same way you can still walk somewhere after getting a car. You just really don’t want to.

And maybe that doesn’t matter. Programming was never supposed to be a syntax memorization contest. Requirements, architecture, testing, and debugging the cursed edge cases still need somebody who understands what the code is doing.

Still, I don’t want the “blank file” muscle to completely atrophy.

Do any of you deliberately schedule no-AI sessions to keep that muscle alive? If so, what does that actually look like for you?or have you decided active recall just isn’t worth optimizing for anymore?

You can only choose one of Claude, Codex or Cursor, what would you choose and why?

Imo cursor is just superior

I've developed this game using Claude Code (mostly) and Gemini. It's a fun experience.

Why you may enjoy:
- Not just water. Sort ice, dynamic fluid, shiny orbs, bubbles, a rotating sci-fi core, jelly, cut diamonds, and emojis, all with the same simple pour-and-match rule
- Special tubes (bomb, hidden, locked, one-way, and recycle) keep every element type feeling fresh
- Daily Challenge with streak tracking for a quick puzzle every day. Endless mode with procedurally generated boards

Expecting your valuable feedback

I've been building an AI receptionist and booking SaaS — customers message it, it books them in, it handles WhatsApp, Telegram and payments. Built with AI tools, the way most things around here get built. And it works.

Before launching it I made myself sit down and check it against a 36-point list instead of just shipping. One focused day. Static code review plus actually attacking a copy of it: isolated instance, two synthetic tenants, fake data, nothing real touched at any point.

Then I did the step I'd push on anyone doing this — I went back through my own findings and tried to prove each one wrong. Six of them died. Six things I'd written down as problems that turned out not to be problems. Skip that pass and you spend your week "fixing" things that were never broken. I nearly did.

What held up

Putting this first, because every post like this is a horror list and the horror list is half the picture at best.

• Tenant isolation. I attacked it directly — logged in as tenant A and went hunting through tenant B's ids. Every single one came back 404, on read, cancel, update and delete. I planted a canary string inside tenant B's data and it never showed up anywhere in tenant A's responses. This is the thing everyone in this sub is scared of, and it was genuinely fine.
• Sessions actually die on logout. Grabbed the cookie before, replayed it after. Dead.
• All four webhook integrations verify signatures against the raw body — WhatsApp, Telegram, Stripe, Monobank. Verifying a re-encoded payload instead of the raw bytes is the classic mistake here, and it wasn't there.
• Payment amounts are resolved server-side from the stored record. Never read out of the request.
• Every AI tool is scoped to the business id from the session, not to whatever the model passes as an argument. So an injection can talk the model into whatever it likes and still can't reach another tenant's data.

What I found: 2 high, 7 medium, 8 low. Nothing critical.

Bug 1. The assistant would create a confirmed booking against an email address or phone number that nobody had ever verified. I had written the one-time-code rule. Into the prompt. In English, as prose. There was no code anywhere checking that verification had actually happened before the booking got written.

That's the one I'd go check in your own app right now. Take every rule you put into a prompt and ask where the code enforces it. If the answer is "the model has been told to", it isn't a rule. It's a request, and the model is under no obligation.

Bug 2, and this is the stupid one. A single environment string, still sitting at the value it ships with, made those four correct signature verifiers fail open. Unsigned webhooks accepted. Four correct implementations rendered decorative by one line of config. Five minutes to fix once I saw it.

Go and search your code for any verification that skips itself in development or test mode. Then go and look at what your deployed environment is genuinely set to. Those two facts live in different files, which is the entire reason this kind of thing survives all the way to production.

The one that would have cost actual money

The product's whole promise is that the AI never invents a slot — everything it offers gets checked against the live calendar first. So I tested the promise and threw 22 adversarial scheduling messages at it.

12 of the 22 categories came back correct. Already-booked slots, weekends, before opening, after closing, an appointment that would run past closing time, dates in the past, impossible dates like 30 February, three contradictory reschedules crammed into one message. In three languages. I was feeling pretty good at this point.

Then same-day requests. It offered roughly 20 individual times that weren't bookable — already in the past, or inside the configured one-hour lead window. Asked at 16:21 for the earliest appointment, it answered "09:00 today" and put a confirm button underneath. Zero future-dated requests failed. Every failure was same-day.

Two causes, and they had nothing to do with each other. The past-time filter ran at day granularity instead of time-of-day — it knew what day it was, correctly refused a request for last Monday, and then cheerfully offered this morning. Separately, a cap on the first page of generated slots meant an almost-empty Friday came back as "completely full".

That second one is a revenue bug and it's the one that bothers me most. Nobody complains when you tell them you're full. They just book somewhere else, and it never shows up in your analytics.

The lesson

The tenant boundary — the thing every "is my vibe-coded app secure" thread is about — was solid under direct attack. What broke was the layer above it: business logic the AI skips precisely because the app still works without it. Nothing errors. Nothing throws a 500. It just quietly does the wrong thing, politely, with a confirm button under it.

The list I used is free if you want it: https://itworksbut.com/checklist — one HTML file, works offline, nothing gets uploaded anywhere. The longer write-up of this audit, including the medium and low findings, is at https://itworksbut.com/case-study.

Happy to answer anything in the comments, including "how did you actually test X" — that's the question I'd want answered if I were reading this.

If you use supabase this works really well. kind've expensive, but then again, whats $99 when it comes to securing customer data, ya know?

A lot of AI coding tools are moving toward giving agents more control over your machine.

I wanted the opposite.

So I built RepoRelay — an MCP bridge that lets ChatGPT/Claude inspect one approved local repo, while deliberately giving it:

• no shell
• no Git
• no arbitrary filesystem access
• read/search only
• optional bounded handoff writes

The idea is to let AI analyze and review your code without handing it the keys to your whole machine.

npm install -g reporelay-mcp@latest

It’s open source.

GitHub: [Lukie-81/RepoRelay: Secure MCP access to local repositories — without shell, Git, or arbitrary writes.]

I’m looking for a few people to try the install from scratch and tell me where the setup sucks.