<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Austin Riedel</title>
    <description>The latest articles on DEV Community by Austin Riedel (@austin_build_with_arc).</description>
    <link>https://dev.to/austin_build_with_arc</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4242420%2F7f8f6ccd-d77e-4eb1-9a0d-85ea29d8bc11.png</url>
      <title>DEV Community: Austin Riedel</title>
      <link>https://dev.to/austin_build_with_arc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/austin_build_with_arc"/>
    <language>en</language>
    <item>
      <title>RecipeHub 02: The secret ingredient is data</title>
      <dc:creator>Austin Riedel</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:33:57 +0000</pubDate>
      <link>https://dev.to/austin_build_with_arc/recipehub-02-the-secret-ingredient-is-data-5cm3</link>
      <guid>https://dev.to/austin_build_with_arc/recipehub-02-the-secret-ingredient-is-data-5cm3</guid>
      <description>&lt;p&gt;&lt;em&gt;The data model is the secret ingredient&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Project 0001 · GitHub for Recipes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TLDR:&lt;/strong&gt; We built a complete production version of GitHub for Recipes in less than a day with ARC. This series shows how.&lt;/p&gt;

&lt;p&gt;New to the series? Start with &lt;a href="https://buildwitharc.io/blog/building-with-arc" rel="noopener noreferrer"&gt;00 · Introducing Building With ARC&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://buildwitharc.io/blog/recipehub-01-prd-not-product" rel="noopener noreferrer"&gt;Last week&lt;/a&gt;, we went through the initial discovery phase for RecipeHub: the early creative process where we took our idea and started to define what we actually wanted to build. Today we're going to talk about how it works, and how we took a recipe from text to structured data.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvzc0hf0iv6tkjlep3wam.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvzc0hf0iv6tkjlep3wam.png" alt="A Lemon Garlic Chicken recipe as written: a cream-colored recipe card with seven ingredients in one column and four numbered steps in plain text" width="800" height="406"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;As written&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0kxelxek4cco1mmfn589.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0kxelxek4cco1mmfn589.png" alt="The same Lemon Garlic Chicken recipe in RecipeHub, with ingredients colored by category, amounts and units set apart, heat levels and cooking times highlighted, and each step listing the ingredients it uses with their amounts" width="800" height="682"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;As data&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;During that process, we quickly realized that RecipeHub didn't exist just to define recipes. RecipeHub needed to actually help you cook them as well. We put together a list of pain points while cooking, created some screen designs and prototypes, and talked to a couple of chefs and home cooks. As the designs and prototypes started to take shape, we felt confident that we could improve cooking outcomes. But how?&lt;/p&gt;

&lt;h2&gt;
  
  
  Data models
&lt;/h2&gt;

