The Washington Technology Industry Association kicked off the third annual Seattle AI Week on Monday with a reminder that AI affects everyone, from engineers and artists to “someone who learned about ChatGPT today,” as WTIA’s Nick Ellingson put it.

“All of us should be a part of that conversation,” he added.

A few people in the audience took that statement literally.

Members of Troublemakers, a Seattle climate activism group, interrupted the week’s opening panel on AI and economic growth several times before they were led out by security. Outside on Elliott Bay, others floated in kayaks with a banner: “Power for People, Not for Tech.”

“These are not your constituents — we are,” one protester told Beau Perschbacher, Gov. Bob Ferguson’s senior policy advisor, as he addressed the large crowd of tech and startup leaders at Seattle’s AI House. Perschbacher was on a panel with Joe Nguyen of the Seattle Metropolitan Chamber of Commerce and Mattie Zazueta of OpenAI, the event’s presenting sponsor.

The group’s main message, according to members who spoke with GeekWire: the rush to build data centers and roll out AI is putting the state’s communities, jobs and environment at risk, and Washington should be investing in green jobs and clean energy instead.

The protest comes amid a broader backlash against data centers in Washington state and across the country. The Seattle City Council voted unanimously in June to pause new large data centers in the city for a year, and Washington AI Resistance organized at least 19 protests around the state this month calling for a statewide moratorium.

The event also came the same day Microsoft offered voluntary buyouts to about 60,000 employees, roughly a quarter of its workforce, as it spends tens of billions of dollars on data centers and AI infrastructure.

The backlash contrasts with a push from the business and tech community for Washington state and the Seattle region to do more to stay competitive in the AI era.

“Washington helped build the technology economy of the last generation. We have an extraordinary opportunity to lead the AI economy of the next,” said former Gov. Chris Gregoire, now CEO of the business group Challenge Seattle, in her opening remarks at the AI Week event.

Gregoire cited efforts to put AI to work on the region’s own problems, including an AI permitting pilot in Everett that she said could cut the median wait for an accessory dwelling unit permit from 252 days to 90. She highlighted the AI-driven protein design work of Nobel laureate David Baker of the University of Washington, with applications in areas including the environment, agriculture and health care.

She also warned that Washington is close to the bottom for its business climate, even though it ranks second in North America for tech talent, as other states court its companies and jobs.

On the panel, Perschbacher said Ferguson’s administration has been focused on data centers since taking office, setting up a work group early last year to study their impact. The group looked for a Washington community that had been harmed by a data center and couldn’t find one, he said.

He added that the state won’t permit data centers to run diesel generators around the clock, and that their water use turned out to be “not out of line with a typical industrial user.”

Electricity is a different story. Data centers “use a really significant amount of electricity,” he said, and with demand also rising from EVs and heat pumps, getting enough power “is a major challenge.”

Perschbacher addressed the protesters directly, saying Washington has some of the strictest environmental laws in the country and that the state’s data center work group reinforced those rules rather than weakening them. Bills on ratepayer protections and transparency for data centers are likely to come back in the next legislative session, he said.

The issue also came up in the event’s second panel, on AI policy. State Sen. Marko Liias, who sponsored a bill this year on high-risk uses of AI, said data centers that want to locate in Washington need to meet “stringent expectations,” including adding clean energy to the grid, recycling water and dropping nondisclosure agreements that keep communities in the dark. Washington’s goal “has never been to be the cheapest or easiest place,” he said.

“When energy becomes scarce, I do think we need to be clear that our communities deserve access to that energy before the data centers do,” Liias said.

Joe Braidwood, founder of AI governance startup Glacis, which works out of AI House, said on the same panel that it was the first event he’d attended there with a public protest. “I think that’s actually kind of promising that people care enough to want to come together and talk and disagree and figure this out,” he said.

Zazueta, OpenAI’s global head of community programs, said in the opening panel that the industry needs to do a better job showing people the benefits of AI. Many people “read about these scary headlines,” she said, but don’t see how the technology applies to their daily lives.

OpenAI runs AI literacy workshops and trains libraries and community groups to lead their own, she said. The company opened an expanded office in Bellevue in March, its largest engineering center outside San Francisco.

Speaking with GeekWire outside the event on Monday afternoon, one of the protesters who had interrupted the panel singled out that remark. She said it dismissed public concerns about AI as the product of bad headlines, and she objected to the idea of using community groups to win people over to the benefits of artificial intelligence.

“They want to infiltrate our communities,” she said.

