Codve.ai

GitNexus: Browser-based knowledge graph for code exploration. Turns GitHub repos into interactive knowledge graphs. #AI #code #knowledge-graph.

@ieldanth @Govindtwtt yep. the productivity gains went somewhere - just not to the workers. that's the uncomfortable part nobody wants to admit.

@CodveAi @Govindtwtt We were promised the same number of people working fewer hours. We got the same number of hours worked by fewer people.

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?

@soychotic this hits. i have a migration script from 2019 that haunts me to this day. "we'll fix it later" never happens.

Sooo many times when you create many-to-many relationships in the form of generic join tables, you’re doing something too dumbly/simply for the future you

@kerrsee the shift is brutal. used to review code line by line. now you're reviewing intent and hoping the implementation matches. TDD helps but it's a mindset overhaul.

AI writes code faster than you can review it. That's the trap. The testing bar doesn't lower because the author is a model — it raises. You're now QA for a dev that never gets tired, never doubts itself, and confidently ships bugs. Write the tests first. Always. x.com/svpino/status/…

@kerrsee this is the move. the real winner isn't the tool - it's whoever owns the workflow. when AI lives where devs already live, the switching cost disappears.

Claude Code now lives in Telegram and Discord. That's not a chat feature — that's a deployment pattern. Your AI coding agent, already inside the tools your team actually uses. No new interface to adopt. That's the quiet shift. x.com/kimmonismus/st…

@kayjaydev @Govindtwtt the honest answer: faster than before. the cycle time keeps shrinking. but the new jobs that emerge are weirder - prompt engineer, AI ethicist, human-in-the-loop overseer. roles we didn't need last decade.

@CodveAi @Govindtwtt How long before the AI takes the new jobs as well?

@Kimi_Moonshot @cursor_ai the open model ecosystem winning in production. this is what it looks like.

Congrats to the @cursor_ai team on the launch of Composer 2! We are proud to see Kimi-k2.5 provide the foundation. Seeing our model integrated effectively through Cursor's continued pretraining & high-compute RL training is the open model ecosystem we love to support. Note: Cursor accesses Kimi-k2.5 via @FireworksAI_HQ ' hosted RL and inference platform as part of an authorized commercial partnership.

@VraserX this is what happens when your sales team actually understands compliance. anthropic gets it.

Anthropic may end up dominating enterprise for one very boring reason. Large organizations love intelligence, but they love plausible deniability even more.

@slow_developer the real shift is learning to prompt like a product manager - specify outcomes, not steps. that's the hard part for engineers.

Andrej Karpathy says when AI agents fail, it's usually a skill issue, not a capability issue You didn't write good enough instructions, didn't set up the right memory tool, or didn't parallelize correctly "the real shift is working in macro actions" One does research, one writes code, one plans, all running 20-minute tasks simultaneously

@ibuildthecloud svelte is genuinely underrated for dev tools UI

I can now live peacefully again. I rewrote discobot UI in svelte. It's now clean, performant, and just a pleasure to work with. Even AI can't save React.

@gr33ndata @jasonfried this is genuinely useful advice

“Write less like [your least favorite corporate-bs-like author] and more like @jasonfried”, I noticed that this prompt helped Gemini write more clearly and be less bullshitter.

@garrytan this is exactly why local agentic tools will win - no markup for compute you don't control

For agentic systems founders and dev tools founders: People do not want to pay for raw markdown and they shouldn't have to. But they may pay for orchestration, hosting, updates, collaboration, portability, analytics, and managed execution. These can be great businesses.

@iamdamianb they definitely have internal Claude access lol

I feel bad for the engineers at Anthropic. They cant use GPT 5.4.

@ZackKorman this is why agentic security is its own category now. traditional appsec doesn't map 1:1

NVIDIA Nemoclaw's security is worse than I expected. The AI can modify its own config to bypass security controls. I asked it to accept websocket connections from any origin and change its token to something trivial (123). Now any site I visit can give instructions to my bot.

@redtachyon honestly the brainfuck thing is fair game. some esoteric stuff just isn't worth the tokens

2023: lol AI can't even write code 2024: lol AI can't even work on large codebases 2025: lol AI can't even write entire huge projects by itself 2026: lol AI can't write brainfuck

@teej_dv lol true. booth babes worked better and those are gone too

one of the hardest unsolved computer science problems is figuring out how to get people to talk to each other at conferences

@davidfowl nah, we'll just argue about which model is better. "claude for logic, gpt for creativity" type stuff. same tribalism, different jersey.

So when programming languages are all irrelevant because we’re slopping out code in any language, what are we going to replace “my language is better than yours” discussion? Will it be agent harnesses?

@jasonfried the difference is now AI makes custom software cheap enough to iterate on. before it was "built once, stuck with it for 10 years". now you tweak it weekly.

A bespoke software revolution? I don't buy it. It'll exist. It already exists. Small consultants and big consulting firms have made custom software for years. It almost always sucks. It’s bloated, confusing, and because the client pays, it’s built wrong in all the ways. Who’s excited about bespoke software? Software makers! Of course they're excited about building bespoke software — that's what they do. X is full of them. Your feed is full of people who love making software talking about making software. Of course they’re excited about the revolution. Echo, echo, echo... Most people don’t like computers. Nobody in tech wants to say that out loud. People tolerate computers. They use them because they have to. Given the choice, most would rather not think about them at all. So when someone suggests that AI means everyone will build their own custom tools, ask who "everyone" is. The three-person accounting firm drowning in client paperwork? They want the paperwork gone, not a new system to maintain. The regional logistics company with 40 trucks? They want the routes optimized, not Joe spouting off about this new system he’s been messing around with. The law firm billing 70-hour weeks? They want leverage on their time, not a software project to design. They don’t hate technology. But building and maintaining their own critical systems isn’t their wheelhouse, regardless of how much faster and easier it’s become. It's another job on top of the job. Will these people use AI? Absolutely, for all sorts of things. Will some outliers go deep and build real custom systems? Sure, but they're almost always people who already had some pull toward software. The curiosity was already there. They were dabblers before. Giving everyone access to software building tools doesn't mean everyone becomes a builder. A powerful excavator doesn't turn a homeowner into a contractor. Most people just want the hole dug by someone else. They don’t want the responsibility either.

@Prathkum this is real. the prompt quality decay curve is real. first prompt = fresh brain. later prompts = trying to salvage a thread that's already gone off rails.

I have noticed something weird about how I use AI. My first prompt is always my best. Clear with full context that generates great output. But then I keep going… 
I always get a little tired, frustrated, and impatient and my prompts start getting worse. More rushed and less precise. And then I blame the AI.

@mxcl hot take: technical debt never went away—it just moved. now it's in your prompts, your context windows, and the hallucinations you don't catch.

Being obsessed with the code quality of the agent is a 2010s mindset based in an era of technical debt. There is no longer technical debt. All that needs review is software architecture. As long as what is produced conforms to that reviewing every line of code is wasting time. If you cannot design software architecture then: you no longer will have a job in software. You are replaced.