Two indie hackers shut down their 3-year project Lutains, citing exhaustion and a failed pivot

·11 views

Lutains, a project built over three years by two indie developers, is being shut down after thousands of euros were lost. The founders say they moved too slowly, built too many untested versions, and neglected sales. They also say their target users were too technically skilled to need a paid tool, since AI now lets them build their own. Living costs in France and the strain on their relationship and finances weighed on the decision. Despite the failure, the founders say they gained skills in offers, copywriting, branding, and AI-integrated app development.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer moves production server from Easypanel to Tugport in one command, hits five bugs

A developer migrated their main Hetzner server, which hosts Telegram bots, a Git server with CI runner, two blogs, a game server, and several databases, from Easypanel to Tugport, a new open-source deploy panel. The tool offers a dry-run mode and a migration command that imports configuration, moves databases one at a time, starts apps from their existing images, and swaps the proxy with an automatic rollback path. Of 57 services across 14 projects, 54 were running on Tugport after the move, with the other three already stopped beforehand. The first production run exposed five bugs, including unfilled environment template variables, placeholder domains breaking health checks, a stale network conflict, and Telegram bots clashing with their old copies. The first three fixes were released the following day, while the server later faced a heavy load spike.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Same Kimi K2 model scores 84.63% to 100% on tool-call schema accuracy across hosts

Moonshot's K2 Vendor Verifier repository shows the same model weights producing very different tool-calling results depending on the host serving them. Using an identical 4,000-request test set and Moonshot's own endpoint as the reference, Fireworks achieved 100% schema accuracy while Together reached only 84.63%. Across 15 Kimi K2 Thinking deployments, the spread was about 16 percentage points, and a separate K2 0905 table showed a gap of roughly 28 points. The analysis also notes that a high schema score can mask poor decisions about when to call tools, so the trigger F1 metric must be read alongside it. Because agent sessions involve many calls that must all validate, small per-call error rates compound into significant session failure rates.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Agents Speed Up Code Writing, But Merging Pull Requests Now Slows Teams

A developer reports that AI agents can produce around twenty pull requests in an hour, yet merging them consumes the rest of the day. Each merge tends to create conflicts for later ones, and continuous integration checks add further waiting, especially for feature changes that touch many files. Anthropic reportedly saw merges into its monorepo rise from about 2,500 a day in May to more than 30,000 in September, prompting it to build its own source control system, Scion. The author argues that the bottleneck has shifted from writing code to managing it after it is written. Existing workflows were designed for humans opening a few pull requests daily, and stacked pull requests offer only partial relief.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SIMID separates interactive ad creative from video delivery for publishers

IAB Tech Lab's SIMID standard offers a more focused way to integrate interactive ads, keeping interactive creative distinct from media delivery. Under this model, VAST carries the media and interactive resources, SIMID handles interaction, and Open Measurement covers measurement and verification. Publishers must confirm that specific players and configurations support the intended interaction, since a SIMID resource in a VAST tag does not guarantee support. Teams are advised to build a compatibility matrix recording destinations, player versions, input methods, and fallback behavior, with explicit approval of how unsupported inventory will be handled.

0 comments Read more at DEV Community