<?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: Chris</title>
    <description>The latest articles on DEV Community by Chris (@deadcatfound).</description>
    <link>https://dev.to/deadcatfound</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%2F4024628%2F34e06b68-2c9f-462b-bfab-e4b7214cec1a.png</url>
      <title>DEV Community: Chris</title>
      <link>https://dev.to/deadcatfound</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/deadcatfound"/>
    <language>en</language>
    <item>
      <title>How to Run Claude Code as a Background Worker on Your Mac</title>
      <dc:creator>Chris</dc:creator>
      <pubDate>Sun, 08 Nov 2026 02:27:26 +0000</pubDate>
      <link>https://dev.to/deadcatfound/how-to-run-claude-code-as-a-background-worker-on-your-mac-2cli</link>
      <guid>https://dev.to/deadcatfound/how-to-run-claude-code-as-a-background-worker-on-your-mac-2cli</guid>
      <description>&lt;p&gt;I run an AI trading desk on a Mac Mini: eight agents and scheduled jobs around the clock, all on a Claude subscription with no API key. It took me a few months of 3am breakages to get Claude Code working while I'm away from the keyboard. Below is the setup that held, plus the failures, so you can skip them.&lt;/p&gt;

&lt;p&gt;Claude Code has a non-interactive mode (&lt;code&gt;claude -p "prompt"&lt;/code&gt;) that prints an answer and exits. You wrap it in a loop, let macOS keep the loop alive, and you get a worker on the subscription you already pay for.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Log in once, in a real terminal
&lt;/h2&gt;

&lt;p&gt;Headless runs reuse the login from your normal session. Open Terminal and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude auth login
claude &lt;span class="nt"&gt;-p&lt;/span&gt; &lt;span class="s2"&gt;"say OK"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the second command prints &lt;code&gt;OK&lt;/code&gt;, background runs will work too. If it asks you to log in, fix that first. A background run can't answer a login prompt and will fail with nothing on screen.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Write the worker loop
&lt;/h2&gt;

&lt;p&gt;This version watches a folder. Drop a &lt;code&gt;.txt&lt;/code&gt; file with a prompt into &lt;code&gt;~/worker/inbox&lt;/code&gt; and the answer shows up in &lt;code&gt;~/worker/done&lt;/code&gt;. You can swap the folder for an API call or a database later and keep the same loop.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;#!/bin/bash&lt;/span&gt;
&lt;span class="c"&gt;# ~/worker/worker.sh&lt;/span&gt;
&lt;span class="nv"&gt;IN&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$HOME&lt;/span&gt;&lt;span class="s2"&gt;/worker/inbox"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nv"&gt;OUT&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$HOME&lt;/span&gt;&lt;span class="s2"&gt;/worker/done"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nv"&gt;LOG&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$HOME&lt;/span&gt;&lt;span class="s2"&gt;/worker/worker.log"&lt;/span&gt;
&lt;span class="nb"&gt;mkdir&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$IN&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$OUT&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;

&lt;span class="k"&gt;while &lt;/span&gt;&lt;span class="nb"&gt;true&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do
  for &lt;/span&gt;job &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$IN&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;/&lt;span class="k"&gt;*&lt;/span&gt;.txt&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt;
    &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="nt"&gt;-e&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$job&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;]&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="k"&gt;continue
    &lt;/span&gt;&lt;span class="nv"&gt;name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;basename&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$job&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; .txt&lt;span class="si"&gt;)&lt;/span&gt;
    &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;&lt;span class="s2"&gt; start &lt;/span&gt;&lt;span class="nv"&gt;$name&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$LOG&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
    &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="nv"&gt;out&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;claude &lt;span class="nt"&gt;-p&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;cat&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$job&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &amp;lt; /dev/null 2&amp;gt;&amp;amp;1&lt;span class="si"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then
      &lt;/span&gt;&lt;span class="nb"&gt;printf&lt;/span&gt; &lt;span class="s1"&gt;'%s\n'&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$out&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$OUT&lt;/span&gt;&lt;span class="s2"&gt;/&lt;/span&gt;&lt;span class="nv"&gt;$name&lt;/span&gt;&lt;span class="s2"&gt;.md"&lt;/span&gt;
      &lt;span class="nb"&gt;rm&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$job&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
    &lt;span class="k"&gt;else
      &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;&lt;span class="s2"&gt; FAIL &lt;/span&gt;&lt;span class="nv"&gt;$name&lt;/span&gt;&lt;span class="s2"&gt;: &lt;/span&gt;&lt;span class="nv"&gt;$out&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$LOG&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
      &lt;span class="k"&gt;case&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$out&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;
        &lt;span class="k"&gt;*&lt;/span&gt;&lt;span class="s2"&gt;"limit"&lt;/span&gt;&lt;span class="k"&gt;*&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nb"&gt;sleep &lt;/span&gt;1800 &lt;span class="p"&gt;;;&lt;/span&gt;   &lt;span class="c"&gt;# usage cap: wait it out, retry later&lt;/span&gt;
      &lt;span class="k"&gt;esac&lt;/span&gt;
    &lt;span class="k"&gt;fi
  done
  &lt;/span&gt;&lt;span class="nb"&gt;sleep &lt;/span&gt;30
