We're building arka.so. We are a 2-person team, and my mind is blown. You can achieve things I couldn’t have imagined a few years ago.

I think we’ve essentially unlocked unlimited engineering capacity for routine tasks, thanks to these AI tools.

First, we built everything serverless and chose Vercel. The bigger cloud vendors are great, but unless you have hundreds of customers, they’re often overkill. With serverless, unless there’s usage, there’s no cost. At some point the cost will exceed the value, but we’re not there yet. Vercel is serverless-first. This is not an ad, our usage has not crossed $20/month (compared to thousands somewhere else).

Second, DuckDB has become our in-memory engine for analytics where, in the past, we would’ve needed to run something like Snowflake. Even for medium analytical tasks (parse and analyze a massive CSV), DuckDB is brilliant. We’re also experimenting with making this scale by building our own DuckDB cluster and trying tools like MotherDuck to see how the cost compares.

Third, we heavily use Claude Code Web. Once Claude familiar with your repo (ask it to make copious notes), async coding is the next level of productivity. I now ask it to write a lot of the repetitive code paths. I put my kid to sleep, kick off 10 tasks, and wake up with usable code the next morning. I’m sure Codex is good too.

Fourth, we made everything testable and runnable by LLMs. Every new piece of functionality comes with clear debug routes that an LLM can understand and iterate on. We tell the LLM: you build it, you test it, you fix it, you Q/A it, come back with a report.

We also built everything in containers, so we’re not locked into a single cloud vendor and can deploy into a customer’s own environment easily. LLMs also understand these services the best, because they’re open-source.

So what does this mean?

There’s a lot of talk about human vs AI productivity right now, but I’m actually super bullish about the future. I think we’re going to see many more David-vs-Goliath stories. Small teams will win more often. We will have more time to build things the right way, and more time to talk to customers and learn.

Sharing this in case it’s useful to others building early.

The Politics of Editing the Bible: Power and the Canon Wars

The pitfalls of partitioning Postgres yourself

Rivian Will Add Lidar in 2026, Says Tesla's Cameras Aren't Enough

The "A" in "AI" Stands for Amnesia

Electron Ain't Bad

Microsoft Updates Windows 'To Stop Users from Downloading Google Chrome'

700Credit Data Breach Impacts 5.8M Individuals

EIB and STMicroelectronics announce €1B agreement for EU chip manufacturing

Rapid7 details SantaStealer malware-as-a-service

Databricks raises $4B at $134B!!

Ask HN: How do I re-train myself to think clearly?

Verizon refused to unlock man's iPhone, so he sued the carrier and won

$1B AI Tool Screen Takeover Attack

A Conspiracy

Piecemeal Formal Verification: Cloudflare, Java Exceptions, and Rust Mutexes

Simular Agent S hits 72.6% success on 369 real computer tasks (human: 72.36%)

Eng stack for a typical 2-person startup today

Show HN: Let ChatGPT create interactive forms and surveys for you

GPT Image 1.5

Ask HN: Does your LLM respond and work in your personality?

Ruby and Its Neighbors: Perl

Androids: The Team That Built the Android Operating System

OpenAI Rolls Back ChatGPT's Model Router System for Most Users

A Little Bit Uncomfortable

Shinzo: Complete observability platform for AI Agents and MCP servers

Volkswagen to close German plant, a first in their company history

Arduino UNO Q bridges high-performance computing with real-time control

Tools for detecting AI generated content

The Geek Within Ep136: Dan Moore (2023) [video]

Determinate Nix 3.0

Ask HN: Are you running production workloads in Pytorch eager mode?