&lt;p&gt;Features are the foundation for any application. They define what an application does (and doesn't do): what it does for users, what value it provides, what unique experiences it creates. In this way, features define &lt;strong&gt;what&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Data models are the first part of defining &lt;strong&gt;how&lt;/strong&gt;. A data model describes how information is structured, what different pieces of information represent, and how they relate to one another.&lt;/p&gt;

&lt;p&gt;That might sound like an abstract concept, but we encounter data models every day. At its simplest, a recipe is a data model: a list of ingredients and a set of instructions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkpu18gbuw2jmvu2e34i5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkpu18gbuw2jmvu2e34i5.png" alt="A recipe card for Lemon Garlic Chicken, annotated by hand. The whole card is one recipe. Each of its seven ingredient lines is one ingredient, and each of its four numbered paragraphs is one step." width="800" height="487"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Data models are important because they don't just define how information is structured. They define how your application understands the information, and they determine what your application can do.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Good: organizes information.&lt;/strong&gt; Gives your data a clear, consistent structure that your application can understand and work with.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Better: enables functionality.&lt;/strong&gt; Captures the relationships between information, making it easier to build the features and experiences you envision.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Best: expands what's possible.&lt;/strong&gt; Creates a foundation for capabilities that go beyond the application's original vision.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The more your application understands about its information, the more interesting features it can support.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Great data models are the secret ingredient to an application.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But the best data model isn't necessarily the most complex one. It's the one that represents your product, supports the features and functionality you want, and allows the product to evolve. To better understand that, let's look at some of the key features for RecipeHub's cook mode.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scaling
&lt;/h2&gt;

&lt;p&gt;The first feature seems simple enough. Users should be able to scale a recipe, so they can make half or twice the servings.&lt;/p&gt;

&lt;p&gt;However, our first data model says that an ingredient is each line of the ingredients list. So what happens when we double "4 boneless, skinless chicken thighs"?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwykhdje3p0trurczugnh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwykhdje3p0trurczugnh.png" alt="Two times '4 boneless, skinless chicken thighs' produces the whole line written out twice, crossed out in red, with the handwritten note: we wanted 8 thighs, not the ingredient twice." width="799" height="202"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There are ways we could get this to work. There are programmatic approaches, and we could use an LLM to do the multiplying. But that's a real trade-off you have to be aware of: the programmatic approach has edge cases, and the LLM has costs that add up across millions of recipes.&lt;/p&gt;

&lt;p&gt;For this feature, a good data model is one that separates the amount from the ingredient name. An even better data model handles the surprisingly rich ingredient entry, accounting for measurements, units and more.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpp183bm44odd214v6jcj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpp183bm44odd214v6jcj.png" alt="The ingredient split into its amount, 4, and what it counts. As data, it has a quantity of kind count with amount 4, and the name 'boneless, skinless chicken thigh'. Times 2, the amount becomes 8." width="799" height="458"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;With that model, we can easily scale the entire recipe. Our application can do something that cookbooks simply can't.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc8l34sx1x3ba51wo6i3n.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc8l34sx1x3ba51wo6i3n.png" alt="The seven Lemon Garlic Chicken ingredients as written, each mapped to a structured quantity and then doubled: 8 chicken thighs, 2 tsp salt, 1 tsp black pepper, 2 tbsp olive oil, 6 cloves garlic, 1 cup chicken broth and 2 lemons." width="800" height="285"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Every application is different and requires a different data model, based on its current and expected features. You should model only what you need (and what's on your roadmap), so a recipe app without scaling may not need this.&lt;/p&gt;

&lt;p&gt;While scaling the ingredients isn't that complex on its own, it gives us the foundation for extracting richer data from recipes. Let's see what other features we can support with a better data model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Categories
&lt;/h2&gt;

&lt;p&gt;Extracting the quantities for ingredients isn't the only feature we had in mind. We quickly started experimenting with the idea of ingredient categories, because chicken thighs, garlic, broth and lemon juice are very different ingredients with very different roles in the recipe.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fylq6h3zbxsphluwh6hop.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fylq6h3zbxsphluwh6hop.png" alt="The Lemon Garlic Chicken ingredient list with four lines circled and annotated by hand: chicken thighs are the main event, garlic is big flavor, chicken broth becomes the sauce, and lemon wakes the whole dish." width="799" height="445"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The vision for RecipeHub may have started with recipe collaboration based on GitHub, but that's not the only part of the application inspired by code. We work with code all day and rely on syntax highlighting to help us understand it, to tell apart keywords, variables, classes and everything else. It helps you understand code much more intuitively, and we wanted to do the same thing for recipes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxgrcvvuyezwdtf4n8ifb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxgrcvvuyezwdtf4n8ifb.png" alt="Four ingredients mapped to categories and their role in the recipe: chicken thighs are protein, garlic is aromatic, chicken broth is liquid, and lemon is acid." width="799" height="214"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;By defining ingredient categories, we can classify ingredients and help cooks understand what each ingredient does for a recipe. We can provide the same semantic understanding that code editors provide, but for chefs at home. This categorization is part of how we intend to improve how well each cook turns out. But it's not the only thing we're doing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cook mode
&lt;/h2&gt;

&lt;p&gt;As we mentioned in the first article, one real pain point we kept coming back to was recipes that have you adding a half dozen ingredients in a single step. You've already started cooking, your hands might be dirty, and now you have to remember how many cups, tablespoons and teaspoons of each you need.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0zucs1f399knv040i11r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0zucs1f399knv040i11r.png" alt="Step 3 of a recipe adds onions, carrots, celery, leeks, garlic and tomato paste. Six of them have no amount in the step, so the cook has to go back to the ingredients list for each one." width="800" height="254"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is a perfect example of a trade-off the original cookbook format had to make. Leaving out the amount for each ingredient in the steps saved space, and spared editors from double-checking countless cloves, cups and tablespoons. But we can easily account for this in our app: our data model, plus testing, makes something like this trivial.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvstwulc5te8mflyqc6mg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvstwulc5te8mflyqc6mg.png" alt="Steps 3 and 4 in RecipeHub's cook mode. Ingredients are colored by category, the heat level and cooking times are highlighted, and below each step a row of chips lists every ingredient it uses with its amount." width="800" height="332"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This provides a much richer view of the step, calling out the ingredients by category and highlighting key details like time and temperature. In a single glance, you can see everything you need to cook the step properly, without worrying about forgetting something.&lt;/p&gt;

&lt;p&gt;It all goes back to the user experience you're looking to provide. Once we decided we wanted to help people actually cook the recipes, we knew we needed this.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If just one user cooking at home can glance across the kitchen and remember to add the herbs thanks to their bright green color, our data model did its job.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Next course
&lt;/h2&gt;

&lt;p&gt;This article is just a taste of RecipeHub's features and data model. For our next course, we'll explore how we combined everything into one complete product spec. Then we'll cover how ARC generated all of the code.&lt;/p&gt;

&lt;p&gt;If you'd like to follow along, be sure to &lt;a href="https://buildwitharc.io/blog/recipehub-02-data-model#subscribe" rel="noopener noreferrer"&gt;join our mailing list&lt;/a&gt;. And if you'd like to learn more about ARC, and how our spec-driven development platform can help build your next application, you can contact us directly at &lt;a href="mailto:contact@buildwitharc.io"&gt;contact@buildwitharc.io&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://buildwitharc.io/blog/recipehub-02-data-model" rel="noopener noreferrer"&gt;ARC blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>database</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Building With ARC: RecipeHub</title>
      <dc:creator>Austin Riedel</dc:creator>
      <pubDate>Fri, 13 Nov 2026 22:18:30 +0000</pubDate>
      <link>https://dev.to/austin_build_with_arc/recipehub-01-prd-product-1g54</link>
      <guid>https://dev.to/austin_build_with_arc/recipehub-01-prd-product-1g54</guid>
      <description>&lt;p&gt;&lt;em&gt;Your product is more than a list of requirements, just like a recipe is more than its ingredients&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Project 0001 · GitHub for Recipes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TLDR:&lt;/strong&gt; We built a complete production version of GitHub for Recipes in less than a day with ARC. This series shows how.&lt;/p&gt;

&lt;p&gt;New to the series? Start with &lt;a href="https://buildwitharc.io/blog/building-with-arc" rel="noopener noreferrer"&gt;00 · Introducing Building With ARC&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;In the Building With ARC series, we're exploring modern software development, taking an idea all the way through to a deployed production application. Along the way, we'll talk about how the best product and engineering teams work and build, and &lt;em&gt;how teams are doing that effectively in the AI era.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;This series is for anyone building or learning how to build production applications. In our next article, we'll dig into data models, business logic, and all the other ingredients but first, we need to agree on what we're making.&lt;/p&gt;

&lt;p&gt;And we're going to do it by mixing two of my favorite things: cooking and coding.&lt;/p&gt;

&lt;h2&gt;
  
  
  Idea
&lt;/h2&gt;

&lt;p&gt;The idea was simple to start: GitHub for Recipes.&lt;/p&gt;

&lt;p&gt;Part of me thought that version control for recipes was actually a good idea, a great way to connect, share recipes and improve them. Part of me thought it was also a good way to approach software development, that recipes could be the perfect way to explore data modeling and product design.&lt;/p&gt;

&lt;p&gt;And part of me thought that "forking" a recipe was just too good to pass up.&lt;/p&gt;

&lt;p&gt;Bad puns aside, there is something special about food. A good meal brings people together, reminds you of home or makes new memories in new places. And a really great meal? That sticks with you. I bet you can recall your favorite meal right now. I was definitely thinking about the best things I've ever cooked as I started.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsgw3flpqdgxlz8k18rda.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsgw3flpqdgxlz8k18rda.jpg" alt="A white bowl of pot roast: braised beef with carrots and potatoes in a dark, glossy gravy, topped with grated cheese and chives, on a wooden table." width="800" height="1062"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The pot roast that started it all.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;All of those meals, at all of those restaurants, cafes and dining tables around the world, started as recipes. A list of ingredients, a handful of steps for turning raw ingredients into something special.&lt;/p&gt;
&lt;h2&gt;
  
  
  Vision
&lt;/h2&gt;

&lt;p&gt;I might like cooking, but I'm not a professional chef, far from it. I've messed up before and I'll mess up again. Some of those misses are on me, but there are definitely recipes with room for improvement, and not just when it comes to ingredients.&lt;/p&gt;

&lt;p&gt;Overly long, complex steps. Tricky timing. Recipes that require a photographic memory for how much of each ingredient you're supposed to add in step 7.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;There's probably a whole other post about what software teams could and should learn from highly skilled chefs and kitchens, and the importance of mise en place. But that's for another time.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It's always unfortunate when a recipe goes wrong, so I knew RecipeHub could help there.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;But it's even worse when it goes right and then is lost forever.&lt;/strong&gt; You remember the meal but not what made it so special. I remember the pot roast, but not why it came together so well that night.&lt;/p&gt;

&lt;p&gt;I knew I needed a way to track recipes, especially the changes that really worked. And I wanted to be able to share them with friends and family.&lt;/p&gt;

&lt;p&gt;As I spent more time thinking about this, the idea turned into the vision.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;RecipeHub is the best platform for recipe experimentation and collaboration.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;To be the best, RecipeHub must deliver four key experiences for recipes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create it&lt;/li&gt;
&lt;li&gt;Cook it&lt;/li&gt;
&lt;li&gt;Evolve it&lt;/li&gt;
&lt;li&gt;Share it&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;
  
  
  Discovery
&lt;/h2&gt;

&lt;p&gt;Every classic recipe started out as an experiment, some curious chef wondering if these ingredients would work well together.&lt;/p&gt;

&lt;p&gt;Every great product is an experiment as well, with a hypothesis that X is broken and it would be awesome if we could do Y instead.&lt;/p&gt;

&lt;p&gt;The first step of that experiment should always be a prototype. One of the best things about AI-enabled coding is how accessible it has made those early prototypes. Anyone can put together a prototype that shows the vision and tests whether the idea is good, whether the solution works, and whether customers like it, love it or need it.&lt;/p&gt;

&lt;p&gt;Prototyping is one of the most important parts of discovery, and it rarely stops with the first attempt. Every experiment teaches you something, and each iteration is an opportunity to build on what worked and improve what didn't.&lt;/p&gt;

&lt;p&gt;Think about cooking. Imagine if every meal you ever made was your first attempt at a recipe. You'd spend your life eating under-seasoned dinners, overcooked steaks, and strange combinations of ingredients that sounded better in theory. Great cooking comes from tasting, adjusting, and trying again. Building with AI is no different.&lt;/p&gt;

&lt;p&gt;I keep calling it an experiment because that's the best way to approach it. But experiments are driven by creativity, and creativity and curiosity are essential to the discovery process. Not every experiment works. There are misses and dead ends.&lt;/p&gt;

&lt;p&gt;But sometimes, someone combines eggs, garlic and anchovies, serves it over romaine lettuce, and the Caesar salad is born.&lt;/p&gt;

&lt;p&gt;At ARC, we consider prototyping an integral step of the process. Modern tooling allows for quick, high-fidelity screen mocks and fully interactive prototypes. That lets teams get feedback quickly, refining some ideas and moving away from others. Prototypes give you conviction about a given approach, so you can build even more valuable features on top of what's already working.&lt;/p&gt;

&lt;p&gt;Here are a few of the experiments from RecipeHub's discovery.&lt;/p&gt;


&lt;div class="ltag-slides ltag-slides--carousel"&gt;
  &lt;div class="ltag-slides__viewport"&gt;
    &lt;div class="ltag-slides__track"&gt;
      &lt;div class="ltag-slide"&gt;
      &lt;img class="ltag-slide__image" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fbuildwitharc.io%2Fimages%2Fblog%2Frecipehub-01%2Fdiff.png" alt="Diff: a side-by-side diff of a Dry-Aged Bolognese recipe, version 5 against a draft, with heavy cream removed, beef marrow added, and the fish sauce, sherry vinegar and braise time changed" width="800" height="467"&gt;
      &lt;div class="ltag-slide__title"&gt;Diff: what evolving a recipe looks like&lt;/div&gt;
&lt;/div&gt;


&lt;div class="ltag-slide"&gt;
      &lt;img class="ltag-slide__image" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fbuildwitharc.io%2Fimages%2Fblog%2Frecipehub-01%2Fprofile.png" alt="Profile: a cook's profile with a contribution heatmap of commits and cooks, pinned recipes with version, star, fork and cook counts, and a recent activity feed" width="799" height="352"&gt;
      &lt;div class="ltag-slide__title"&gt;Profile: a profile built on the vision&lt;/div&gt;
&lt;/div&gt;


&lt;div class="ltag-slide"&gt;
      &lt;img class="ltag-slide__image" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fbuildwitharc.io%2Fimages%2Fblog%2Frecipehub-01%2Fsyntax.png" alt="Syntax: a recipe's ingredient notes as published in plain text, next to the same words parsed into ingredients, substitutions and linked recipes" width="" height=""&gt;
      &lt;div class="ltag-slide__title"&gt;Syntax: structure, emerging from the prose&lt;/div&gt;
&lt;/div&gt;



    &lt;/div&gt;
      
        
      
      
        
      
  &lt;/div&gt;
    &lt;div class="ltag-slides__progress"&gt;
      &lt;span class="ltag-slides__progress-thumb"&gt;&lt;/span&gt;
    &lt;/div&gt;
&lt;/div&gt;


&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Diff: what evolving a recipe looks like.&lt;/strong&gt; We started with the classic GitHub view: the diff. What does it look like to evolve a recipe? A side-by-side diff of a draft against the current version tracks every ingredient and step that was added, removed or changed, so each tweak is saved as a new version with a note on why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Profile: a profile built on the vision.&lt;/strong&gt; Next: what should a cook's profile show? Commits and cooks side by side in a year of activity, pinned recipes with versions, stars, forks and cook counts, and a feed of recent changes. A profile about experimenting and collaborating, not just collecting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Syntax: structure, emerging from the prose.&lt;/strong&gt; The more we prototyped, the clearer it became that a recipe holds far more structured data than its text lets on. The same ingredient notes, as published and then parsed: ingredients, roles, substitutions and linked recipes pulled out of the writing, without losing the author's voice. That structure is where our next article picks up.&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Discovery creates decisions, and decisions define the product.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Those decisions can't be lost. They need to be written down as project documents: a functional spec or PRD defining what the product does. Some products need additional documents, with more detailed explanations of how key features work. As we got clearer on the experiences we wanted RecipeHub to provide, we created several documents that we'll share in our next article.&lt;/p&gt;

&lt;p&gt;So now we have our product definition. Or do we?&lt;/p&gt;

&lt;h2&gt;
  
  
  Alignment
&lt;/h2&gt;

&lt;p&gt;We only have a product definition if all of our decisions, documents, prototypes and the entire team are aligned. Otherwise, we have missing features, bugs and angry customers.&lt;/p&gt;

&lt;p&gt;Good teams spend a lot of time and energy making sure they're aligned. Are they aligned on what the product does, and what it doesn't do? Are individual features aligned, creating a cohesive user experience? Most importantly, is what they're building aligned with what customers actually want or need?&lt;/p&gt;

&lt;p&gt;Alignment is when the creativity of discovery coalesces into a valid product definition.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Your product isn't your PRD or your prototype. It's your idea, your vision, everything from discovery, and the decisions you make when you see them together.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's why we built ARCitect, an agentic IDE for writing production-grade specifications. ARCitect works with you, understanding your screens, prototypes, diagrams and documents to define your product spec. It doesn't just pull everything together: it flags conflicts and open questions and refines feature requirements to create the best version of your product. You can read more in the &lt;a href="https://buildwitharc.io/blog/arcitect-2-0" rel="noopener noreferrer"&gt;ARCitect 2.0 announcement&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Alignment and a clear product definition have become even more important in the era of AI-enabled coding. Say the PRD says one thing and the prototype shows something different. You can write thousands of lines of code, and burn millions of tokens, working from conflicting definitions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;At ARC, we fully embrace spec-driven development. With ARCitect, we turn product documents and prototypes into complete, coherent functional specifications. Those functional specs become the single source of truth, the authoritative definition of the product.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;By creating a single source of truth, we create alignment for every product on our platform.&lt;/strong&gt; Whether you're coding yourself, working with developers or with agents, everyone is operating from the same definition.&lt;/p&gt;




&lt;p&gt;*Originally published on the &lt;a href="https://buildwitharc.io/blog/recipehub-01-prd-not-product" rel="noopener noreferrer"&gt;ARC blog&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>webdev</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
