Satoshi-is-here

The fundamental shift is moving assignments from testing what students can produce to testing what students can think. AI can generate a competent essay, but it cannot replicate the cognitive process of wrestling with an idea — and that process is where learning actually happens. The most effective redesign strategy is making the process visible and graded. Instead of assigning a final paper, require students to submit iterative drafts with reflective annotations explaining what changed between versions and why. Ask them to maintain a thinking log: what sources did they consult, what arguments did they consider and reject, where did they change their mind? This approach works because AI can produce a polished output but cannot authentically reconstruct the messy, nonlinear reasoning that produced it. A second powerful approach is local and personal specificity. Assign problems anchored in the student's immediate context — analyze the zoning dispute happening three blocks from campus, interview a family member about their immigration experience and connect it to course themes, audit your own university's sustainability practices against frameworks from class. These assignments resist AI completion because they require original primary data that doesn't exist on the internet. Third, lean into AI as a collaborative tool rather than pretending it doesn't exist. Assign students to generate an AI response, then critically evaluate it: what did the AI get wrong? What nuance did it miss? What sources would you need to verify its claims? This teaches a skill arguably more valuable than essay writing itself — the ability to evaluate machine-generated content critically. Finally, bring back oral examination in modern form. A ten-minute conversation where a student defends their written work, answers follow-up questions, and thinks on their feet reveals understanding in a way no written submission can — and is essentially AI-proof. This doesn't require returning to formal vivas; even brief in-class discussions where students present and field questions accomplish the same goal.

The space debris problem has a counterintuitive property that makes it urgent: removing just five to ten large objects per year from crowded orbital bands could prevent the Kessler cascade that would make low Earth orbit unusable. The priority isn't cleaning everything — it's strategic removal of the highest-risk items before they collide and multiply. The most deployment-ready technology is robotic capture missions targeting defunct satellites and spent rocket bodies in the 800-1000 km altitude band, where collision probability is highest. The European Space Agency's ClearSpace-1 mission, launching soon, demonstrates this approach: rendezvous with a specific piece of debris, capture it with robotic arms, and deorbit both into atmospheric burn-up. The challenge is cost — roughly $100-200 million per object removed using current approaches. Scaling this requires shifting from bespoke missions to standardized, reusable servicing vehicles that can deorbit multiple targets per flight. For smaller debris (1-10 cm), ground-based laser nudging is the most promising near-term option. High-powered lasers ablate a tiny amount of surface material, creating just enough thrust to alter the object's orbit toward atmospheric reentry. This avoids the enormous cost of launching a separate vehicle for each piece of junk. But technology alone won't solve this. The critical bottleneck is governance. No international framework currently assigns responsibility for removing debris or liability for creating it. A realistic reform would extend the "polluter pays" principle to space: require launch operators to post bonds covering end-of-life deorbiting costs, and fund an international debris removal fund through per-launch fees. The Outer Space Treaty needs updating to establish clear property rights over abandoned objects — currently, you cannot legally remove another nation's debris without permission, even if it threatens everyone's satellites. The most overlooked piece is prevention. Mandating that all new satellites carry propulsion for controlled deorbit within five years of mission end would dramatically reduce future accumulation at a fraction of the cost of active removal.

Yes, but what we teach should change dramatically. The analogy to horse-shoeing misses something crucial: coding isn't just a vocational skill, it's a way of thinking. The real question is which aspects of programming education remain valuable and which should be replaced. The enduring value lies in computational thinking — decomposing problems, recognizing patterns, designing algorithms, and reasoning about systems. These cognitive skills transfer far beyond writing code. A student who understands why a loop works, what a database query actually does, or how an API connects two systems can direct AI tools intelligently. Without this foundation, you're relying on a tool you fundamentally don't understand, which is a recipe for brittle, insecure, and subtly broken software. What should change is the emphasis on syntax memorization and boilerplate. Nobody needs to memorize Python's string formatting rules anymore. The new curriculum should teach students to specify problems precisely, evaluate AI-generated code critically, debug outputs they didn't write, and understand system architecture at a conceptual level. Think of it like mathematics education after calculators: we still teach arithmetic reasoning even though nobody hand-computes long division professionally. The middle ground looks like this: early education (ages 8-14) focuses on logic, algorithms, and computational thinking through visual or block-based tools, building mental models of how computers process information. Later education (15+) shifts toward AI-augmented development — students learn to architect solutions, write specifications, review and test AI output, and understand security implications. The goal moves from "can you write this function" to "can you design this system and verify that it works correctly." The countries that drop programming education entirely will produce a generation that can prompt AI tools but cannot evaluate, debug, or improve what they produce — effectively creating a new form of technological dependency more dangerous than the old one.

Start with layout, not aesthetics. The kitchen triangle — the path between sink, stove, and fridge — is the functional core of any kitchen. Before picking cabinet doors or colors, map out your current workflow: where do you prep, where do you cook, where do you land groceries? A layout that fits how you actually cook will feel right ten years from now even if trends shift. Ballingslöv offers several standard configurations; have them help you model your space before committing to anything visual. For evergreen style, the simplest principle is: suppress the things that date quickly, invest in the things that age well. Cabinet hardware, faucets, and light fixtures are cheap to replace in five years. Cabinet door style and layout are expensive to change. This means go conservative on cabinet doors — flat-front Shaker or plain slab profiles have stayed relevant for decades and will continue to. Avoid anything with distinctive period detailing (ornate profiles, glass mosaic backsplashes, ultra-trendy colors). Ballingslöv's classic lines in white, light grey, or natural wood tones consistently hold up over time. For countertops, honed stone or composite materials in neutral tones (warm whites, greys, or dark charcoals) outlast fashionable choices like concrete or bright quartz patterns. Avoid anything that looks like it belongs to a specific era. Handle the regret risk explicitly: before finalizing, live with your material samples for two weeks. Pin them up in the kitchen, look at them in morning and evening light, and notice whether you still feel good about them. Most renovation regret comes from decisions made in a showroom under artificial lighting with a salesperson present. Ballingslöv's planning service lets you iterate digitally — use it extensively. The goal is to have no surprises on installation day.

The core problem is that universities are structured around stability, not adaptability. Tenure systems, shared governance, and accreditation cycles all serve legitimate purposes — protecting academic freedom, ensuring quality — but they create enormous inertia. A curriculum change that a company could implement in weeks requires committee approvals, faculty senate votes, and accreditor sign-off that can stretch across years. Funding models reinforce this. Most universities depend on tuition locked into four-year degree structures and government grants tied to credit-hour requirements. Experimenting with modular credentials or compressed timelines risks both revenue streams and regulatory compliance. The institutions most in need of reform are often the least financially able to risk it. There is also a cultural dimension often overlooked: faculty are hired and promoted for research excellence, not pedagogical innovation. A professor who redesigns their course around project-based learning gets no tenure credit for it. The incentive structure actively punishes experimentation. Realistic reforms should target these structural roots. First, decouple accreditation from rigid credit-hour requirements and allow competency-based progression — some institutions like Western Governors University already prove this works at scale. Second, create dedicated innovation budgets that let departments pilot new formats without risking core operations, similar to how corporations fund R&D separately. Third, reform promotion criteria to weight teaching innovation alongside publication records. Finally, build stackable credential pathways where students can earn meaningful micro-credentials that aggregate toward full degrees, letting the university serve both rapid upskilling needs and deep disciplinary training without choosing between them.