&lt;span class="k"&gt;done&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;chmod&lt;/span&gt; +x ~/worker/worker.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The script deletes a job file only after a successful run. A failed job stays in the inbox and the loop retries it on the next pass.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Keep it alive with launchd
&lt;/h2&gt;

&lt;p&gt;Close a terminal tab and your loop dies with it. launchd, the macOS service manager, can start your script at login and restart it if it crashes. Save this as &lt;code&gt;~/Library/LaunchAgents/com.you.claude-worker.plist&lt;/code&gt; and change &lt;code&gt;YOU&lt;/code&gt; to your username:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="cp"&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;/span&gt;
&lt;span class="cp"&gt;&amp;lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;plist&lt;/span&gt; &lt;span class="na"&gt;version=&lt;/span&gt;&lt;span class="s"&gt;"1.0"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;dict&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;Label&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&amp;lt;string&amp;gt;&lt;/span&gt;com.you.claude-worker&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;ProgramArguments&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;array&amp;gt;&amp;lt;string&amp;gt;&lt;/span&gt;/bin/bash&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&amp;lt;string&amp;gt;&lt;/span&gt;/Users/YOU/worker/worker.sh&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&amp;lt;/array&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;EnvironmentVariables&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;dict&amp;gt;&amp;lt;key&amp;gt;&lt;/span&gt;PATH&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;/Users/YOU/.local/bin:/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&amp;lt;/dict&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;RunAtLoad&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&amp;lt;true/&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;KeepAlive&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&amp;lt;true/&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;StandardErrorPath&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&amp;lt;string&amp;gt;&lt;/span&gt;/Users/YOU/worker/stderr.log&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/dict&amp;gt;&amp;lt;/plist&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;launchctl load ~/Library/LaunchAgents/com.you.claude-worker.plist
&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"Write a haiku about cron jobs"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; ~/worker/inbox/test.txt
&lt;span class="c"&gt;# wait ~30s&lt;/span&gt;
&lt;span class="nb"&gt;cat&lt;/span&gt; ~/worker/done/test.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. The four things that break it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;PATH.&lt;/strong&gt; launchd starts your script with a bare PATH, so the first error you'll likely hit is &lt;code&gt;claude: command not found&lt;/code&gt;. Run &lt;code&gt;which claude&lt;/code&gt; in Terminal and make sure that folder is in the plist's PATH line.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Auth expiry.&lt;/strong&gt; Your login expires after a while, and a power outage can leave it stale. After that each run fails with a 401 until you log in again in a real terminal. The worker can't do that step for you. Check once an hour with &lt;code&gt;claude -p "say OK"&lt;/code&gt; and send yourself an alert if it doesn't come back &lt;code&gt;OK&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Usage caps.&lt;/strong&gt; Your subscription has a session limit and a weekly limit, and the worker shares both with you. Read the error before you alert on it. My setup fired "auth failing" alarms for four hours one afternoon when I had only hit the session cap. When you see a limit message, have the worker wait and retry.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sleep.&lt;/strong&gt; Your Mac runs nothing while it sleeps. On a desktop, set it to never sleep in System Settings or run the worker under &lt;code&gt;caffeinate -s&lt;/code&gt;. A laptop with the lid closed stops too, unless you plug it into power and an external display.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Watch your burn.&lt;/strong&gt; If your agents can create their own follow-up work, they can eat a weekly limit in days. Mine used 11% of my week in a single day because each job queued "monitor" and "finalize" jobs of its own. I fixed it two ways: each job has to finish as done or blocked, and no job may queue new work for itself.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Where to take it next
&lt;/h2&gt;

