<?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: R.K. Mullins</title>
    <description>The latest articles on DEV Community by R.K. Mullins (@rk_mullins_9e9a87a255b5).</description>
    <link>https://dev.to/rk_mullins_9e9a87a255b5</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%2F4172087%2F7ae11446-ce7a-4af0-8175-b84b419c1d59.jpg</url>
      <title>DEV Community: R.K. Mullins</title>
      <link>https://dev.to/rk_mullins_9e9a87a255b5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rk_mullins_9e9a87a255b5"/>
    <language>en</language>
    <item>
      <title>Help Me Test My Cooking Game — Forging Cuisine (Android Closed Test)</title>
      <dc:creator>R.K. Mullins</dc:creator>
      <pubDate>Thu, 08 Oct 2026 21:35:48 +0000</pubDate>
      <link>https://dev.to/rk_mullins_9e9a87a255b5/help-me-test-my-cooking-game-forging-cuisine-android-closed-test-14l7</link>
      <guid>https://dev.to/rk_mullins_9e9a87a255b5/help-me-test-my-cooking-game-forging-cuisine-android-closed-test-14l7</guid>
      <description>&lt;p&gt;I'm Keith Mullins. I built an Android cooking game called &lt;strong&gt;Forging Cuisine&lt;/strong&gt;, and I need your help testing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is it?
&lt;/h2&gt;

&lt;p&gt;Forging Cuisine is a cooking game for everyday home cooks — not experts. You run a kitchen, learn real cooking techniques (doneness temps, flavor pairing, the kind of stuff that makes you think like a cook), and share dish cards of what you create. No ads, no in-app purchases — it's a $4.99 game, and testers get it free during the closed test.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I need
&lt;/h2&gt;

&lt;p&gt;Google Play requires &lt;strong&gt;12 testers opted in for 14 days&lt;/strong&gt; before I can apply for production access. I'm at 7 of 12 right now. I need 5 more.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's involved
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;I'll add your Gmail address to the closed testing track in the Play Console&lt;/li&gt;
&lt;li&gt;You opt in, install the game, and play it over the next couple of weeks&lt;/li&gt;
&lt;li&gt;If something breaks, there's a Report a Bug button right in the game&lt;/li&gt;
&lt;li&gt;That's it — play, have fun, tell me what breaks&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Interested?
&lt;/h2&gt;

&lt;p&gt;Drop your Gmail address in the comments or DM me, and I'll add you to the tester list. The game is in solid shape — this is about real-world testing before launch, not debugging a broken build.&lt;/p&gt;

&lt;p&gt;Thanks for helping an indie dev get his game out the door.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Keith Mullins — published author, self-taught cook, and creator of Forging Cuisine. I build things with AI and $0.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>gamedev</category>
      <category>testers</category>
      <category>cookinggame</category>
    </item>
    <item>
      <title>[Boost]</title>
      <dc:creator>R.K. Mullins</dc:creator>
      <pubDate>Thu, 08 Oct 2026 21:22:46 +0000</pubDate>
      <link>https://dev.to/rk_mullins_9e9a87a255b5/-4o1h</link>
      <guid>https://dev.to/rk_mullins_9e9a87a255b5/-4o1h</guid>
      <description></description>
    </item>
    <item>
      <title>Can't Code and Broke</title>
      <dc:creator>R.K. Mullins</dc:creator>
      <pubDate>Thu, 08 Oct 2026 21:17:55 +0000</pubDate>
      <link>https://dev.to/rk_mullins_9e9a87a255b5/cant-code-and-broke-4jlh</link>
      <guid>https://dev.to/rk_mullins_9e9a87a255b5/cant-code-and-broke-4jlh</guid>
      <description>&lt;p&gt;Build Your Own Windows &amp;amp; Mac App with AI and $0&lt;/p&gt;

&lt;p&gt;You have an idea for a Windows application.&lt;/p&gt;

&lt;p&gt;You don't know how to program, and you don't want to learn. You don't want to pay someone else to build it either.&lt;/p&gt;

&lt;p&gt;Once upon a time, you would have been stopped right there. In the time we live in now, you don't have to be.&lt;/p&gt;

&lt;p&gt;I'm Keith Mullins. I'm not a programmer — I'm a retired engineering designer, a published author, and a self-taught cook who builds things with AI. I wrote a book called &lt;em&gt;Can't Code and Broke&lt;/em&gt; that teaches non-programmers how to build real Windows and Mac applications using AI with $0 invested. This post is the short version of how it starts.&lt;/p&gt;

&lt;h2&gt;
  
  
  The most important thing you'll learn isn't programming
&lt;/h2&gt;

&lt;p&gt;It's a process: a direct, to-the-point way of thinking about and explaining what you want.&lt;/p&gt;

&lt;p&gt;Here's the mistake most people make. They open an AI chat and type something like:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Build me a Windows application that keeps track of my customers."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That sounds perfectly clear to you, because you already know what you mean.&lt;/p&gt;

&lt;p&gt;AI doesn't.&lt;/p&gt;

&lt;p&gt;What information do you want to keep about your customers? Names? Addresses? Phone numbers? Email addresses? Purchase history? The AI will guess — and it will guess wrong. Then you'll be irritated at the AI for something that was your fault for not being specific.&lt;/p&gt;

&lt;h2&gt;
  
  
  Never assume. Verify.
&lt;/h2&gt;

&lt;p&gt;That's the one rule. Apply it to every stage of the build.&lt;/p&gt;

&lt;p&gt;Before you tell AI anything, you turn your idea into something buildable: you write down exactly what the app does, screen by screen, button by button. Then you set up a free workspace. Then you learn how to talk to the AI — not like a programmer, like a person giving clear instructions.&lt;/p&gt;

&lt;p&gt;You'll test what the AI creates instead of assuming it works. When something breaks, you'll learn how to describe the problem precisely and feed it back. You'll repeat that process until your idea isn't just an idea anymore.&lt;/p&gt;

&lt;p&gt;It becomes working software you can install and run.&lt;/p&gt;

&lt;h2&gt;
  
  
  It doesn't need to be complicated
&lt;/h2&gt;

&lt;p&gt;The application you build doesn't need to be the next big thing. That's not the point. The point is to learn a process that works — one you can use again on the next idea, and the one after that.&lt;/p&gt;

&lt;p&gt;I know this works because I've done it. I went from zero programming to real working software, and I did it without spending a dime.&lt;/p&gt;

&lt;p&gt;If you want the full walkthrough — all eleven sections, from turning your idea into something buildable to building a Mac version without owning a Mac — that's what the book is for.&lt;/p&gt;

&lt;p&gt;But the core of it is right here: be specific, test everything, and never assume. Verify.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Keith Mullins is the author of Can't Code and Broke. He builds software, writes books, and cooks — all with the same philosophy: keep it simple, verify everything.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
