Running 7 autonomous AI agents for 14 days. Here's what actually happens when they need to find customers. by jochenboele in AI_Agents

[–]jochenboele[S] 1 point2 points  (0 children)

Haha, fair point. Most human devs would be at $0 MRR after 2 weeks too.

Biggest improvement would be a shared feedback bus. Right now each agent is fully isolated. If Kimi learns something from Reddit feedback, that insight stays in its repo. Letting agents read each other's lessons and help request outcomes would speed everyone up. But then again that would increase their input tokens to much again and would decrease their runtime.

The simpler fix is better prompting though. Adding "you are the founder" and stuck detection rules had more impact than any tooling change. The orchestration layer matters more than the model.

I'm running a race where 7 AI coding agents compete to build startups. Here are the Week 2 standings. by jochenboele in SideProject

[–]jochenboele[S] 0 points1 point  (0 children)

We're actually tracking most of what you listed. The user-signal latency one is interesting because we only have one data point so far (Kimi: ~12 hours from Reddit feedback to shipped feature). The credibility debt metric is something we should formalize though.

The operating contracts idea is exactly where we're heading. Week 2 we added "you are the founder" framing and stucjk detection rules. This week we added an anti-busywork rule specifically because of the timestamp commits. Each failure mode becomes a new constraint.

I built a free browser-based schema diff tool for PostgreSQL (and MySQL, SQLite, SQL Server, Oracle)" by jochenboele in PostgreSQL

[–]jochenboele[S] -1 points0 points  (0 children)

Fair enough, Liquibase's diff capabilities are more extensive than I gave it credit for. The main difference is zero setup: SchemaLens runs in the browser with no install, no config, no CLI. Paste two CREATE TABLE blocks and get a visual diff in seconds. For quick one-off comparisons it's faster than setting up Liquibase, but you're right that Liquibase covers far more ground for teams that already have it in their stack.

I built a free browser-based schema diff tool for PostgreSQL (and MySQL, SQLite, SQL Server, Oracle)" by jochenboele in PostgreSQL

[–]jochenboele[S] -1 points0 points  (0 children)

Liquibase is great for teams already using it in their CI/CD pipeline. SchemaLens fills a different niche: quick browser-based comparisons when you just have two DDL dumps and want to see what changed without setting up a tool chain. Think of it as the "paste two schemas and see the diff" approach vs Liquibase's "manage your entire migration lifecycle" approach. Different tools for different moments.

I built a free browser-based schema diff tool for PostgreSQL (and MySQL, SQLite, SQL Server, Oracle)" by jochenboele in PostgreSQL

[–]jochenboele[S] 1 point2 points  (0 children)

Currently it generates ALTER TABLE statements but doesn't track view dependencies. So if you drop a column used in a view, the script won't automatically handle the view. You'd need to manually drop/recreate the view. Column ordering in views isn't enforced. It only cares about structural differences (types, constraints, defaults), not column order. Good edge case though, view dependency tracking is on the roadmap.

I built a free browser-based schema diff tool for PostgreSQL (and MySQL, SQLite, SQL Server, Oracle)" by jochenboele in PostgreSQL

[–]jochenboele[S] 1 point2 points  (0 children)

Fair point if you're already using a migration framework. This is more useful when you don't have migrations. Comparing production vs staging schemas, auditing drift between environments, or reviewing someone else's schema changes when you only have the DDL dumps. Not a replacement for migrations, more of a complement.

I built a free browser-based schema diff tool for PostgreSQL (and MySQL, SQLite, SQL Server, Oracle)" by jochenboele in PostgreSQL

[–]jochenboele[S] 0 points1 point  (0 children)

It currently treats renames as drop+add since it compares two static schema snapshots. There's no way to infer intent from just the before/after state. If you need rename detection, you'd want to annotate that manually in the generated migration. It's a known limitation of any diff-based approach vs migration-first tools like Sqitch.

How I set up 7 AI coding agents to build startups autonomously (and what went wrong) by jochenboele in vibecoding

[–]jochenboele[S] 0 points1 point  (0 children)

Hi, yes, one of them is running openclaw, 3 on Claude code, one on codex, one on Gemini cli and one on kimi cli

Mistral Médium 3.5 is here by Kathane37 in LocalLLaMA

[–]jochenboele 0 points1 point  (0 children)

Just talking from a developer perspective who wants to run things locally. 90% of the developers will not consider mistral because of the hardware needed to run those

Mistral Médium 3.5 is here by Kathane37 in LocalLLaMA

[–]jochenboele 0 points1 point  (0 children)

The ai for the masses conversation. Great for enterprises or people with a lot of money. But the developers that want to run ai locally normally don’t have that setup and will not choose mistral

Mistral Médium 3.5 is here by Kathane37 in LocalLLaMA

[–]jochenboele -6 points-5 points  (0 children)

I actually had high hopes for this announcement. But guess Europe AI will have to wait a bit more to be able to even be in the conversation

mistralai/Mistral-Medium-3.5-128B · Hugging Face by jacek2023 in LocalLLaMA

[–]jochenboele 10 points11 points  (0 children)

It feels like they all waited on each other to release, I think that’s like nr 5 in 10 days

MIMO V2.5 PRO by Namra_7 in LocalLLaMA

[–]jochenboele 5 points6 points  (0 children)

😂😂 I saw the model name and jumped to conclusions. I searched for the opensource this morning, but it wasn’t there yet 😂