
Hello! We're kicking off another DEV Weekend Challenge, a short bite-sized challenge planned to fit...
Hello! We're kicking off another DEV Weekend Challenge, a short bite-sized challenge planned to fit into your weekend. We know the submission window is tight, so we've set the timing to ensure that no matter where you are in the world, you'll have the majority of your Saturday and Sunday to participate.
We'll select one overall winner and four prize category winners who utilize a specific technology as part of their challenge submission.
Let's get to it!
{% card %}
This weekend, we welcome you to build something inspired by passion.
Passion is the fire that drives us. It’s the rivalry that pushes competitors to greatness, the love that fuels late-night side projects, the devotion fans pour into their teams, their fandoms, their crafts. With the World Cup ongoing, passion for the game is everywhere: in the stands, in the streets, in living rooms around the world.
Please interpret this prompt however you'd like. A tribute to a rivalry (sporting or otherwise)? A tool for tracking the projects or hobbies you love? A World Cup companion app for the truly devoted fan? Something that captures obsession, romance, or team spirit? Any angle is fair game! {% endcard %}
Four prize categories are up for grabs for participants who incorporate a specific technology into their project. You don't need to use any of these tools to be eligible for our overall winner spots, but if you're curious about any of the tech, this is a great excuse to give one a try.
Pro Tip: Since prize category winners are drawn from a smaller pool of submissions, your odds of taking home a prize are meaningfully higher.
Note: You may use multiple technologies in a single submission to qualify for multiple categories, but participants are limited to one win per challenge.
All submissions will be judged on the following:
Five winners will each take home:
All participants with a valid submission will receive a completion badge.
{% card %}
Publish a post on DEV using the submission template below and the #weekendchallenge tag. Your post should give us an overview of what you made, the inspiration behind it, and a demo of your project.
Please review our judging criteria, rules, guidelines, and FAQ page before submitting so you understand our participation guidelines and official contest rules such as eligibility requirements. {% endcard %}
Check out our official challenge page for resources to help you get started with tech from our prize category partners.
Launch Time: July 10, 2026 2:00 AM UTC Submissions Due: July 13, 2026 6:59 AM UTC Here's what that looks like across a few timezones:
| Timezone | Launch Time (Local) | Submissions Due (Local) |
|---|---|---|
| PDT | Thursday, Jul 9 at 7:00 PM | Sunday, Jul 12 at 11:59 PM |
| EDT | Thursday, Jul 9 at 10:00 PM | Monday, Jul 13 at 2:59 AM |
| GMT | Friday, Jul 10 at 2:00 AM | Monday, Jul 13 at 6:59 AM |
| CEST | Friday, Jul 10 at 4:00 AM | Monday, Jul 13 at 8:59 AM |
| IST | Friday, Jul 10 at 7:30 AM | Monday, Jul 13 at 12:29 PM |
| JST | Friday, Jul 10 at 11:00 AM | Monday, Jul 13 at 3:59 PM |
| AEST | Friday, Jul 10 at 12:00 PM | Monday, Jul 13 at 4:59 PM |
<mark><strong>Winners will be announced on Thursday, July 30.</strong></mark>
Questions about the challenge? Drop them in the comments below.
Good luck!!
aiMost of us have seen a coding agent fail to complete a task we know it can do. We just don't...
googlecloudWhen building Generative AI applications, developers often encounter a massive bottleneck: sequential...
discussI’ve been thinking about sharing some electronic circuit posts on Dev.to — small circuits, DIY...
agentsWhat nobody tells you about exporting your multi-agent prototype to a local workspace. Every...
agenticarchitectAutonomous agents are genuinely good at answering messy business questions. Give one an LLM and a set...
aiPR volume went up, ticket quality didn't, and the gap got filled with LLMs on both sides of the review: bots reviewing, bots replying, bots occasionally arguing with bots about priorities that only existed in a teammate's head. Our CEO named the actual problem, and it's bigger than code review.
Workflows from the Neura Market marketplace related to this Stable Diffusion resource