DEV Community: The DEV Team

What was your win this week??

Jess Lee — Fri, 19 Jun 2026 06:00:00 +0000

👋👋👋👋
Looking back on your week -- what was something you're proud of?
All wins count -- big or small 🎉

Examples of 'wins' include:

Getting a promotion!
Starting a new project
Fixing a tricky bug
Actually remembered to eat lunch (a hero's journey)🧃

Happy Friday!

Congrats to the Hermes Agent Challenge Winners!

Jess Lee — Thu, 18 Jun 2026 22:13:44 +0000

We are thrilled to announce the winners of the Hermes Agent Challenge! Over the past few weeks, the DEV community dove headfirst into one of the most exciting open-source agentic systems on the scene, and the submissions absolutely delivered.

The range of what people built and wrote left us genuinely impressed — Hermes' memory architecture got a thorough cognitive-science breakdown, the cost curve of a self-improving agent got stress-tested in production, someone built a full immune system for stress-testing AI agent safety, and a Linux desktop HAL was shipped entirely by AI agents. These are just a few of the standout submissions that made judging genuinely hard.

Now, without further ado, let's celebrate our winners! 🎉

Build With Hermes Agent Winners 🏆

From an offline-first emergency response platform to a 25-agent legislative simulation, the Build submissions pushed Hermes into genuinely ambitious territory. What stood out across the board was how purposefully each project used Hermes' agentic capabilities — not as a wrapper around a chat model, but as the actual load-bearing infrastructure. Parallel task delegation, persistent memory, scheduled autonomy, and model-agnostic routing all showed up in real, working builds.

Hermes Agent Challenge Submission: Build With Hermes Agent

ujja

May 28

Building an Offline-First Bushfire Response Platform With Hermes Agent

#hermesagentchallenge #devchallenge #agents

14 min read

Hermes Agent Challenge Submission: Build With Hermes Agent

Monika Sadlok

May 30

I Built a 25-Agent Polish Parliament That Drafts Bills With Real Legal Citations

#hermesagentchallenge #devchallenge #agents

6 min read

Hermes Agent Challenge Submission: Build With Hermes Agent

Elliott

May 29

Skills are Prompts. Here's how Hermes Apprentice turns them into weights

#hermesagentchallenge #devchallenge #agents #ai

9 min read

Hermes Agent Challenge Submission: Build With Hermes Agent

Arqam Waheed

May 30

I Made My AI Models Argue, Then Let Hermes Be the Judge

#hermesagentchallenge #devchallenge #agents #ai

10 min read

Write About Hermes Agent Winners 🏆

The Write submissions gave us useful breakdowns and genuine perspective. The strongest pieces ranged from practical setup guides to sharp critical arguments — about the self-trust issue baked into Hermes' skill architecture, what persistent memory actually changes about the developer experience, and when local agents earn their complexity. Whether you're just getting started with Hermes or already running it in production, there's something here for you to sink your teeth into.

Hermes Agent Challenge Submission

MxGuru

May 19

Two Local-Agent Philosophies: Where Hermes Earns Its Design, and Where the Tradeoffs Invert

#hermesagentchallenge #devchallenge #agents

7 min read

Hermes Agent Challenge Submission: Write About Hermes Agent

Paimon

May 31

Nous Research Hermes Agent: Setup and Tutorial Guide

#hermesagentchallenge #devchallenge #agents

10 min read

Hermes Agent Challenge Submission

Simphiwe Twala

May 16

Building an Ambient Developer Daemon with Nous Hermes

#hermesagentchallenge #devchallenge #agents

12 min read

Hermes Agent Challenge Submission

Vishal Keerthan

May 18

The Self-Trust Problem in Hermes Agent's Skill Architecture

#hermesagentchallenge #devchallenge #agents #opensource

10 min read

Prizes

All eight winners will each receive:

$125 USD
DEV++ Membership
Exclusive DEV Badge

All participants with a valid submission will receive a completion badge.

What's Next?

Check out the June Solstice Game Jam happening now:

Themes of Pride, Juneteenth, and Alan Turing

Jess Lee for The DEV Team

Jun 3

Join the June Solstice Game Jam: $1,000 in prizes!

#devchallenge #gamechallenge #gamedev

239

4 min read

Thank you once more to everyone who participated.

Happy coding! 💙

Congrats to the Gemma 4 Challenge Winners!

Jess Lee — Thu, 18 Jun 2026 18:56:22 +0000

We are so excited to announce the winners of the Gemma 4 Challenge!

This is officially our most participated-in challenge to date, and the range of submissions made that obvious from the start. We saw a ten-year-old GPU-less laptop pushed to its limits, a $50-a-month OCR bill replaced by a local vision pipeline, disaster scenes compressed into 200-byte emergency payloads, and a phone that notices when an elder living alone needs help. The sheer array of topics and builds made these a joy to read through.

Now, let's cut to the chase and celebrate our winners!

🎉 Congratulations To…

Build With Gemma 4 Winners

This prompt asked builders to put Gemma 4 to work, and the range of what came back was the whole story.

We saw the model packed onto a disaster-relief app for the Philippines that keeps functioning when the cell towers go down, turned into a lanyard-worn pair of eyes for blind and low-vision users, and routed through a strict tool-dispatcher so a 2B model could safely tap and type on someone's behalf. One submission ran entirely peer-to-peer so no prompt ever touched a server, and another distilled a HIPAA-bound DBA's 3 AM database panic into a six-section runbook that never left their laptop.

Across all of it, these projects show Gemma 4 expanding the map what can be built and who gets to use it.

Gemma 4 Challenge: Build With Gemma 4 Submission

John Paul Curada

May 24

LIKAS: An offline disaster companion for the Philippines, powered by on-device Gemma 4 E2B

#devchallenge #gemmachallenge #gemma #ai

5 min read

Gemma 4 Challenge: Build With Gemma 4 Submission

Hassan Imam

May 24

AccessLens — A persistent on-device visual interpreter for the blind

#devchallenge #gemmachallenge #gemma

4 min read

Gemma 4 Challenge: Build With Gemma 4 Submission

AVINASH S KARANTH

May 22

p2p-ai — Distributed Peer-to-Peer AI Inference Network

#devchallenge #gemmachallenge #gemma

4 min read

Gemma 4 Challenge: Build With Gemma 4 Submission

Adebisi Mosimiloluwa

May 19

Genie: Building a Privacy-First Autonomous Agent That Controls Your Phone, Entirely Offline

#devchallenge #gemmachallenge #gemma

10 min read

Gemma 4 Challenge: Build With Gemma 4 Submission

Sireesha Chavvakula

May 25

I built a local Postgres triage co-pilot because HIPAA says I can't paste plans into ChatGPT or Claude

#devchallenge #gemmachallenge #postgres #ai

6 min read

Write About Gemma 4 Winners

The writing prompt covered just as much ground, from practical decision-making to deep architectural breakdowns to honest on-the-ground reporting.

One winner laid out exactly how to pick between Gemma 4's four variants before writing a single line of code, while another went under the hood of the model's vision system to explain how it compresses image patches into soft tokens. A third explored what an agentic Gemma 4 misinformation moderator for the Fediverse would actually have to contend with, a fourth shared the hard-won configuration tricks for getting real speed out of Gemma 4 E2B on Android, and the last took the open-model "catch-up" story to Freetown and tested it against the phones people actually carry.

Taken together, these posts are some of the most useful reference material the community has produced on Gemma 4 yet.

Gemma 4 Challenge: Write about Gemma 4 Submission

Soumyadeep Dey

May 23

Gemma 4 Has Four Variants. Here's How to Pick the Right One Before You Write a Single Line of Code.

#devchallenge #gemmachallenge #gemma

8 min read

Gemma 4 Challenge: Write about Gemma 4 Submission

Youdiowei Eteimorde

May 24

Gemma 4 Soft Tokens: The Rise and Fall of 16x16 Words ⚡👀

#devchallenge #gemmachallenge #gemma

20 min read

Gemma 4 Challenge: Write about Gemma 4 Submission

Connor Green

May 24

Anatomy of the Slopster

#devchallenge #gemmachallenge #gemma #java

18 min read

Gemma 4 Challenge: Write about Gemma 4 Submission

IBIYEMI Samuel O.

May 23

Gemma 4 on Android: Tricks for Faster On-Device Inference

#devchallenge #gemmachallenge #gemma #android

8 min read

Gemma 4 Challenge: Write about Gemma 4 Submission

ATMR

May 24

Open Models and the Sub-Saharan Region

#devchallenge #gemmachallenge #gemma #emergingmarkets

20 min read

Prizes

The five “Build with Gemma 4” winners will receive:

$500 USD cash prize
DEV++ Membership
Exclusive DEV Badge

The five “Write About Gemma 4” winners will receive:

$100 USD cash prize
DEV++ Membership
Exclusive DEV Badge

All participants with a valid submission will receive a completion badge on their DEV profile.

What's Next?

Check out the June Solstice Game Jam happening now:

Themes of Pride, Juneteenth, and Alan Turing

Jess Lee for The DEV Team

Jun 3

Join the June Solstice Game Jam: $1,000 in prizes!

#devchallenge #gamechallenge #gamedev

239

4 min read

Thank you again to everyone who participated.

See you next time 💜

Welcome Thread - v380

Sloan the DEV Moderator — Wed, 17 Jun 2026 04:00:00 +0000

Leave a comment below to introduce yourself! You can talk about what brought you here, what you're learning, or just a fun fact about
yourself.
Reply to someone's comment, either with a question or just a hello. 👋

Come back next week to greet our new members so you can one day earn our Warm Welcome Badge!

How We Saved Big and Simplified Our Image Pipeline: Adopting bunny.net on DEV

Ben Halpern — Tue, 16 Jun 2026 16:41:51 +0000

Hey everyone, Ben here.

If you’ve been following the journey of DEV and our open source project Forem, you know we’ve always been obsessed with web performance. Way back in the day, I spoke at Codeland about how to make your website so fast it goes viral in Japan, diving into the mechanics of edge caching and how we kept our page loads nearly instant.

Our core philosophy has always been simple: keep the architecture as lean as possible, cache aggressively at the edge, and let the Rails monolith (Forem) focus on what it does best. For years, Fastly has handled our HTML edge caching brilliantly—most of your page requests never even have to touch our Puma servers, which keeps our RAM usage low and our response times in the milliseconds. Fastly continues to be how all the document content on DEV is served.

But while edge-caching static HTML is a well-understood problem, user-uploaded media is a completely different beast.

As DEV grew, we found ourselves drowning in images. Every post cover, user avatar, comment screenshot, and challenge banner is a high-res asset uploaded by our community. Serving billions of these images globally, while keeping page sizes lightweight, eventually led us into a silent scaling trap: a tangled, multi-CDN media pipeline, massive cloud egress fees, and eye-watering monthly bills.

Here is the story of how we ended the multi-CDN chaos, simplified our media architecture, saved a small fortune, and used edge scripting to build a smarter, faster image-serving pipeline with bunny.net.

The Chaos of Multi-CDN and the Billing Reality Check

To understand why we made the switch, you have to look at what our image pipeline used to look like.

For a long time, our media stack was a bit of a patchwork. We had different CDNs handling different parts of the platform, an image proxying service for dynamic resizing, and raw assets sitting in cloud storage (like AWS S3).

When a user uploads a 10MB JPEG as an article cover, our Rails app doesn't pre-process it into dozens of different dimensions. Instead, we rely on on-the-fly image transformation. In theory, this is great: the browser requests image.jpg?width=800, and a dynamic image optimizer resizes it, converts it to WebP or AVIF, and serves it.

In practice, the economics and mechanics of this setup at scale are brutal, especially when you factor in the realities of modern web traffic:

The Scraper & Traffic Tax: On the open web, you aren't just serving human users. You are constantly being hit by RSS readers, search crawlers, and high-frequency scrapers. Traditional setups simply weren't smart enough to handle this gracefully. A wave of aggressive scrapers requesting un-cached variations or bypassing standard query parameters would force our pipeline to repeatedly re-fetch and re-process assets, sending computing costs into the stratosphere.
Egress Fees: Every single time an image optimizer had to fetch a raw image from our cloud storage origin because of a cache miss (often induced by the traffic patterns mentioned above), we paid steep cloud egress fees.
Transformation Pricing: Many premium image CDNs charge "per thousand images processed" or utilize complex, punitive usage tiers. When you have millions of active posts and users scrolling feeds with hundreds of custom-sized avatars, those transformation counts skyrocket.
Multi-CDN Friction: Running separate providers for HTML caching and image delivery/optimization created massive operational overhead. We had complex header configurations, CORS issues, and routing rules scattered across different YAML files and dashboards.

Our media bills were ballooning, it was incredibly expensive, and we were spending way too much time debugging why our pipeline wasn't smart enough to handle volatile traffic spikes smoothly. We needed a solution that was fast, reliable, highly configurable, and above all, economically sustainable.

Why We Hopped Over to bunny.net

I’ve actually been using bunny.net for years across many of my personal projects. Whether spinning up a quick side application or testing out a new concept, I always found myself returning to it because it is an incredibly well-designed platform with sensible, intuitive products. It lacks the dense, enterprise bloat of traditional cloud vendors; instead, it provides clean developer ergonomics that just work. Because of that first-hand experience, I knew it was a platform we could trust to scale seamlessly with DEV.

What really sold us for Forem wasn't just the raw bandwidth savings (though slashing our bandwidth bills to a fraction of what premium enterprise CDNs charge was a massive win). It was how beautifully their product ecosystem handled our specific architectural pain points through the combination of Bunny Optimizer and Edge Scripting.

1. Bunny Optimizer and Perma-Cache

Bunny Optimizer acts as a fully managed, dynamic image transformation API. We could easily plug it in, append simple URL query parameters (like ?width=600&height=300&crop=1:1), and let Optimizer handle the resizing, cropping, and automatic compression on-the-fly. It automatically negotiates next-gen formats like WebP or AVIF based on the browser's Accept headers, reducing file sizes by up to 80% without any visible quality loss.

But the real magic ingredient—and our ultimate weapon against scraper traffic—is Perma-Cache.

Normally, when a CDN edge server evicts an infrequently accessed image variant, the next request has to go all the way back to the origin (our cloud storage) to fetch and re-optimize it, triggering more egress fees. Perma-Cache solves this by permanently replicating the optimized image variants to Bunny Storage.

Once an image is processed once, it is stored at the edge forever. It never has to hit our AWS origin again, shielding our backend from erratic traffic and virtually eliminated our cloud storage egress fees overnight.

2. Edge Scripting: TypeScript-Native Control

While Bunny Optimizer gave us the raw power to resize images, we needed fine-grained control over how we served them. We didn't want to pollute our Rails views with complicated URL-building logic, and we wanted to prevent users (or bots) from downloading massive raw images.

This is where Edge Scripting came in.

Built on Deno and V8, Edge Scripting runs JavaScript and TypeScript directly at the edge, allowing us to write lightweight, type-safe middleware that executes in milliseconds. It completely replaced the need for custom image proxies or complex Rails controller routing.

Under the Hood: Forem’s Pluggable Images::Optimizer Service

If you look into Forem's codebase, you’ll see that we’ve always designed our image pipeline to be pluggable. We didn't want to hardcode our views to use a specific CDN's query parameters. If a template wants to render a post cover image, it calls a unified helper that delegates to our Images::Optimizer service:

# app/views/layouts/application.html.erb
<%= Images::Optimizer.call(Settings::General.favicon_url, width: 32) %>

Inside app/services/images/optimizer.rb, we use a simple strategy pattern. The Optimizer class acts as a router that maps standardized parameters (like width, height, fit, gravity) to the specific URL format required by the active CDN provider.

Historically, Forem has supported providers like Fastly, Cloudflare, and Cloudinary and adding bunny.net was incredibly straightforward. Here is a look at how our Rails service handles this multi-CDN routing:

# app/services/images/optimizer.rb
module Images
  class Optimizer
    def self.call(url, options = {})
      return url if url.blank?

      # Select the provider strategy based on our environment configuration
      case provider
      when :bunny
        BunnyProvider.call(url, options)
      when :cloudflare
        CloudflareProvider.call(url, options)
      when :fastly
        FastlyProvider.call(url, options)
      else
        url
      end
    end

    def self.provider
      ENV.fetch("IMAGE_OPTIMIZATION_PROVIDER", "bunny").to_sym
    end
  end
end

Each provider implements its own URL rewriting strategy. For example, our bunny.net provider simply builds standard query strings that Bunny Optimizer parses:

# app/services/images/bunny_provider.rb
module Images
  class BunnyProvider
    def self.call(url, options = {})
      uri = URI.parse(url)
      query_params = []
      query_params << "width=#{options[:width]}" if options[:width]
      query_params << "height=#{options[:height]}" if options[:height]
      query_params << "crop=#{options[:crop]}" if options[:crop]
      query_params << "auto=format"

      uri.query = [uri.query, query_params.join("&")].compact.join("&")
      uri.to_s
    end
  end
end

This decoupled architecture is fantastic for an open-source project like Forem. Different self-hosted communities can configure their own CDN of choice by simply changing the IMAGE_OPTIMIZATION_PROVIDER environment variable.

However, while the Rails app generates these optimized URLs, we ran into an interesting operational challenge: what happens when a template forgets to pass a width parameter, or a legacy post contains raw external URLs?

If we relied only on Rails-side URL building, any fallback or unparsed URL would still trigger a heavy, unoptimized image load. This is where our Edge Scripting strategy stepped in—to act as a global safety net right at the network boundary.

Deep Highlight: Smart Downsizing at the Edge

With Edge Scripting, we can intercept image requests right at the CDN layer and apply custom business logic before the request even reaches the optimizer or storage.

For example, we wanted to ensure that user profile avatars and feed thumbnails are never served larger than they actually need to be, regardless of what the original upload was or what query parameters were requested. If a client requests a raw, un-optimized avatar URL, our edge script automatically intercepts it, checks the context, and rewrites the request to enforce a strict maximum width and apply WebP compression.

Here's a simplified example

// A lightweight middleware script running on bunny.net's Edge
export default async function handleRequest(request: Request) {
  const url = new URL(request.url);

  // Intercept requests to our user-uploaded uploads path
  if (url.pathname.startsWith('/uploads/')) {
    const isAvatar = url.pathname.includes('/avatars/');
    const isThumbnail = url.pathname.includes('/thumbnails/');

    // Check if the request already has optimization parameters
    const hasWidth = url.searchParams.has('width');

    if (isAvatar && !hasWidth) {
      // Dedicatedly downsize all avatar requests to a max of 150px
      url.searchParams.set('width', '150');
      url.searchParams.set('height', '150');
      url.searchParams.set('crop', '1:1');
    } else if (isThumbnail && !hasWidth) {
      // Enforce a strict mobile-friendly limit on thumbnails
      url.searchParams.set('width', '400');
    }

    // Ensure automatic next-gen format negotiation (WebP/AVIF) is active
    url.searchParams.set('auto', 'format');

    // Fetch the optimized asset from bunny.net's CDN pipeline
    return fetch(url.toString(), request);
  }

  return fetch(request);
}

This is incredibly powerful because it offloads the "computational thinking" of image delivery entirely to the edge. Our Rails application doesn't have to keep track of responsive image breakpoints or generate heavy, complex markup. We just request the logical asset URL, and our edge script dynamically handles the rest based on client headers and context.

Even better, we’ve integrated this into our standard development workflows. We use GitHub Actions combined with fine-grained personal access tokens to manage and deploy these edge scripts automatically. When we want to adjust our optimization rules or add support for a new layout—like optimizing billboard images or adjusting resolutions on challenge pages—we just push a commit, our CI runs, and the new edge logic is live globally in seconds.

Graceful Failures: Smart Fallbacks Over Plain Broken Images

Beyond routing and sizing, running code at the edge unlocked a massive UX victory: the ability to handle missing or broken assets gracefully.

In a massive community ecosystem, edge cases happen. A user might delete an external image they linked to, an old upload path might break during a migration, or a malformed request could slide through. Traditionally, when an image fails to load or returns a 404/500, the browser drops a jarring, ugly "broken image" icon that disrupts the layout and makes the entire site look broken.

With Edge Scripting, we can catch these failures mid-flight. If our origin or storage returns an error status code, the edge script intercepts the response and seamlessly rewrites it to serve a beautifully styled, custom placeholder image that says "Image not available" or matches our UI theme.

Instead of writing complex, heavy JavaScript event listeners (onError) into every single <img> tag across the Rails application, we handle it natively at the network layer. The application layer never has to think about fallback logic, and our users get a consistent, unbroken visual experience no matter what happens behind the scenes.

Future considerations

Stabilizing and optimizing our image pipeline was just phase one. As we look ahead to how DEV and Forem will continue to evolve, video is the next logical horizon.

Video delivery is notoriously complex—requiring adaptive bitrate streaming (HLS/DASH), multi-resolution transcoding, specialized storage, and optimized video players. In legacy architectures, this usually means spinning up another fragmented set of expensive third-party video processors and complex integrations.

Given our success with their media infrastructure, bunny.net is our definitive first choice for how we are thinking about video moving forward. Their unified platform approach extends directly into video streaming with products that match the same sensible, developer-first philosophy as their image optimizer. Because we can trust their infrastructure to scale predictably without predatory data transfer costs, expanding our edge architecture to handle next-generation rich media feels like a natural progression rather than a daunting infrastructure overhaul.

Final Thoughts

As developers, we often focus on optimizing our database queries, refactoring Ruby code, or fine-tuning our server configurations. But sometimes, the biggest wins are sitting right there in your network tab.

Egress fees and bloated media delivery are a silent tax on growing platforms. By moving to an edge-native, developer-friendly platform like bunny.net, we were able to simplify our architecture, speed up our page loads, and save a lot of money in the process.

If you’re running a media-heavy platform or building open-source community software like Forem, do yourself a favor: look closely at your CDN bills, check your cloud storage egress, and see if you can offload some of that weight to a platform built to grow with you. Your budget (and your users) will thank you.

Happy coding ❤️

What was your win this week?

Jess Lee — Fri, 12 Jun 2026 06:00:00 +0000

👋👋👋👋
Looking back on your week -- what was something you're proud of?
All wins count -- big or small 🎉

Examples of 'wins' include:

Getting a promotion!
Starting a new project
Fixing a tricky bug
Survived a meeting that could've been an email 📵

Happy Friday!

Congrats to the Google I/O 2026 Writing Challenge Winners!

Jess Lee — Thu, 11 Jun 2026 15:38:46 +0000

We are so excited to announce the winners of the Google I/O 2026 Writing Challenge!

We asked you to explore the announcements from Google I/O 2026 and share your thoughts and firsthand takes. Wow, you delivered. The quality and depth of submissions genuinely impressed our team. From hands-on walkthroughs to bold opinions on what the announcements really mean for developers, the entries were thoughtful, original, and packed with insight.

Thank you to everyone who participated. Your writing helps make this community one of the best places on the internet to learn what's actually happening in tech.

Now, let's celebrate our five winners! 🎉

🏆 Congratulations To…

Google I/O Writing Challenge Submission

Vrushali

May 24

The Sleeper Announcement from Google I/O 2026 That Will Change How We Think About Apps

#devchallenge #googleiochallenge #android #kotlin

7 min read

@vrushali_dev_15 wrote a standout deep-dive into AppFunctions — Android's new API for exposing app capabilities directly to AI agents. With 10 years of Android experience behind the lens, this post goes far beyond the surface announcement to map out the full architectural shift this signals and what developers should be thinking about right now, even before shipping a single AppFunction.

Google I/O Writing Challenge Submission

Vicente Junior

May 22

I gave Gemini 3.5 Flash a CVE-fix PR to review. It found another bug in the same file.

#googleiochallenge #devchallenge #ai #gemini

7 min read

@vicente_junior_dev did something rare: actually tested the thing. Running Gemini 3.5 Flash across 3 real production PRs, including a CVE fix, the post documents what the model caught. Grounded, honest, and exactly the kind of first-person experimentation we love to see.

Google I/O Writing Challenge Submission

Laurina Ayarah

May 24

Google Is Killing Gemini CLI on June 18. Here Is What to Do Before Then

#devchallenge #googleiochallenge

5 min read

@toboreeee gave developers a practical heads-up on something that could easily slip by: Gemini CLI deprecating on June 18. Rather than just reporting the news, the post walks readers through exactly what to do before the cutoff. Genuinely useful and well-timed.

Google I/O Writing Challenge Submission

S M Tahosin

May 21

The Most Underrated Announcement from Google I/O 2026 Was Buried in a 90-Second Demo

#discuss #googleiochallenge #devchallenge #python

6 min read

@tahosin spotted what most I/O coverage missed entirely: the Managed Agents API, buried in a 90-second demo. After two days of hands-on testing, the post delivers a clear-eyed breakdown of why this low-key announcement might matter more than all the Gemini headlines combined.

Google I/O Writing Challenge Submission

Rini Susan V S

May 24

Why Local AI Was the Real Winner of Google I/O 2026 (An Insider’s Take)

#devchallenge #googleiochallenge #googleio #edgeai

4 min read

@rinisvs made the case that through all the Gemini and cloud buzz, the real story of Google I/O 2026 was local AI. With an insider's perspective, this piece cuts through the hype and lays out why on-device intelligence may be the most consequential long-term thread running through the entire event.

Prizes

Each winner will receive:

$200 USD
DEV++ Membership
Exclusive DEV badge

All participants with a valid submission will receive a completion badge — keep an eye on your DEV profile!

What's Next?

Check out our current game challenge:

Themes of Pride, Juneteenth, and Alan Turing

Jess Lee for The DEV Team

Jun 3

Join the June Solstice Game Jam: $1,000 in prizes!

#devchallenge #gamechallenge #gamedev

231

4 min read

Happy Coding! 💚

Welcome Thread - v379

Sloan the DEV Moderator — Wed, 10 Jun 2026 14:48:30 +0000

Leave a comment below to introduce yourself! You can talk about what brought you here, what you're learning, or just a fun fact about
yourself.
Reply to someone's comment, either with a question or just a hello. 👋

Come back next week to greet our new members so you can one day earn our Warm Welcome Badge!

Github "Finish-Up-A-Thon" Challenge Winner Announcement Delayed & General Challenge Timeline Updates

Jess Lee — Mon, 08 Jun 2026 22:21:49 +0000

Hey all, we have a quick update for everyone who participated in the GitHub "Finish-Up-A-Thon" Challenge, followed by a more general challenge timeline change.

First off — wow. Our recent challenges have really taken off, and the "Finish-Up-A-Thon" was no exception. The quality and volume of submissions have been incredible (we received over 500 submissions!), and we want to make sure our judges have the time to give every entry the thoughtful review it deserves.

As a result, we're pushing the winner announcement back to June 25. Thank you so much for your patience, and for putting so much heart into your builds. We can't wait to share the results!

Second, we know we've been updating the timelines for quite a few challenges. Here's our latest winner announcement timeline for those of you who have participated in the last few:

Google I/O 2026 Writing Challenge: June 11
Gemma 4 Challenge: June 18
Hermes Agent Challenge: June 18
GitHub "Finish-Up-A-Thon" Challenge: June 25
June Solstice Game Jam: July 9

Finally, we will be increasing the standard judging period for our challenges moving forward. Previously, we strived to select final challenge winners the week after submissions are due, but given our current pace of participation, we are now giving ourselves at least two full weeks so we don't run into these bottlenecks the future.

Thanks again for your participation. This is one of the best problems we could ever dream of having!

In the meantime, consider joining our game challenge — it's been a while since we've gotten to host one of these 😄

Themes of Pride, Juneteenth, and Alan Turing

Jess Lee for The DEV Team

Jun 3

Join the June Solstice Game Jam: $1,000 in prizes!

#devchallenge #gamechallenge #gamedev

182

4 min read

Happy coding! 💙

Winner Announcement Delayed for the Google I/O 2026 Writing Challenge

Jess Lee — Thu, 04 Jun 2026 16:45:54 +0000

Hey all, we have a quick update for everyone who participated in the Google I/O Writing Challenge.

We were thrilled by the number of posts that came in. Your takes on Google I/O 2026 were thoughtful, creative, and hard to rank. As a result, we need a bit more time to review all submissions before making our final decisions.

We'll be back with the winner announcement by June 11. Thank you so much for your patience, and for the effort you put into your writing.

In the meantime, consider entering one of our ongoing challenges:

Revive old projects using GitHub Copilot

Jess Lee for The DEV Team

May 21

Join the GitHub Finish-Up-A-Thon Challenge: $3,000 Prize Pool!

#githubchallenge #devchallenge #githubcopilot

750

104

3 min read

Themes of Pride, Juneteenth, and Alan Turing

Jess Lee for The DEV Team

Jun 3

Join the June Solstice Game Jam: $1,000 in prizes!

#devchallenge #gamechallenge #gamedev

125

4 min read

DEV Community: The DEV Team

What was your win this week??

Congrats to the Hermes Agent Challenge Winners!

Build With Hermes Agent Winners 🏆

Write About Hermes Agent Winners 🏆

Prizes

What's Next?

Congrats to the Gemma 4 Challenge Winners!

🎉 Congratulations To…

Build With Gemma 4 Winners

Write About Gemma 4 Winners

Prizes

What's Next?

Welcome Thread - v380

How We Saved Big and Simplified Our Image Pipeline: Adopting bunny.net on DEV

The Chaos of Multi-CDN and the Billing Reality Check

Why We Hopped Over to bunny.net

1. Bunny Optimizer and Perma-Cache

2. Edge Scripting: TypeScript-Native Control

Under the Hood: Forem’s Pluggable Images::Optimizer Service

Deep Highlight: Smart Downsizing at the Edge

Graceful Failures: Smart Fallbacks Over Plain Broken Images

Future considerations

Final Thoughts

Top 7 Featured DEV Posts of the Week

What was your win this week?

Congrats to the Google I/O 2026 Writing Challenge Winners!

🏆 Congratulations To…

Prizes

What's Next?

Welcome Thread - v379

Github "Finish-Up-A-Thon" Challenge Winner Announcement Delayed & General Challenge Timeline Updates

Top 7 Featured DEV Posts of the Week

Winner Announcement Delayed for the Google I/O 2026 Writing Challenge