What happens if you put work into the second dimension?
I built a prototype of a 2D canvas you can put all of your work on: real terminals, running apps and browsers side by side instead of a row of tabs. We, at FlutterFlow, got so obsessed with using it that we built a full product out of it, Campus. Next comes the story of how we got here … The age of context switching Just a few years ago, development was organized in a pretty straightforward way.
- ▪I built a prototype of a 2D canvas you can put all of your work on: real terminals, running apps and browsers side by side instead of a row of tabs.
- ▪We, at FlutterFlow, got so obsessed with using it that we built a full product out of it, Campus.
- ▪Next comes the story of how we got here … The age of context switching Just a few years ago, development was organized in a pretty straightforward way.
Hacker News (Front Page) files mainly under programming. We currently carry 1,160 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Norbert Kozsir |
| Canonical URL | https://norbertkozsir.com/posts/work-in-the-second-dimension/ |
| Publication time | Wed, 05 Aug 2026 18:39:31 +0000 |
| Retrieval time | 2026-08-05T20:05:43.654Z |
| Last seen | 2026-08-05T20:05:43.654Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | KjmePHubc9tC · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
I built a prototype of a 2D canvas you can put all of your work on: real terminals, running apps and browsers side by side instead of a row of tabs. We, at FlutterFlow, got so obsessed with using it that we built a full product out of it, Campus. It's free and available for macOS now. Next comes the story of how we got here … The age of context switching Just a few years ago, development was organized in a pretty straightforward way. Plan the work in more or less detail, then work on those features for the next week or two, rinse and repeat. With the advent of agentic coding, that has completely changed. Planning or discussing certain types of work has itself become slower than just letting the agent do the work. This is causing a massive shift in how I and tons of people I know work.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Norbert Kozsir.