Clock Lobster — News

The Power of Intentional Constraints

Mon, 31 Aug 2026 17:00:00 -0700

The Power of Intentional Constraints

Published 2026-09-01

We often chase moreΓÇömore tools, more hours, more options. Yet the most productive creators and teams thrive on less. A recent insight from DeRonin_ cuts to the core of this paradox: constraints are not limitations; they are catalysts.

What the Insight Reveals

DeRonin_ observed that when we artificially narrow our scopeΓÇöfewer tasks, shorter deadlines, reduced choicesΓÇöour brain shifts from frantic multitasking to focused problem-solving. This isn’t just about time management; itΓÇÖs about cognitive energy. Unlimited options lead to decision fatigue. A single, well-defined constraint forces us to prioritize what truly matters.

The Underlying Principle

This idea aligns with the Yerkes-Dodson law: performance peaks at a moderate level of arousal (pressure). Too much freedom breeds procrastination; too much stress breeds burnout. Intentional constraints create the “just right” environment. Think of it as setting the stage for flow.

How to Apply This Today

Time Boxing: Dedicate a fixed 45-minute block to one task. No interruptions. The deadline drives action.
Tool Reduction: Use only one note-taking app for a week. The simplicity forces clarity.
Scope Limitation: When starting a project, list exactly three outcomes. Delete everything else.

Real-World Example

A design agency I know limited client revisions to two per project. The result? Clients thought harder about feedback, and the team delivered faster, higher-quality work. The constraint became a filter for what was essential.

The Takeaway

Next time you feel overwhelmed, don’t addΓÇösubtract. Set a constraint that narrows your focus. As DeRonin_ reminds us, the boundaries we choose can become the launchpad for our best work.

Browse all News

DeepSWE Value on a 1M-Token Codebase: Flash, Pro, or Luna?

Fri, 21 Aug 2026 17:00:00 -0700

News

DeepSWE Value on a 1M-Token Codebase: Flash, Pro, or Luna?

Published August 22, 2026

Series: News — Model appraisal
Published: 2026-08-22
Author: Victor Salmon
Dataset: Clock Lobster LLM-Cost-Comparison

Short answer: on a million-token codebase, DeepSeek V4 Flash 0731 is the practical recommendation for routine implementation. GPT-5.6 Luna is the better middle ground when the task needs more independent judgment. DeepSeek V4 Pro buys a higher DeepSWE score, but the extra reasoning tokens and higher output price mean that it produces fewer successful solutions per $100 in this modelled workload.

This is not a universal ranking. It is a costed scenario for independent programmers working on large repositories, where the whole codebase is available to the agent on each solution attempt. That distinction matters more than a leaderboard screenshot.

What does the comparison show?

The table below combines the published DeepSWE v1.1 score with a one-million-token uncached input and a ten-thousand-token visible answer budget. Thinking or effort tokens are counted as billed output. “Successful solutions per $100” is the number of attempts affordable at that cost multiplied by the DeepSWE pass rate.

Model	DeepSWE	Input $/M	Output $/M	Effort multiplier	Cost / attempt	Attempts / $100	Successful solutions / $100
DeepSeek V4 Flash 0731	54.4%	$0.14	$0.28	1.34×	$0.144	696	378
DeepSeek V4 Pro 0813	62.7%	$0.435	$0.87	1.57×	$0.449	223	140
GPT-5.6 Luna	67.2%	$0.20	$1.20	1.25×	$0.215	465	313

DeepSeek V4 Pro 0813 is the GA checkpoint represented here, using the published 62.7% DeepSWE result and $0.435/$0.87 pricing.

How I accounted for the extra token burden

A cheap input token does not make a large-repository task cheap. If the agent needs the whole codebase, the first pass is already roughly one million input tokens. On top of that, a reasoning model may generate hidden effort tokens before it writes the answer or calls a tool.

For a comparable calculation, I used:

1,000,000 uncached input tokens for the repository;
10,000 visible output tokens for the implementation and tool loop;
the local measured thinking-token ratios for DeepSeek Flash (34%) and Pro (57%);
a conservative 25% effort allowance for Luna, because the published GPT-5.6 table reports DeepSWE and pricing but not a directly comparable hidden-token ratio.