The opening panel with Zazueta, Perschbacher and Nguyen was titled “The Abundance State: Washington’s Chance to Lead the AI Future.” The protester objected to that framing, saying the panelists’ idea of abundance came down to easing permits for data centers.

It wasn’t the first time the group has protested the tech industry’s energy use. In 2024, it blocked entrances at Amazon’s Seattle headquarters to protest the company’s plans to power data centers in Oregon with natural gas.

Inside the event on Monday, as the interruptions continued, Nguyen, a former state senator who now leads the Seattle chamber, had responded to the protesters directly. “If you want to have your own event, have your own event,” he told them.

After they were led out, Nguyen said he agreed with the protesters, calling their passion “very warranted.” Those concerns are one reason Washington created some of the most stringent energy policies in the country, he said, adding that everyone would be better off if data centers elsewhere were held to the same standards.

“I think we’re very unique in Washington state to be able to actually do this in a way that really is mindful of our values, of the environment, and also pushing for innovation as well,” he said.

At the same time, Nguyen said demand for AI and data centers is market-driven, and it isn’t fair to criticize data centers while using them every day.

“For anybody who’s upset with data centers, I hope that when you email me, don’t email me,” he said. “Print it off and walk it to my office.”

Note: GeekWire’s Todd Bishop is interviewing OpenAI’s Vijaye Raji on stage Tuesday morning at WTIA’s Seattle AI Summit, part of Seattle AI Week.

On October 18, right in the middle of shipping a multi-feature audit and a supplement tracker redesign on my personal life_os_app (my daily Flutter Web + Cloud Firestore operating board), GitHub Actions stopped scheduling jobs. The billing meter for my personal account's hosted runner minutes had hit 100%.

Look at what my .github/workflows/ci.yml and deploy-live.yml were doing on every push and pull request:

1. Spinning up an ubuntu-latest VM.
2. Pulling the Flutter SDK and warming the Pub cache (~90s).
3. Installing Python 3 and running 68 CLI sync unit tests (~15s).
4. Running flutter analyze and 466 widget and accessibility tests (~110s).
5. Compiling flutter build web --release --no-web-resources-cdn (~140s).
6. Authenticating via Workload Identity Federation (google-github-actions/auth@v2) and deploying to Firebase Hosting target board (~35s).

That is 6.5 minutes per PR push and another 4 minutes on merge to main. Across 70+ PRs in October, a single-developer personal project burned through thousands of CI minutes doing work my local Apple Silicon MacBook finishes in under 35 seconds.

When your CI budget hits zero on a personal repo, you have two choices: pay for extra runner minutes to compile code your laptop already compiled, or build a deterministic local verification and deployment pipeline that is faster and safer than the YAML workflow it replaces.

Here is the exact architecture I use to keep life_os_app shipping to Firebase Hosting and Cloud Firestore with zero GitHub Actions spend.

Architecture: The Three-Layer Local Verification Gate

Moving deploys to your local machine only works if you never deploy unverified state. In life_os_app, the application state is split across two runtimes:

• Python 3.14 CLI Sync Tools (tool/board_*.py): Morning and evening scripts that pull from Apple Reminders, Google Calendar, Harvest, Notion, and GCP Billing, then write structured JSON documents into Cloud Firestore over REST.
• Flutter Web Client (lib/): A Riverpod 3 + Material 3 multi-skin web app served from Firebase Hosting with a custom offline Service Worker (web/offline-sw.js).

Layer 1: Firestore Schema Validation Before Every REST Write

One of the biggest risks of running CLI sync tools outside a container is accidentally clobbering fields that the Flutter Web client writes directly from the browser. For example, on the Events and Admin tabs, I tick tasks directly in the UI (config/events.taskTicks and config/admin.done), while tool/board_events.py and tool/board_admin.py sync metadata from Notion and GCP Billing.

To prevent a CLI run from wiping browser taps, tool/board_firestore.py enforces two rules before any HTTP PATCH leaves the machine:

1. Explicit schema validation on every collection (dayPlans, stats, config, finance, plan).
2. Field-level update masks (?updateMask.fieldPaths=...) plus hard blocks against overwriting client-owned map keys:

# tool/board_firestore.py
if path == "config/events" and "taskTicks" in data and not fields:
    raise SystemExit(
        "refusing to overwrite config/events.taskTicks without --fields; "
        "pass --fields updated,source,events"
    )
if path == "config/admin" and "done" in data and not fields:
    raise SystemExit(
        "refusing to overwrite config/admin.done without --fields"
    )