&lt;p&gt;Swap the inbox folder for a real queue. A small web service hands out jobs, and the worker on your Mac claims them with a token, runs them on your subscription, and posts the results back. You never hand the service an API key. If your Mac is off, the jobs wait, so show an "offline" badge to whoever is waiting on them.&lt;/p&gt;




&lt;p&gt;I built &lt;a href="https://deadcatfound.org/floor" rel="noopener noreferrer"&gt;The Floor&lt;/a&gt; on this pattern: a trading ops desk where the hosted side queues work and a small runner on your machine does it with Claude Code, Codex, Gemini CLI or Ollama. Paper trading only. &lt;a href="https://premium.deadcatfound.org/demo" rel="noopener noreferrer"&gt;Demo here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally posted at &lt;a href="https://deadcatfound.org/guides/claude-code-background-worker" rel="noopener noreferrer"&gt;deadcatfound.org&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claude</category>
      <category>macos</category>
      <category>ai</category>
      <category>automation</category>
    </item>
    <item>
      <title>I run an AI trading firm on a used Mac Mini. Here is how it is put together.</title>
      <dc:creator>Chris</dc:creator>
      <pubDate>Sun, 02 Aug 2026 03:28:44 +0000</pubDate>
      <link>https://dev.to/deadcatfound/i-run-an-ai-trading-firm-on-a-used-mac-mini-here-is-how-it-is-put-together-59ap</link>
      <guid>https://dev.to/deadcatfound/i-run-an-ai-trading-firm-on-a-used-mac-mini-here-is-how-it-is-put-together-59ap</guid>
      <description>&lt;p&gt;Three months ago I wanted to know whether a set of AI agents could run a research desk end to end without me sitting over them. So I built one. It has been running since May on a used Mac Mini I paid $343 for, and everything it does gets published.&lt;/p&gt;

&lt;p&gt;Paper money only. Up 4.47% since May, worst drawdown along the way was 5.3%. That is not the interesting part. The interesting part is what breaks.&lt;/p&gt;

&lt;h2&gt;
  
  
  No dependencies
&lt;/h2&gt;

&lt;p&gt;The whole thing is the Python standard library plus sqlite3. No third party packages at all.&lt;/p&gt;

&lt;p&gt;That sounds like a constraint I would regret and it has not been. What I gave up: pandas, requests, a dozen convenience libraries. What I got: nothing to pin, nothing to resolve, no virtualenv to activate, and it runs on a fresh machine with nothing but Python on it.&lt;/p&gt;

&lt;p&gt;I have never lost an evening to a broken install, and that used to be most of my lost evenings.&lt;/p&gt;

&lt;p&gt;If you are building something that has to run unattended for months, the dependency you do not have is the one that cannot break at 9:35 on a Tuesday.&lt;/p&gt;

&lt;h2&gt;
  
  
  launchd, not cron, not Docker
&lt;/h2&gt;

&lt;p&gt;Every job is a launchd agent. Market open trigger, per-strategy executors, data fetch, sync, publish.&lt;/p&gt;

&lt;p&gt;Two things I learned the hard way.&lt;/p&gt;

&lt;p&gt;The machine going to sleep will silently kill your schedule. I lost a signal because the Mac dozed through a 15:50 window and nothing anywhere told me. The fix is a caffeinate -i -s job with KeepAlive that never gets unloaded. It looks ridiculous sitting in the agent list. Leave it there.&lt;/p&gt;

&lt;p&gt;StartCalendarInterval fires on wall clock, not on completion. If a job runs longer than its interval you now have two of them fighting over the same state file.&lt;/p&gt;

&lt;h2&gt;
  
  
  One account per strategy
&lt;/h2&gt;

&lt;p&gt;Seven strategies, seven separate broker accounts. This is the single best decision in the system.&lt;/p&gt;

&lt;p&gt;Blend them into one account and a losing strategy hides inside a winning month forever. Split them and every month tells you which one actually earned it. Last week I shut one down because its edge turned out to be an artifact of the parameter grid I had searched rather than anything real. I only knew because it had its own equity curve to look at.&lt;/p&gt;

&lt;p&gt;The cost is bookkeeping. Worth it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The failure that taught me the most
&lt;/h2&gt;

&lt;p&gt;A strategy hit its kill threshold and halted. It flattened its positions at the broker correctly. Then it returned before writing that back to its own state file.&lt;/p&gt;