That gives Flash 13,400 billed output tokens, Pro 15,700, and Luna 12,500. The cost formula is simple: 1M × input price + effort-adjusted output × output price. If your repository is 1.4M tokens, scale the input portion by 1.4. If your harness reuses a prompt cache, the real bill can be materially lower.

Why a higher benchmark can be an expensive trap

A lot of independent programmers are solving this problem in different ways. Some use one model for everything. Some keep a frontier model open for architecture and hand routine changes to a cheaper agent. Some split the repository into services, keep a tight task ledger, or use tests as the interface between a planner and an implementer.

The trap is looking at a higher benchmark for an inexpensive model and deciding that you should spend for a much more powerful tool than you need. A benchmark measures capability on a task distribution. It does not tell you whether your next change needs that capability, whether the model will see a clean specification, or whether the extra reasoning will prevent more rework than it costs.

In this scenario, Pro has the highest effort burden and the most expensive output. It scores better than Flash, but the score improvement does not pay back the price difference when the whole million-token repository is sent every time. Luna is a more interesting compromise: its DeepSWE score is higher than Pro’s in the published table, while its post-cut price makes it less costly per attempt.

The workflow I would actually use

Planning and building are different jobs.

I would use a very smart model — DeepSeek V4 Pro, GPT-5.6 Sol, or Claude Opus — to reduce uncertainty first. Ask it to inspect the repository, identify the smallest safe change, name the files and invariants, and write a plan that another agent can follow. This is where a stronger model earns its keep: not by writing every line, but by making the problem smaller.

Then I would orchestrate the plan with DeepSeek V4 Flash 0731 or DeepSWE. Flash is my recommendation here because the combination of 1M context, agentic coding score, and very low price makes repeated implementation and test loops affordable. DeepSWE is also a sensible choice when its harness, tool use, or task specialization fits your workflow better.

The expensive model should clarify the work. The inexpensive model should do the work that has already been clarified.

What this table does not tell you

DeepSWE is a useful long-horizon signal, not a promise that any model will solve your repository. The benchmark’s tasks, harness, tool permissions, test quality, patch size, and retry policy all differ from your project. The cost model also assumes uncached input and one fixed output budget. Real agents may spend less, spend much more, or fail early.

For a fair decision, measure your own task mix. Take ten representative issues, run the same harness, record total billed tokens and human rework, and compare cost per accepted change — not just cost per attempt.

Capability is a budget. Spend the most of it where it shrinks the problem, then let cheaper models carry the pieces.

Browse the full benchmark series · Use the cost-per-word calculator · See how Clock Lobster builds agent workflows

Sources: DeepSWE v1.1 leaderboard, OpenAI GPT-5.6 release benchmark table, OpenAI July 30 pricing update, and the Clock Lobster benchmark catalog.

Kalshi Bets on a Market for AI Computing Power

Mon, 13 Jul 2026 17:00:00 -0700

News

Kalshi Bets on a Market for AI Computing Power

Published July 14, 2026

Series: News — Article Review Published: 2026-07-14 Source: Bloomberg Author: Victor Salmon

The article

Kalshi — the prediction-markets exchange — is pushing to turn AI compute into a tradeable commodity. Per Bloomberg's Katherine Doherty (July 14, 2026), Kalshi is offering a forward curve tracking compute — "compute" being shorthand for the power, storage, memory, and GPU resources that feed AI.

The curve is built from Kalshi's own event contracts, spanning various GPU grades, locations, and tenors, on both weekly and monthly bases, reaching up to a year into the future. In plain terms: a market that plots where the rental price of AI hardware is heading.

Kalshi isn't alone. This is the third such move in 2026 — CME Group announced a futures market for AI computing power back in May (partnering with Silicon Data), and ICE / NYSE's owner unveiled plans for its own compute futures market the same month. The race to price AI infrastructure is clearly on.

Read the source at Bloomberg →

Our take

A forward curve for compute is the kind of plumbing most people will never see — but it matters a lot if you pay an LLM bill. Here's why.

The headline price of "AI compute" has been a fuzzy, marketing-driven number. Vendors quote per-token rates; hyperscalers quote per-GPU-hour; brokers quote per-H100-month. None of them line up, and the gap between the cheapest and most expensive path to the same output can be enormous. Our own tokenizer-efficiency benchmark found a 74% spread in how many tokens different models burn on the same words — meaning two models at the same sticker price can cost wildly different amounts per unit of real work.

