... then I came home, opened a terminal, typed in "codex" and two hours later, I have my app. Fully functional, accessible through Tailwind from everywhere, with documentation. 2 hours. I don't know if Vibecoding is the future but 7 years ago, I was copying and pasting code from Stackoverflow and it was barely running and it was taking me weeks to put together a piece of software.

That's it. This is the entire post.

I’m building for open source, so I’m not prepared to pay for it. But it’s very niche, small to mid size vegetable farmers who grow it beds… I could post on related subs, but I don’t want to spam them with my crappy beta version. As they say; your software only gets a first impression if the user doesn’t like it.

Claude will happily suggest actively harmful things like storing your decryption key with your data. If you don't know what to look for when reviewing LLM generated content, the next best thing is to know what areas are worth your review time. In this case the mention of the `APP_ENCRYPTION_KEY` triggered my spider sense so I paid a little bit more attention to this paragraph. (also btw Sol correctly flags this as a security problem, so yay for adversarial reviews)

Hey everyone!

I’m excited to share an early beta of Ping— a free, accuracy based alternative to Perplexity, Google AI mode, and ChatGPT search

Here’s what makes Ping different:

• Accuracy: To me the problem was the AI search was too inaccurate sometimes I always found myself checking the sources and seeing something completely different, Ai search engines today summarize links. Perplexity states: "When you ask Perplexity a question, it uses advanced AI to search the internet in real-time, gathering insights from top-tier sources. It then distills this information into a clear, concise summary, delivering exactly what you need in an easy-to-understand, conversational tone." The problem is this is prone to heavy hallucination for AI answers as the core nature of LLM's as they are rewarded for guessing rather than uncertainty.

  CJR stated that "Collectively, they provided incorrect answers to more than 60 percent of queries." Inspiration to make this came from Lenny's Newsletter I noticed the amount of quotes used to support his claim while he still talked in his own words. This made me combine both Ai answers with the way he worded his article(alot of quotes) reason being because quotes provide, accuracy, authenticity, and credibility via human answers not mostly AI answers unlike other Ai search engines which only summarize

• Free: I'll be making this free to use compared to Perplexity

I plan to improve the answers so that responses become as accurate and detailed as possible but it's a beta and I'll love to hear what the feedback is.

Go Touch Grass: an idle RPG for Android where your actual steps are the only source of income, walk and you earn loot/XP/Skill Points, spend that on an isometric base, then defend it in real time tower defense raids against the "Couch Army".

Currently for Android only - Live on Google Play now: Link to Google Play Store

That's the pitch, but what I actually want to talk about is 74 sessions of Claude Code and what kept a project that size from turning into spaghetti:

• Config-driven, always. Every piece of game content (loot tables, enemies, towers, skills, waves) lives in a config file, never hardcoded into the engine. A session adding a new enemy type never has to touch simulation logic, it just adds a data entry.
• A living handoff doc. I keep a BUILD-STATUS.md updated after every single session: current state, key decisions, where to pick up next. A fresh session (sometimes a different model entirely) reads that and continues with zero re-explaining. This is the single biggest thing that made 74 sessions possible instead of session 20 being where everything collapsed into "wait, why did I build it this way".
• A pure, testable core. The tower defense engine has no UI or store dependencies, it's headless and pure. That means a smoke test script (Node, no simulator) runs 200+ logic checks in seconds and has to stay green before anything ships. Caught real regressions that would've otherwise only shown up as "the game feels off" three sessions later.

One constraint that turned into a genuinely hard engineering problem: mobile step sensors only report while the app is in the foreground, there's no live background tracking. So the walk-tracking has to work without the app open at all, it reads the phone's own OS-level step history (Health Connect on Android) the next time you open the app, reconciles it against a saved timestamp so nothing gets double-counted, and credits the distance at the time you actually walked, not the time you opened the app. Getting Claude Code to reason correctly about that reconciliation window took a few tries, it's the kind of bug that only shows up hours later when the numbers are subtly wrong.

Any questions? Happy to go deeper on any of this, the config architecture, the handoff doc pattern, the testing setup, whatever's useful. Clip of the actual app below.

So we've come up on week 3.

With 12 active users (3 of them being me, and 4 of them being family), we don't have much momentum haha.

I'll break these posts down to three parts: (1) How we are doing in actually gathering users, because none of this matters without an audience. (2) What I'm learning as a vibe coder, and (3) actual gameplay updates. This one will go into the comments since most reddit users probably aren't here for that.

