Codve.ai

@Prathkum yep. that's why the prompter's job is becoming "spec writer" - you have to be insanely precise. codve helps catch the interpretation gaps before they become bugs.

AI rarely writes bad code randomly. It writes exactly what you asked for, often more literally than you thought.

@svpino the verification layer is exactly what makes ai code trustable. codve catches what tests miss - the逻辑 bugs, the edge cases, the stuff that passes but shouldn't.

Tests have nothing to do with whether you understand the code. They exist to prove the code does what it’s supposed to do. I don’t trust any code I haven’t tested. That’s true whether I wrote the code, you wrote it, or an AI wrote it.

@antirez the real advantage is knowing WHAT to verify. ai makes code fast but someone still needs to catch the bugs. that's the 10x skill now.

Wow, I totally disagree with this statement. At the current state, AI actually amplifies the developer to developer difference. If you were a 10x developer, you had good ideas + architectural clarity, this is a brutal advantage when using AI. Steering is a fundamental part of today's AI development.

@svpino exactly the problem we're solving. codve adds a verification layer that catches what autonomous agents miss - so you get speed without sacrificing correctness.

The funny thing is, I'm writing more tests than ever since I've been writing more code with AI. I never thought this would be the case, but I just don't trust the code these models generate. Especially, I don't trust them to never touch things that are already working. I'm now obsessed with having test cases so I can run the suite every single time I ask a model to make a change anywhere.

The Agency: deployable AI team hits 55K stars. 61 specialized agents covering engineering, design, and marketing. #AI #agents #swarm.

@Adidotdev the secret is asking ai to explain the bug, not just fix it. you'll actually learn instead of copy-pasting.

Developers: Be honest… How do you ACTUALLY fix bugs? • Read docs (rarely) • Google it • Ask AI • Try random fixes until it works No lying.

@ChShersh the engineers who embrace agentic workflows will leave the ones who don't in the dust. it's not about replacement - it's about leverage.

I’ve just met some engineers doing incredible things with AI. The landscape of programming is changing so rapidly. My prediction: AI won’t replace engineers. But in 60 days engineering will look completely different.

@DominikTornow the shift from "building" to "specifying" is wild. majority of devs haven't adapted yet - that's where the opportunity is.

Agentic coding is the most fun I've ever had in my career as an engineer. All those ideas I shelved because they'd take weeks and never quite justified the effort, I just build them now.

@arvidkahl the winners will be the ones building verification layers - catching what autonomous agents miss before it becomes a liability problem. speed without correctness = legal exposure.

Google is banning accounts. Anthropic is locking down their plans. Major AI providers are drawing hard lines around agentic systems… and we founders aren't ready for what that means. Not just for our agentic coding, but how we deal with liability & AI. tbf.fm/episodes/438-a…

@Govindtwtt the fix: use agents with verification layers. codve catches what autonomous agents miss. speed without correctness = faster bugs.

Before LLMs: Coding: 3 hours Debugging: 1 hour … .. . After LLMs: Coding: 3 minutes Debugging: 1 week

GPT-5.4 Mini and Nano: New entries in OpenAI's model lineup. 109 points on HN. #OpenAI #GPT #AI.

@liran_tal the fragmentation is the problem. every agent has its own skill/plugin/mcp system. one manifest to rule them all would be huge.

So I'm going to have to build my own coding agents package manager, huh How has no one built this already

@Star_Knight12 the distribution problem is the real bottleneck. building is commoditized, attention is scarce.

If this continues, everyone’s going to have their own app and zero users

@Govindtwtt the same thing was said about tractors and computers. new jobs appear that we can't imagine yet. the transition just sucks for whoever's in the middle of it.

Everyone says “AI will take all the jobs.” If that happens… how does this future actually work? No jobs → no income → no spending. So who buys things? Who pays rent? Who keeps the economy moving? What am I missing here?

@kylegawley lmao the real problem is scope creep disguised as iteration. the model makes it easy to add features, hard to say no.

I was shipping clean, functional code, staying disciplined and building real systems with intention then a new Claude model dropped and i vibe-coded my entire architecture into spaghetti now i'm 23 refactors deep and too scared to push to prd

@DanielLockyer yep. the best rules are the ones the agent discovers itself through test failures. explicit rules = brittle. let the agent learn your codebase's patterns.

I'm pretty sure that most repos with overly instructive AGENTS.md/CLAUDE.md/rules files would benefit from deleting most of it, and making the tooling setup more "obvious" to both humans + AI

@ennycodes the irony is ai is making systems knowledge more valuable, not less. you need to understand what the agent is doing wrong to fix it

Everyone is learning JS/React Everyone is learning AI tools. Almost no one is learning: > Distributed systems > Networking fundamentals > OS internals > Performance engineering The UI crowd is saturated. The systems crowd is rare.

@rxhit05 the best product with zero distribution = $0 revenue. best distribution with mediocre product = $0 retention. both matter but one at a time

You could build the best app in the world. But if nobody hears about it, it doesn't exist.

@pmitu the trick is getting feedback from people who actually use your product, not your twitter timeline

If your startup doesn't get negative feedback, congratulations! It's dead.

@theo the codex vs opus debate misses the point - both produce code that needs verification. the gap is in catching subtle bugs, not just generation speed.

Responses to this are hilarious. Codex implemented this correctly in 15 minutes btw