&lt;p&gt;For two days the code believed it held three positions that did not exist. Nothing crashed. Nothing logged an error. Every downstream job read a state file that was quietly wrong.&lt;/p&gt;

&lt;p&gt;I found it by diffing local state against the broker's positions endpoint, which is now something that runs on a schedule instead of whenever I happen to think of it.&lt;/p&gt;

&lt;p&gt;The lesson generalises well past trading. Your stop path has to finish writing state, not just stop. An early return in an error branch is exactly where this hides, because the happy path is the one you tested.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure, do not model
&lt;/h2&gt;

&lt;p&gt;I assumed my fills were 5 to 10 basis points optimistic. Then I pulled 125 real filled orders and compared each one against that session's close. The median was -5.9 bps on market entries, and 43% of them filled better than the close. My estimate was worse than reality.&lt;/p&gt;

&lt;p&gt;One caveat if you try this: split the audit by order type. Stop and limit exits fill when the market is moving against you, that is the entire point of them, so leaving those in makes your entries look far worse than they are.&lt;/p&gt;

&lt;p&gt;Same pattern on my own website. I spent weeks convinced I had a traffic problem. Added a beacon and found people were reaching the final step, hitting an OS security warning, then following instructions on my own page that had stopped working on current macOS.&lt;/p&gt;

&lt;p&gt;Both times I had a strong belief and no measurement, and both times the measurement said something else.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it is now
&lt;/h2&gt;

&lt;p&gt;It runs unattended. Market opens, agents pull their data, size positions, place orders, log what they did, publish it. I read a summary at night.&lt;/p&gt;

&lt;p&gt;Happy to answer anything about the agent setup, keeping scheduled jobs alive on a Mac, going dependency free, or how the isolation is wired.&lt;/p&gt;

</description>
      <category>python</category>
      <category>architecture</category>
      <category>showdev</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>I'm not a real developer, so I built my app the simplest way possible</title>
      <dc:creator>Chris</dc:creator>
      <pubDate>Sat, 18 Jul 2026 00:27:30 +0000</pubDate>
      <link>https://dev.to/deadcatfound/im-not-a-real-developer-so-i-built-my-app-the-simplest-way-possible-2m79</link>
      <guid>https://dev.to/deadcatfound/im-not-a-real-developer-so-i-built-my-app-the-simplest-way-possible-2m79</guid>
      <description>&lt;p&gt;I'm not a developer by trade. I'm a basic upper-middle management guy with an MBA, that works a cyber project management job by day. So take this as "here's what worked for me," not expert advice.&lt;/p&gt;

&lt;p&gt;When I rebuilt an old trading script into a real app — a local tool that runs AI agents to test trading strategies and write up the results — I made one rule for myself: keep it as simple as humanly possible. No extra software bolted on. Just Python and a single file to hold the data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why
&lt;/h2&gt;

&lt;p&gt;Because I'm not an engineer. Every extra piece of software you add on is one more thing that can break — and one more thing I won't know how to fix at 1am. The more the app leans on other people's tools, the more likely I am to get stuck. So I kept the moving parts down to almost nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The upside
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Anyone can run it as long as they have Python. No complicated setup.&lt;/li&gt;
&lt;li&gt;All the data lives in one file, so backing it up is just copy and paste.&lt;/li&gt;
&lt;li&gt;Nothing to update, nothing to clash, a lot less that can go wrong.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The tradeoff
&lt;/h2&gt;

&lt;p&gt;I had to build a few basic things by hand that ready-made tools would have done for me. More work up front, and a real engineer would probably roll their eyes at some of it. But for a solo, non-expert like me, "boring and reliable" beats "fancy but fragile."&lt;/p&gt;

&lt;h2&gt;
  
  
  My honest question
&lt;/h2&gt;

&lt;p&gt;For the actual developers here: when does "keep it simple, no extras" stop being smart and start being stubborn? For me it has worked — the thing just runs. But I'm sure there's a line, and I'd like to know where you'd draw it.&lt;/p&gt;

&lt;p&gt;(If you're curious what the app is: a self-hosted paper-trading tool — practice money only, nothing leaves your machine. Demo, no signup: &lt;a href="https://premium.deadcatfound.org/demo" rel="noopener noreferrer"&gt;https://premium.deadcatfound.org/demo&lt;/a&gt;. But I care more about the "keep it simple" question than the app.)&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>python</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