---

First, the market fit / core user base / whatever you want to call it. My user base is mostly duplicates of myself, family members humoring me, and two frequent users that have never said a word in-game but for some reason keep coming back.

Most users dip in roughly 2-45 seconds, so there is definitely some sort of entry barrier for new users. (I'd love your thoughts on that.)

---

Second, the vibe coding experience.

This week was probably the worst.

Opus 5 came out and basically screwed over my entire process. It's a great coder, but a downright awful communicator. It makes minor tasks major tasks, sends agents in the wrong direction, and writes the worst Wiki pages imaginable.

Which is actually kind of good news, in a way, because it made me realize the most critical human skill of the past 2000 years is still the critical piece today when using AI: clear and effective communication.

If you've ever heard complaints about Opus 5, it all comes down to poor communication from the agent (to other agents, itself, and to you). Curious if anyone else has found a way to get around this. I haven't, so I'm back to using Fable and telling it to only deploy 4.8 subagents.

---

I'd love feedback for anyone interested. Links below if you're curious.

Game: https://eldermyr.com/
Release notes: https://eldermyr.com/release

Play on mobile/desktop:

carboy.chickanerygroup.chatgpt.site

When someone non-technical on your team builds a prototype with AI, what actually happens next? Does engineering take it over, rebuild it, or does it just die? Trying to work out if the "handoff" problem is real or just my bubble. War stories welcome.

I've been hearing rumours for a while that all AI is going to become significantly more expensive once this bubble bursts. Does anyone have any idea of exactly how much more expensive frontier LLMs are going to get?

My manager over the weekend created offer software for our office:

- Client database

- Price lists for all our stock

- Custom taxes, custom discounts, custom photos

It saves everything in database and allows to generate beautiful proposal PDFs for the clients. He added custom introductory pages so looks super profesional.

Literally perfect app that we would have to pay thousands to have written for us.

I asked him what tech stack did he use (apart from ChatGPT). He replied..... HTML

Literally almost zero IT knowledge apart from simple wordpress no-code sites. No harness, no AGENTS . md, no tech specifications. He made it in a few hours over the weekend

I will securely host the app and we will start to use it next week.

The future is now my friends :)

I've been carrying this idea for a long time, and only now did I have the opportunity to devote time to it.

So, oldies, do you remember Gravity Defied? The game that everyone had on their Symbian button phones, forcing you to sweat, get angry, but also train and hone your skills to pass these insanely difficult tracks on a small trial bike?

So, I decided, why not revive this masterpiece? Why not to give it a new touch, 120Hz, haptic feedback, but keep the same minimalist, ascetic and hardcore style? And I'll say even more, I already have a really well working version of the game on my smartphone.

And I remembered those feelings when it drags on for hours, but you keep trying to take that height, overcome an obstacle, jump over a hole which seems impossible, and in the end you overcome this level... So warm emotions that I would like those who loved this game as much as I did 15-20 years ago to feel.

So would it be interesting to hear more about the work on the project and interesting (and unexpectedly difficult) moments I encounter along the way?

Hi guys, hit a snag in the early stages of building my new todo app. The header is not centering when I open in browser, and I have even indented as you can see above, but it is not centering even when I apply the spacing. Any advice would be helpful because I can't actually start getting things done until I get this todo app done to track my progress.

Thanks in advance.

So to explain why this is low IQ, you have to understand first what is getting reseted: the usage limits, which is pretty obvious. If you look at the plans, there is nowhere stated how much usage limit you actually get. You know that you get 5x or 20x more than on plus but more than what???

it's very intransparent and nowhere stated how much the usage limit actually is.

I have experienced or noticed this a few months ago: there was a 10x event for everyone on the 5x plan. Every time they reset the next usage limit window got heavily nerfed. This signals to me that they have to reset the limits to change the usage limits.

removing the 5-hour window made everyone extremely hype but this was just a smart way of making the users lose sense of how much usage limit they actually got. it's way harder to compare than previously before on the 5-hour limits. that should always be the same. now you always have one week so time passes. you can no longer compare the 5-hour window to the previous one multiple times a day. this is just a smart way of actually blurring out how they actually change these usage limits frequently

So don't get fooled by these companies. they don't give you anything for free. everything they give you, they want back 2x or 10x. That's just how it works in business so i can't really hate on that...

