Jökull Sólberg Auðunsson jokull

Trip tour vertical gallery assignment audit

Generated: 2026-06-02T15:52:14.847Z

Method

Supabase live filter: tour.is_published = true, tour.is_unlisted = false, and tour.dato_id IS NOT NULL.
Dato filter: published allTours records from the Content Delivery API.
Failure rule: the tour detail bento gallery renders the first five Dato gallery assets. A tour is flagged when fewer than 2 of those first 5 assets have customData.layout = "vertical".
Dato published failures before SQL filtering: 18. Live listed failures after Supabase filtering: 13.

Agent Sandbox Blueprint Prompt

This prompt is for teams that want to bolt an agent-native sandbox onto an existing monorepo.

The goal is not to create another E2E suite or a prettier docker-compose up. The goal is to give coding agents a disposable, inspectable, worktree-local environment where they can behave more like a careful human doing manual QA: open the app in a browser, click through real flows, inspect logs, read local side effects, check emails, review analytics/error events, adjust seeded scenarios, and produce visual proof without waiting for a human to run the project.

Think of this as giving agents vision and x-ray access to the app. Each agent/worktree should be able to spin up its own realistic runtime, keep working longer, avoid port fights with other agents, and leave behind evidence artifacts that make reviews easier.

The shape you are aiming for is this:

Michael Arnaldi on X:

Hot take: TUIs are a phase, and GUIs that basically emulate TUIs are a phase too. We just don't know how the IDE of the future will look like.

He's talking about the arc of dev tools. Terminal, then Notepad++, then richer IDEs, then VSCode. Each phase building on the last, borrowing metaphors, adding chrome. What comes next?

But something about the question stuck with me.

Unix evolved under constraints. Teletypes. Tiny memory. Slow connections. Those limits forced everything through text — and text turned out to be strangely universal. Decades later, everything still speaks it.

Deployment plan: dato_tour → tour rename (PR #1418)

Deployment Plan: `dato_tour` → `tour` Rename (PR #1418)

Context

PR #1418 renames dato_tour → tour tables, switches 97 files, and establishes the foundation for admin-first tour creation. Existing tour rows keep DatoCMS IDs as Tour.id; new Tour.datoId column (nullable) links to DatoCMS content. New tours get cuid2 IDs.

Migration strategy: Expand-Contract (zero-downtime reads)

Expand (this PR): New tables/columns created alongside old ones, data backfilled, old constraints relaxed

Migrating a Next.js blog to vinext (Cloudflare Workers): Hurdles

This documents the struggles encountered migrating a Next.js 15 blog (with MDX, Shiki syntax highlighting, and OG image generation) to vinext on Cloudflare Workers.

1. `EvalError: Code generation from strings disallowed`

The showstopper. @mdx-js/mdx's run() internally calls new Function() to evaluate compiled MDX. Workers completely blocks eval and new Function at request time.

EvalError: Code generation from strings disallowed for this context

Usability test findings — Trip to Japan (Feb 2026)

Usability Test Findings — Trip to Japan

Source: User testing video (video-382132.mp4) — ~10 min session
Date: 2026-02-27

Timeline

Kjarval ehf. (6704180140) — Research Notes

Private members' club & coworking at Austurstræti 10A/12, 101 Reykjavík. Opened 2019. Part of Sonato reciprocal club network (100+ partner clubs worldwide).

Ownership

Shareholder	Stake	Shares
GO loyalty solutions ehf.	60%	375,000
M9 ehf.	20%	125,000

Dato Tour Model — Field Audit

Why `fromPrice` is going away

The static fromPrice field in DatoCMS has been replaced by live inventory pricing (amount) from our booking providers. The static price was stale and misleading — it didn't reflect actual availability or seasonal pricing. We've removed it from all queries and components.

What changes for tours without inventory pricing? They simply show no price instead of a stale/incorrect one. This is cleaner and more honest.

Þorpið vistfélag — lóðagreining úr fundargerðum Reykjavíkur

Greining á lóðum sem Þorpið vistfélag ehf. og tengd félög hafa fengið úthlutað eða sótt um byggingarleyfi á, samkvæmt fundargerðum skipulagsfulltrúa og byggingarfulltrúa Reykjavíkur í gagnagrunni planitor.io.

Tengd félög

Félag	Kt.	Þekkt lóðir
Þorpið - Vistfélag ehf.	6410180230	Jöfursbás 11, Breiðhöfði 9
Þorpið 2 ehf.	4809200740	Jöfursbás 11 (byggingarleyfishafi)

	[core]
	excludesfile = ~/.gitignore
	[user]
	name = Jökull Sólberg
	email = jokull@solberg.is
	[init]
	defaultBranch = main
	[push]
	autoSetupRemote = true
	default = current