In addition, caching the gcloud auth print-access-token call with @functools.lru_cache(maxsize=1) and enforcing a 15-second socket timeout cut multi-document Firestore sync latency by 80% and eliminated hanging background processes when switching Wi-Fi networks.

Layer 2: Per-Document Decode Isolation in Flutter Streams

In Cloud Firestore, a single malformed field inside one historical document in a collection query (collection('dayPlans').snapshots()) will normally throw a FormatException or TypeError inside .map(), killing the entire StreamProvider and replacing your UI with an error state.

During my audit pass, I hardened every repository to isolate decoding per document:

// lib/features/day_board/data/board_repository.dart
List<T> _decodeEach<T>(
  QuerySnapshot<JsonMap> query,
  T Function(JsonMap data, String id) decode,
) {
  final results = <T>[];
  for (final doc in query.docs) {
    try {
      results.add(decode(doc.data(), doc.id));
    } on Object catch (error, stackTrace) {
      developer.log(
        'Skipping malformed document ${doc.reference.path}',
        name: 'day_board.repository',
        error: error,
        stackTrace: stackTrace,
      );
    }
  }
  return results;
}

When saving multi-day edits (such as editing 7 days of focus blocks and habit notes in the This Week sheet), replacing 14 sequential await set() calls with a single atomic WriteBatch (saveWeekEditsBatch) eliminated partial-save race conditions on flaky mobile connections.

Layer 3: Self-Contained Web Bundles (--no-web-resources-cdn) & Service Worker Cleanup

When deploying Flutter Web to Firebase Hosting for daily use on iPhone, iPad, and desktop, CDN font/CanvasKit fetches can stall on airplane or train Wi-Fi. Building with --no-web-resources-cdn bundles CanvasKit and font assets directly into build/web/, paired with a custom web/offline-sw.js that races network against a 3.5-second timeout before falling back to cache:

// web/offline-sw.js
function networkFirst(request, timeoutMs) {
  return new Promise((resolve, reject) => {
    const timer = setTimeout(() => reject(new Error('timeout')), timeoutMs);
    fetch(request)
      .then((response) => {
        if (response && response.ok) {
          caches.open(CACHE).then((cache) => cache.put(request, response.clone()));
        }
        resolve(response);
      })
      .catch(reject)
      .finally(() => clearTimeout(timer));
  }).catch(() => caches.match(request));
}

Notice the .finally(() => clearTimeout(timer)) cleanup: without it, every fast network response leaves an orphan timer running until timeoutMs expires.

Benchmarking: Cloud CI vs. Local Verification Gate

Table totals exclude the Flutter SDK download and Pub cache warm-up (~90s), which is what brings a full PR run to ~6.5 minutes.

Key Takeaways for Flutter & Firebase Engineers

1. Keep CI YAML for PRs when budget allows, but make your local gate identical. A single local command (dart format -l 120 lib/ test/ && flutter analyze && python3 -m unittest discover -s tool -p '*_test.py' && flutter test) guarantees parity before firebase deploy.
2. Use Firebase Hosting multi-site targets (hosting:board, hosting:board-staging). Mapping targets in .firebaserc lets you preview on staging or promote to live with --only hosting:board without touching sibling sites on the same GCP project.
3. Never let one bad Firestore document take down a collection stream. Wrap per-document .fromJson() calls inside a helper that logs to dart:developer and skips the corrupted record.
4. Test accessibility contrast and 44pt tap targets in flutter test, not in production. Running textContrastGuideline and androidTapTargetGuideline with GoogleFonts.config.allowRuntimeFetching = false catches neon text shadow contrast drops and 32pt icons in milliseconds.

The complete local release gate in one command:

dart format -l 120 lib/ test/ && \
  flutter analyze && \
  python3 -m unittest discover -s tool -p '*_test.py' && \
  flutter test && \
  flutter build web --release --no-web-resources-cdn && \
  firebase deploy --only hosting:board --project esra-life-os

Since the mid-1990s, every desktop and laptop PC has followed the exact same blueprint: an x86 CPU connected to system RAM on one side, and a discrete GPU wired to separate VRAM across a narrow PCIe bus on the other. While that split architecture powered three decades of spreadsheets, web browsers, and rasterized games, it hits a brick wall when you try to run a 120-billion-parameter AI agent locally on your desk.