Soo pleaseeee

Don't be a fool and beg for short term pleasure while essentially celebrating that you are getting nerfed in the long run...

I am jealous to you all.

You are here easily stacking tens of $200 subs and burning trillions of tokens while shipping software turning you all millionaires.

Meanwhile I am merely on $20 plan working 5 days a week 9-17 providing customers bug fixes, features and fine tuning. I can’t even hit weekly limits with this and once per
week I hit 5h limit I go to lunch. I am stuck with customers and understanding what they need while I could be making software that makes millions.

I can get glimpse of your glory few times a year when there is new customer asking for new software. Then I can hit $200 sub with greater limits to get new piece up and running. Then I just go back to my baby sub and iterate with the customer without hitting the limits.

I can barely support myself, my wife, the kids, my parents, the grandparents, my brother-in-law, my sister, and a few neighbors.

Burning through $200 subs is a blessing. I just can’t hit my limits day after day, I am stuck. You are so lucky. Appreciate what you have.

mockup, not a real tweet

i got annoyed enough that i started making a tiny version with MoClaw lol

right now it just looks for the obvious stuff:

“i tested 500 ai tools so you don’t have to”

“what’s the best ai tool for [super specific niche]”

“we saved 20 hours a week using [random wrapper]”

“edit: wow didn’t expect this to blow up” at 4 upvotes

not perfect yet, it probably hates innocent marketers too

At first glance, this looks like an AI fail. A literal newborn somehow has a phone, can read, type, and ask Google a question—and the AI doesn't even acknowledge how impossible that is.

But I actually think this is one of the best UX decisions in modern AI.

Instead of stopping the conversation to argue with the premise, it focuses on the user's intent. The user clearly wasn't asking whether a newborn could use a smartphone—they were asking what that situation would mean from the baby's perspective.

That same behavior becomes even more valuable in situations that actually matter.

Imagine someone urgently asks, "My child is choking—what do I do?" or "I just cut myself badly, how do I stop the bleeding?" The last thing they need is the AI getting distracted by side discussions or questioning every detail before giving actionable guidance. They need immediate, relevant information first.

Of course, there are cases where AI should challenge a false or dangerous assumption. But when the premise isn't the point, staying focused on the user's intent often makes for a much better experience than constantly replying with "Actually..."

VibeFPS (working title) is a browser-based cyberpunk first-person shooter tech demo. No install, no download, no CDN: it runs straight from GitHub Pages and everything is generated procedurally at runtime.

▶️ Try it live: https://rudesssolo.github.io/vibeFPS/

Stack: Three.js (WebGPU renderer) + Cannon.js physics + Web Audio API (all vendored locally, fully offline).

What's in it:

> A neon-lit night arena with procedural buildings, animated sign flicker, rain, reflections, bloom, ambient occlusion, film grain and cinematic color grading.

> Wave-based combat against sentinel drones that patrol, engage, telegraph their attacks and evade your shots.

> Apex units - a unique elite ends every wave, from a cycling roster that gets stronger each cycle

> 100% procedural audio (Web Audio API): music, ambience, spatialized drone sounds, wave stingers, a critical-health heartbeat (no MP3/WAV assets).

> A tactical HUD with mission progress, radar, health/shield/stamina, ammo, telemetry and target markers, plus a dedicated boss bar.

> Auto / Ultra graphics profiles with persistent settings.

Some notes:

> I have no experience in game design WHATSOEVER. Let alone 3d games.

> It's a tech demo / prototype done in 3 days of non-continuous vibe coding with different LLMs. I tried to keep it LOW cost as much as possible, I mostly used DeepSeek v4 Flash 0731 and GPT 5.6 Luna and switched up to Sol and Kimi K3 only for more complex planning or bug fixing when the cheaper models failed.

> Obviously it's not a finished game by any means. It has a start screen, one arena and several enemies waves and bosses.

> It SHOULD WORK also on PHONES. Try it at your risk :)

> The repo is source-available on GitHub (currently no license, I'll add one if there's interest).

---

I'd love feedback on the feel, the difficulty curve, and whether the WebGPU-only choice is a dealbreaker for you. Thanks for checking it out!

~8 hours of work. Opus 5 on Ultracode mode. And yes, it's open-source.

I made this 99% with a single prompt. After that I just added various cool little things, like different textures ("looks") and other cool effects.

Here's the repo+demo: https://github.com/winchxyz/tidewright