<?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: Professor Wolfe</title>
    <description>The latest articles on DEV Community by Professor Wolfe (@professor_wolfe_0ca9faedc).</description>
    <link>https://dev.to/professor_wolfe_0ca9faedc</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%2F4247779%2F2f2f7af9-c236-4938-9293-fce5725f3c99.jpg</url>
      <title>DEV Community: Professor Wolfe</title>
      <link>https://dev.to/professor_wolfe_0ca9faedc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/professor_wolfe_0ca9faedc"/>
    <language>en</language>
    <item>
      <title>Five small Node.js tools, two huskies, and an experiment in making development more fun</title>
      <dc:creator>Professor Wolfe</dc:creator>
      <pubDate>Mon, 16 Nov 2026 12:38:37 +0000</pubDate>
      <link>https://dev.to/professor_wolfe_0ca9faedc/five-small-nodejs-tools-two-huskies-and-an-experiment-in-making-development-more-fun-3206</link>
      <guid>https://dev.to/professor_wolfe_0ca9faedc/five-small-nodejs-tools-two-huskies-and-an-experiment-in-making-development-more-fun-3206</guid>
      <description>&lt;p&gt;A discussion with my programming students about creativity sent me down a side-project rabbit hole. I wanted to make something for fun, then see whether it could become useful outside the joke.&lt;/p&gt;

&lt;p&gt;That became &lt;strong&gt;DeployAnyway&lt;/strong&gt;, a collection of five small open-source Node.js tools. My huskies, Dallas and Benji, supplied the inspiration: plenty of curiosity, enthusiasm, and the occasional questionable decision.&lt;/p&gt;

&lt;p&gt;The motto is “Software nobody requested, built with questionable priorities, and shipped with absolute confidence!” The software still needs to preserve failures and check actual results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with something you can run
&lt;/h2&gt;

&lt;p&gt;With Node.js 22.13+ or 24, try:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx @deployanyway/bro-say &lt;span class="s2"&gt;"The tests passed. Suspicious, but welcome."&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That puts your message into an original terminal character's speech bubble. There are character, mood, theme, wrapping and thought-bubble options, plus a structured API.&lt;/p&gt;

&lt;p&gt;The part I hope earns its place in build scripts is the build summary. Install the package:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install @deployanyway/bro-say
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then render facts collected by your script:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;renderBuildSummary&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@deployanyway/bro-say'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;summary&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;renderBuildSummary&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Release build'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;exitCode&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;tests&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;passed&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;42&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;failed&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;skipped&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;durationMs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1520&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;commit&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'example-commit'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;summary&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Those numbers are illustrative input, not a test runner's output. Your script supplies its real results and preserves the underlying command's exit status. Passing test counts alone do not establish that a build succeeded.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rest of the collection
&lt;/h2&gt;

&lt;p&gt;Each package works independently:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;error-translator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Explains supported Node.js errors and follows &lt;code&gt;Error.cause&lt;/code&gt; chains with practical debugging checks. Unknown errors remain unknown.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;excuse-js&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Generates developer excuses for comic relief, or drafts incident updates from known facts. Public incident updates keep the jokes off.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;doggo-log&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Provides log levels, JSON output, async request context and configurable secret redaction, with optional dog commentary.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ship-it-meter&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Evaluates test reports, coverage and build receipts against release policies, and explains missing evidence or blockers.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;There is a &lt;a href="https://deployanyway.github.io/launch/" rel="noopener noreferrer"&gt;runnable workflow combining all five&lt;/a&gt;: logging a request, diagnosing a failure and checking release evidence. The docs explain which behavior runs in the browser and which requires Node.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Codex helped
&lt;/h2&gt;

&lt;p&gt;I used OpenAI Codex extensively for implementation, tests, declaration types, documentation and release workflows. I supplied the ideas, direction and feedback; I maintain the projects and am responsible for what ships. AI also helped prepare this article.&lt;/p&gt;

&lt;p&gt;The project went through repeated revisions. One lesson was that “it builds and the tests pass” is a different milestone from “another developer wants this in their project.” That's the part I'm trying to learn about now.&lt;/p&gt;

&lt;p&gt;The libraries do not require an AI service at runtime.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try one and tell me what you'd change
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://deployanyway.github.io/" rel="noopener noreferrer"&gt;Interactive demos — no signup or installation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/DeployAnyway" rel="noopener noreferrer"&gt;Source, documentation and issues on GitHub&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.npmjs.com/org/deployanyway" rel="noopener noreferrer"&gt;All five packages on npm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you try one, would it earn a place in a real script or codebase? What would make you keep it, and what feels unnecessary? A confusing example or a reason you wouldn't use it is useful feedback too.&lt;/p&gt;

&lt;p&gt;Disclosure: these are my projects. They're MIT-licensed, and contributions and bug reports are welcome.&lt;/p&gt;

</description>
      <category>node</category>
      <category>javascript</category>
      <category>opensource</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