A tradeable forward curve won't fix tokenizer inefficiency, but it does something complementary: it makes the underlying — the hardware itself — legible and hedgeable. Three things follow:

Price discovery. Today, if you want to know what an H100-hour will cost in March, you call a broker and get a quote that's only as good as your leverage. A liquid forward curve turns that into a public number everyone can see.
Hedging. Teams that buy serious compute (training runs, inference fleets) can lock in future costs instead of gambling on spot prices. Predictability is worth money.
Benchmark reality. A compute price index lets cost-per-task numbers — like the ones we publish in Benchmarks — be normalized against the actual market price of the iron, not just the provider's rate card.

The open question is whether prediction-market contracts (Kalshi's model) will be liquid and trusted enough to become a real reference price, or whether the exchange-traded futures from CME and ICE will dominate. Kalshi's bet is that its event-contract approach, sliced by GPU grade and geography, captures granularity the bigger exchanges won't bother with at first.

Why it matters

For most readers the takeaway is practical, not financial. Compute is quietly becoming the single biggest variable cost of doing anything with AI — and until now it's been opaque. Three exchanges racing to publish forward prices means that opacity is starting to lift. If you're budgeting an AI project, watching a compute curve (the way you'd watch a currency or commodity) is about to become a reasonable thing to do.

And on our end: a public compute price makes the per-word, per-task cost analysis we do in Benchmarks more grounded — we can quote results against a shared market reference instead of a provider's list price. We'll be watching which curve becomes the standard.

Browse all News

Five Signals a Workflow Is Ripe for AI

Mon, 13 Jul 2026 17:00:00 -0700

News

Five Signals a Workflow Is Broken — and Ripe for AI

Published July 14, 2026

Series: News — Article Review Published: 2026-07-14 Source: Corey Ganim on X Author: Victor Salmon

The post

In a thread on X (July 14, 2026), Corey Ganim offers a bluntly practical method for finding broken workflows in a small business — the kind worth automating. His advice: ask the owner "Can you show me how this happens today?", then watch for five telltale signals:

Tabs. How many tools do they open? Six tabs to finish one task means friction.
Copy/paste. What gets moved by hand from one place to another? That's automation opportunity.
Waiting. Where does work stall waiting on a reply, an approval, a missing file? That's a bottleneck.
Rework. Where do people fix the same mistakes over and over? That's a process problem.
Handoffs. Where does a task pass from one person to another? That's where things get lost.

He lists concrete examples: a bookkeeper's month-end close, logistics quote creation, recruiting candidate screening, agency client onboarding, school enrollment inquiries. The thesis, in his words: "simply watching how the work gets done today will show you exactly where AI belongs."

Read the source thread on X →

Our take

This is the part of automation that almost nobody writes about — and it's the part that determines whether an AI project succeeds. Most failure isn't in building the agent; it's in picking the wrong task to automate.

Ganim's five signals are a field-ready discovery checklist, and they line up almost perfectly with the layers we teach and build. Mapping them to what comes next:

Copy/paste and Tabs are pure data-movement problems. Once you've spotted them, the fix is usually a single integration or a desktop agent moving data between tools — exactly what our Basic Agents and Agents Working for You tracks cover.
Waiting is an orchestration problem — work idling for an approval or a missing input. This is where autonomous agent loops (that poll, remind, and fetch) earn their keep.
Rework is a quality problem — usually a categorization or extraction step that an LLM can do once, correctly, instead of a human fixing it repeatedly.
Handoffs are a coordination problem — and the most valuable to fix, because that's where errors compound and context gets lost between people.

One nuance worth adding: signals 1 and 2 (Tabs, Copy/paste) are the cheapest wins and the best place for a small business to start. Signals 4 and 5 (Rework, Handoffs) are higher-value but harder — they touch how people work, not just what tools they use. Start with the copy/paste, build trust, then tackle the handoffs.

Why it matters

If you're a small-business owner (or you help one), the highest-leverage hour you can spend this week is the one Ganim describes: sit down, pick one recurring task, and just watch how it gets done. The broken parts will announce themselves. Once you know where the friction is, the question of whether AI helps — and which kind — answers itself, and our Tutorials pick up right from there.

And if you'd rather have someone do that discovery with you, that's literally the first thing we do — book a consultation and we'll map your five signals together.

Browse all News