With the rollout of the NVIDIA DGX Spark and GB10 Grace Blackwell Superchip alongside the Windows-powered RTX Spark (N1X) platform, NVIDIA CEO Jensen Huang has declared the end of thirty years of traditional PC architecture. In this hardware guide, we examine why the split CPU-GPU memory wall is dead, how NVLink-C2C unifies 128 GB of memory on a single 3nm chip, and how local autonomous agents reshape your next PC.

Table of Contents

• Why Thirty Years of Split CPU and GPU Memory Hit a Wall
• Inside the GB10 Grace Blackwell Superchip and RTX Spark N1X Silicon
• Rewriting the Windows Kernel and Securing Local Agents with OpenShell
• Scaling to Two Hundred Billion Parameters on Your Desk with DGX Spark
• Comparing Traditional x86 PCs, NVIDIA RTX Spark, and DGX Spark
• How Developers Should Prepare for the Post-Traditional PC Era
• Frequently Asked Questions (FAQ)
• End Note

End Note

Just as smartphones transformed mobile phones from voice-call handsets into pocket computers, NVIDIA's GB10 and RTX Spark architecture transforms the personal computer from a manual application launcher into an autonomous agent workstation. By fusing a 20-core Arm Grace CPU, a 6,144-core Blackwell GPU, and 128 GB of coherent unified memory over NVLink-C2C, the thirty-year-old PCIe memory bottleneck is officially history.

 

If your daily workflow involves local LLM fine-tuning, multi-agent orchestration, or massive 3D rendering scenes that choke a 16 GB or 24 GB discrete graphics card, unified-memory Grace Blackwell desktops and laptops represent the biggest architectural leap since 1995.

 

In the previous episode, we covered organizational culture, including why posters aren’t the way to change culture, crucial theoretical foundations from Douglas McGregor and Ron Westrum, the impact of arbitrary deadlines, and why feedback keeps organizations healthy.

This episode examines Platform Engineering and the persistent debate between mandatory and optional adoption strategies. The episode was inspired by data from our Future of Platform Engineering report.

Watch the episode

You can watch the episode below, or read on to find some of the key discussion points.

Watch Continuous Delivery Office Hours Ep.12

The rise of mandatory platforms

Mandatory platforms have been an issue in the past, with platform producers and consumers diverging dramatically on whether a platform is successful. Part of the perception gap comes down to platform teams losing the adoption signal: if everyone must use the platform, you’ve lost a way to discover gaps and flaws in what you provide.

Since then, platforms have become broader. Platforms now have almost 6x as many features as they did when the perception gap was present. As platforms take on tasks that developers truly appreciate, like security and compliance, the gap between producers and consumers has closed.

You might think of this like the difference between being forced to use a bicycle to travel both before and after the invention of the bicycle saddle. Riders are far happier to be forced to cycle when they have a cushioned seat.

Alongside the dissipation of perceptual differences, it turns out mandatory platforms outperform optional platforms in terms of goal attainment. However, there are many factors contributing to platform success, like monitoring developer satisfaction and regularly eliciting feedback to help improve the platform.

The other factors of platform success have more impact, and you should still consider optional adoption, but combined with mandatory policies. That means development teams have to meet the same standards they would meet if they adopted the platform, which makes platform adoption more appealing and less likely to cause conflict or friction.

Not just more features, but the right ones

The most common number of features baked into a platform was four, but that has grown to 24. Platforms are getting broader, and these wider platforms are more successful than the tiny ones of the past. Despite this link between platform breadth and goal attainment, it’s important to bear in mind that the volume of features alone is not a sufficient strategy, and that choosing to solve the right problems is the path to success.

Maintaining regular contact with developers, lightly assessing their satisfaction with the platform, and dedicating time to conversations that shape your platform’s direction are all part of the high-performance platform playbook. The usefulness comes from solving the right problems, and you need to focus on developer needs to make the right choices.

Platform teams are rediscovering many of the capabilities of the State of DevOps research and its associated model, like Lean Product Management, which prove useful in building platforms as internal products.

The invisible platform dilemma

Unsurprisingly, platforms that meet more goals have higher budget safety. They are showing a return on investment, so they can be confident in maintaining their funding over the long run. Platforms that fail to meet their goals are more likely to have their budgets redirected to other initiatives.

Platform teams need to show the value back to the organization in terms the organization understands and for measures it cares about. With AI initiatives soaking up money, some organizations will start reallocating funds and focus, leaving platforms underfunded or dropped.

Some of the best platforms will be invisible in daily use because developers don’t have to keep interacting with them. These boring, invisible platforms are the most valuable, but the least visible. Providing metrics and proof of value for these platforms will keep them funded.

Happy deployments!