Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-01-A: Sleep
  • UC-01-B: Task
  • UC-01-C: Timer
  • UC-01-D: Worker
• NOTES
  • JavaScript Module
  • Rust Module
  • References

FUNCTIONAL ANALYSIS

usecase-beta
  direction LR
  actor tech_stack("Tech Stack")
  systemBoundary "UC-01: Async"
    async_sleep("Sleep")
    async_task("Task")
    async_timer("Timer")
    async_worker("Worker")
  end
  tech_stack --> async_sleep
  tech_stack --> async_task
  tech_stack --> async_timer
  tech_stack --> async_worker

UC-01-A: Sleep

1. WHEN invoking a Sleep, THE module SHALL delay for a specified amount of milliseconds.
2. IF the delay is not a number, THEN the module SHALL raise an API violation error.

UC-01-B: Task

TO BE DETERMINES

UC-01-C: Timer

TO BE DETERMINES

UC-01-D: Worker

TO BE DETERMINES

NOTES

JavaScript Module

Class Architecture

classDiagram
  namespace codemelted_ns["codemelted"] {
    %% Module Core
    class CResult
    class CProtocol

    %% Async Use Case Specifics
    class CFuture~T~ {
      +cancel() void
      +execute(T data) void
      +has_completed() boolean
      +result() Promise~CResult~T~~
    }

    class CTaskCB~T~ {
      +callback(T data) T
    }

    class CTimerEvent {
      +interval() number
    }

    class CTimerProtocol

    class CWorkerEvent {
      +as_error_event() ErrorEvent
      +as_message_event() MessageEvent
      +event() ErrorEvent | MessageEvent
      +is_error() boolean
    }

    class CWorkerOptions {
      +credentials string
      +name string
      +type string
    }

    class CWorkerProtocol
    note for CWorkerProtocol "Not supported on Node runtime.<br>Make sure to use runtime_available()<br>to make sure it exists within the JavaScript runtime"

    class codemelted {
      <<module api>>
      +async_sleep(delay) Promise~void~
      +async_task(task, data, delay) CFuture~T~
      +async_timer(name, interval, rx_handler) CTimerProtocol
      +async_worker(name, options, rx_handler, url) CWorkerProtocol
    }
  }

  CFuture --> CResult: returns
  CTimerProtocol --> CTimerEvent: fires
  CTimerProtocol --|> CProtocol: implements
  CWorkerProtocol --> CWorkerOptions: consumes
  CWorkerProtocol --> CWorkerEvent: fires
  CWorkerProtocol --|> CProtocol: implements
  codemelted --> CFuture: creates
  codemelted --> CTaskCB: consumes
  codemelted --> CTimerProtocol: creates
  codemelted --> CWorkerProtocol: creates

Rust Module

TO BE DETERMINES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

Further Refined Use Case Model

UC-1: Function Feature

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• FUNCTIONAL ANALYSIS
  • UC-1: Function Feature
• NOTES
  • References

FUNCTIONAL ANALYSIS

UC-1: Function Feature

IF Describing via Behavioral Driven Development (BDD) User Story Format

• Description: As a [who], I want [what], so that [why].
• Scenario 1: Describe the scenario
  • Given: Sets up the initial context, state, or preconditions of the system before any action happens.
  • When: Describes the specific action, event, or trigger performed by the user or system.
  • Then: Specifies the expected observable outcome or response after the action.
  • And: Extends any of the previous statements to add positive or multiple conditions, actions, or results.
  • But: Adds a negative condition, exception, or contrasting limitation to the preceding steps
• Scenario 2: Describe the scenario
  • Given: Sets up the initial context, state, or preconditions of the system before any action happens.
  • When: Describes the specific action, event, or trigger performed by the user or system.
  • Then: Specifies the expected observable outcome or response after the action.
  • And: Extends any of the previous statements to add positive or multiple conditions, actions, or results.
  • But: Adds a negative condition, exception, or contrasting limitation to the preceding steps

IF Describing via Use Case Scenario Format:

• Description: A description of what this use case is all about.
• Actors: Who / what is triggering this use case.
• Trigger: The ideal setup necessary for the use case scenario to run.
• Main Success Scenario: The primary, ideal sequence of steps where everything goes right and the user achieves their goal without errors
• Alternate Flows: Different paths or optional behaviors that still lead to success (e.g., a customer pays with PayPal instead of a credit card)
• Exception Flows: Paths handling errors, invalid inputs, or system failures (e.g., a declined credit card or an out-of-stock item)
• Post-Condition: The expectation when the main success scenario completes.

IF Describing via EARS Function Requirements Format:

• Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
• State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
• Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
• Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
• Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

NOTES

References

Table of Contents

• CODE
  • CSS Styles
  • JavaScript Module
  • Linux / Unix Shell Script
  • PowerShell Script
  • Rust Module
  • Webpage
• MARKDOWN
  • Feature Request
  • Object-Oriented Analysis and Design (OOAD)
  • Process
  • README
  • Test Case

CODE

The following are starter coding templates that either conform to the given languages SDK documentation tool or just has a comments section for good maintenance purposes.

CSS Styles

CSS styles serve as the basis for styling an HTML webpage. It can create a rich User Interface experience to aid in developing either static website, Single Page Application (SPA), or a Progressive Web Application (PWA) taking full advantage of a near native experience without the hassle of an app store. The organization below is a guide in grouping your CSS in a way that allows for easy maintenance and overrides to flow appropriately.

/*
===============================================================================
@file BRIEF ABOUT FILE
@author EMAIL / WEBSITE
@copyright © 2026 AUTHOR. All Rights Reserved.
@license MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the 'Software'), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge,  publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

@history
- YYYY-MMM-DD:
@todos
1. Thing to do in file.
===============================================================================
*/

/* ========================================================================= */
/* [ROOT VARIABLES] ======================================================== */
/* ========================================================================= */


/* ========================================================================= */
/* [GLOBAL HTML TAG STYLES] ================================================ */
/* ========================================================================= */

/* ========================================================================= */
/* [CUSTOM HTML ELEMENT STYLES] ============================================ */
/* ========================================================================= */

/* ========================================================================= */
/* [ID TAG STYLES] ========================================================= */
/* ========================================================================= */

/* ========================================================================= */
/* [REUSABLE CLASS STYLES] ================================================= */
/* ========================================================================= */

JavaScript Module

Any complicated JavaScript full-stack solution should utilize ES6 modules. This allows for segmenting code into organized chunks. The below template is validated via typedoc which universally makes the nicest documentation between the different JavaScript V8 runtimes and web pages alike. Extra information is stored within this example to allow for one-off module management. For larger projects, this additional information would be unnecessary. The // @ts-check at the top of the module is key for utilizing modern type checking within major code editors and linters.

// @ts-check
// ============================================================================
/**
 * <mark>Add Image Tag if you have one.</mark>
 *
 * | Key       | Value                                                        |
 * | --------- | ------------------------------------------------------------ |
 * | AUTHOR    | EMAIL / WEBSITE                                              |
 * | COPYRIGHT | © YYYY NAME. All Rights Reserved.                            |
 * | VERSION   | v26.X.Y (Last Updated YYYY-DD-MM)                            |
 *
 * <mark>Introduce the module.</mark>
 *
 * # FEATURES
 *
 * <mark>Identify the important aspects of the project and what makes it cool.</mark>
 *
 * # GETTING STARTED
 *
 * <mark>Identify the steps necessary to be successful with the repo.</mark>
 *
 * # USAGE
 *
 * <mark>Identify how to use the repo once getting started is done.</mark>
 *
 * ## TODOS
 *
 * - <mark>Track things that need changing.</mark>
 *
 * # LICENSE
 *
 * <mark>Identify the license that governs this repo.</mark>
 *
 * @module starter_module
 */
// =============================================================================
// [MODULE CORE] ===============================================================
// =============================================================================

// Put your module privates here

// =============================================================================
// [PUBLIC API] ================================================================
// =============================================================================

// Put exports below here.

Linux / Unix Shell Script

Every now and again you will need to build quick utilities in a terminal shell. The example below gives the ability to manage such a script whether it is a personal tool chain or represents a bigger DevOps solution. No individual versioning is captured but keeping a version history and to-do section is handy when you are individually managing the script, but it does not exist in source control repository.

#!/usr/bin/env bash
# =============================================================================
# FILE: WHAT IS THIS SCRIPT FOR
# AUTHOR: email / website
# COPYRIGHT: © YYYY NAME. All Rights Reserved.
# LICENSE: MIT License
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the 'Software'), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge,  publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included
# in all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# HISTORY:
# - [YYYY-MMM-DD]:
# TODOS:
# 1. What to do.
# =============================================================================
function main {
  local VERSION = "vXX.Y.Z [Last Modified YYYY-MMM-DD]"
  # You can also break up the script with more functions making it very
  # versatile for writing complex BASH scripts for you UNIX / LINUX system.
  function sub_task {
    # See sub_task
  }

  # -------------------------------------------------------------------------
  # [MAIN] ------------------------------------------------------------------
  # -------------------------------------------------------------------------
  $action = $1
  if [ "$action" == "help" ]; then
    # Do something with the action.
    sub_task
  fi
}
main $@

PowerShell Script

Same as the Linux / Unit Shell Script a Windows terminal shell offers PowerShell. Unlike traditional Linux / Unix shells utilize POSIX rules for passing strings, PowerShell offers Object parsing utilizing .NET core. What is even more powerful, is that PowerShell core can run on Linux / Unix shells as well-meaning you can create a cross-platform shell script.

It has all the modern programming language niceties wrapped into a shell environment. Its help system is fully integrated into the environment with the ability to build distributable modules or scripts via the PowerShell Gallery. To that end however, most users are just creating simple scripts to the example below follows the same paradigm as shell scripts with the PowerShell script. If you want to develop more complicated, scripts, visit PowerShell Learn for examples of organizing such scripts.

#!/usr/bin/pwsh
# =============================================================================
$ABOUT_SCRIPT = @{
file = @"
What does the script do...
"@
author = "mark.shaffer@codemelted.com / codemelted.dev"
copyright = "© 2025 - 2026 Mark Shaffer. All Rights Reserved."
license = @"
MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE SOFTWARE.
"@
history = @"
- 2026-MMM-DD: What was modified.
"@
todos = @"
1. Things to do.
"@
}
# =============================================================================
function main {
  # You can also break up the script with more functions making it very
  # versatile for writing complex powershell scripts for you devops needs.
  function sub_task {
    # do sub_task work.
  }

  # Start defining the main of the script
  [string]$action = $args[0]
}
main @args

Rust Module

Rust has a very powerful way of organizing modules. Understanding that module system helps to build powerful memory safe applications. To this end, when starting off, you can organize modules within a module source file. Each source file in a Rust project is a module that can be divided up with more modules. When the scope of this module grows to large, you can break it out into a more organized module project. But this serves as a good starting point. Delete sections not needed in the introductory header based on your companies coding standards.

// ============================================================================
//! | Key       | Value                                                       |
//! | --------- | ----------------------------------------------------------- |
//! | AUTHOR    | EMAIL / WEBITE.                                             |
//! | COPYRIGHT | © YYYY NAME. All Rights Reserved.                           |
//!
//! # FEATURES
//!
//! <mark>Identify the important aspects of the project and what makes it cool.</mark>
//!
//! # GETTING STARTED
//!
//! <mark>Identify the steps necessary to be successful with the repo.</mark>
//!
//! # USAGE
//!
//! <mark>Identify how to use the repo once getting started is done.</mark>
//!
//! # TODOS
//!
//! <mark>List of TODOs that need handling within the module.</mark>
//!
//! # LICENSE
//!
//! MIT License
//!
//! © YYYY NAME. All Rights Reserved.
//!
//! Permission is hereby granted, free of charge, to any person obtaining a
//! copy of this software and associated documentation files (the "Software"),
//! to deal in the Software without restriction, including without limitation
//! the rights to use, copy, modify, merge, publish, distribute, sublicense,
//! and/or sell copies of the Software, and to permit persons to whom the
//! Software is furnished to do so, subject to the following conditions:
//!
//! The above copyright notice and this permission notice shall be included in
//! all copies or substantial portions of the Software.
//!
//! THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
//! IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
//! FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
//! THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
//! LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
//! FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
//! DEALINGS IN THE SOFTWARE.
// ============================================================================
// [MODULE CORE IMPLEMENTATION] ===============================================
// ============================================================================
#![doc(html_logo_url =
  "https://codemelted.com/assets/favicon/apple-touch-icon.png")]

/// Say something about the module
mod module_core {
  // Implement you module public / private here.
  // Private module with pub items are only pub within the module file.
}

// ============================================================================
// [XXX MODULE IMPLEMENTATION] ================================================
// ============================================================================

/// Say something about the module
pub mod api {
  // Implement you module public / private here.
  // When the module is pub, it is accessible to other module files.
}

Webpage

Identifies all the OpenGraph and Twitter card tags in order for sharing a page to preview properly within those apps. Also provides all the tag layouts for getting started on a simple webpage or building a complicated SPA / PWA solution.

<!DOCTYPE html>
<!--
FILE: Tell me about the file and why it exists for this project
COPYRIGHT: Any copyright information or set / delete.
LICENSE: what license or set N/A or delete.
-->
<html lang="en"><head>
  <!-- Set the title of the page-->
  <title>TITLE</title>
  <meta property="og:title" content="TITLE">
  <meta name="twitter:title" content="TITLE">
  <!-- Set who authored the page-->
  <meta name="author" content="AUTHOR NAME">
  <meta name="twitter:site" content="@yourusername OR DELETE">
  <!-- Provide a description for your page-->
  <meta name="description" content="DESCRIPTION">
  <meta property="og:description" content="DESCRIPTION">
  <meta name="twitter:description" content="DESCRIPTION">
  <!-- Set Your Website Reference-->
  <meta property="og:url" content="YOUR WEBSITE REFERENCE">
  <meta name="twitter:image" content="https://yourwebsite.com">
  <meta property="og:image" content="https://yourwebsite.com">
  <!-- Set keywords in CSV format-->
  <meta name="keywords" content="KEYWORDS">
  <!-- Image Preview For Website-->
  <meta property="og:image" content="https://example.com" />
  <meta name="twitter:image" content="https://yoursite.com/image.png" />
  <!-- Set your Favicon -->
  <link rel="icon" type="image/x-icon" href="FAVICON_LOCATION.ico">
  <!-- Leave these alone -->
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta property="og:type" content="website" />
  <meta charset="UTF-8">
  <!-- Determine what you are doing below for loading resources-->
  <link rel="stylesheet" href="STYLE_SHEET.css">
  <style>
    /* Define some styles if not externally loaded */
  </style>

  <script src="LOAD A SCRIPT"></script>
  <script>
    // Define script behavior
  </script>
</head><body>
  <!-- Build the UI -->
  <script>
    // Define script behavior
  </script>
</body></html>

MARKDOWN

With AI becoming a powerful tool within a software engineer's arsenal, it is important to apply sound software engineering principles to aid in what you are building. You should control the AI tool, not the other way around. The templates below serve different aspects of software engineering techniques whether utilizing AI or not.

Each of the markdown templates have a YAML header to support webpage generation via different tools. It is then proceeded with HTML <center></center> that has an optional <img /> tag for a header image along with a <h1></h1> tag for a title. Finally, it is proceeded with a **Table of Contents** section for the breakdown of what is contained as sections. From there each template will identify the markdown header sections along with <mark></mark> tags explaining what information is utilized within the template.

Feature Request

Before becoming a full-fledged software engineer, you will start a job working Jira tickets or analyzing Discrepancy (DR) / Problem Report (PR). In either event, when you are new to a system you have to apply Black Box / White Box techniques to determine what change you are making.

The template below provides two sections. The first is the FUNCTIONAL ANALYSIS to allow for fleshing out exactly what is needed to make the change complete. The second section is NOTES. This is a free-form section to capture any design elements or test changes to validate the change. This information can either "complete" the change or serve as information into larger artifacts within your development process. Hence, its free-form nature.

---
title: "My Document Title"
date: YYY-MMM-DD
author: "Jane Doe"
description: ""
tags: []
categories:
---

<center>
  <mark>Project logo</mark>
  <h1>Project Title</h1>
</center>

<mark>Brief introduction to the feature being requested. Could be from a Jira board, assigned problem report, customer request, or the start of a bigger project. This focuses mainly functionality of a singular request and may serve as a bigger piece of a whole.</mark>

**Table of Contents**

- [FUNCTIONAL ANALYSIS](#functional-analysis)
  - [UC-1: Function Feature](#uc-1-function-feature)
- [NOTES](#notes)

# FUNCTIONAL ANALYSIS

<mark>An introductory use case model or other architecture diagram that may aid in visualizing the different requirements categories below.</mark>

<mark>Add a new model for each complex Function Feature that may need further pictorial and feature breakdown until it is at its lowest testable functional description.</mark>

## UC-1: Function Feature

<mark>IF Describing via Behavioral Driven Development (BDD) User Story Format</mark>

- **Description:** As a [who], I want [what], so that [why].
- **Scenario 1:** Describe the scenario
    - *Given:* Sets up the initial context, state, or preconditions of the system before any action happens.
    - *When:* Describes the specific action, event, or trigger performed by the user or system.
    - *Then:* Specifies the expected observable outcome or response after the action.
    - *And:* Extends any of the previous statements to add positive or multiple conditions, actions, or results.
    - *But:* Adds a negative condition, exception, or contrasting limitation to the preceding steps
- **Scenario 2:** Describe the scenario
    - *Given:* Sets up the initial context, state, or preconditions of the system before any action happens.
    - *When:* Describes the specific action, event, or trigger performed by the user or system.
    - *Then:* Specifies the expected observable outcome or response after the action.
    - *And:* Extends any of the previous statements to add positive or multiple conditions, actions, or results.
    - *But:* Adds a negative condition, exception, or contrasting limitation to the preceding steps

<mark>IF Describing via Use Case Scenario Format:</mark>

- **Description:** A description of what this use case is all about.
- **Actors:** Who / what is triggering this use case.
- **Trigger:** The ideal setup necessary for the use case scenario to run.
- **Main Success Scenario:** The primary, ideal sequence of steps where everything goes right and the user achieves their goal without errors
- **Alternate Flows:** Different paths or optional behaviors that still lead to success (e.g., a customer pays with PayPal instead of a credit card)
- **Exception Flows:** Paths handling errors, invalid inputs, or system failures (e.g., a declined credit card or an out-of-stock item)
- **Post-Condition:** The expectation when the main success scenario completes.

<mark>IF Describing via EARS Function Requirements Format:</mark>

- Ubiquitous (Always Active): The <system name> shall <system response> (e.g., The mobile phone shall have a mass of less than 150 grams
- State-Driven (Active During a State): While <state>, the <system name> shall <system response> (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
- Event-Driven (Triggered by an Event): When <trigger>, the <system name> shall <system response> (e.g., When the user presses the power button, the device shall turn on)
- Optional Features: Where <feature is present>, the <system name> shall <system response> (e.g., Where the navigation package is installed, the system shall display the map)
- Unwanted Behavior: If <unwanted trigger>, then the <system name> shall <system response> (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

# NOTES

<mark>Add any specific notes that will aid in the implementation and validation of the given feature request. This can include UML artifacts, examples, test demonstration, etc. to satisfy the full implementation of the feature request.</mark>

Object-Oriented Analysis and Design (OOAD)

From the book Managing Software Requirements (A Use Case Approach) 2nd Ed it provides a fully fleshed out template for performing a full Object-Oriented Analysis and Design utilizing use cases. To that end, the template has been tweaked to break out FUNCTIONAL ANALYSIS still utilizing a use case model as the introduction, but identifies the different ways of deriving and fleshing out functional behavior of a system. From there the NON-FUNCTIONAL ANALYSIS allows for the breakdown of all the different non-functional areas of a system usually forgotten or ignored. Finally, the DESIGN ANALYSIS allows for designing out the rest of the software / hardware / system boundaries to fully flesh out the design.

This template can be all encompassing or broken up into different OOAD markdown files for larger more complex systems. It is really up the software engineer in managing how this is broken up to make sense. The key is if you build it, keep in sync and up to date with the software solution you are building.

---
title: "My Document Title"
date: YYY-MMM-DD
author: "Jane Doe"
description: ""
tags: []
categories:
---
<center>
  <mark>Company Logo If Available</mark>
  <h1>ID: Title</h1>
</center>

**Table of Contents**

- [INTRODUCTION](#introduction)
  - [Purpose](#purpose)
  - [Scope](#scope)
  - [Terms](#terms)
  - [References](#references)
- [FUNCTIONAL ANALYSIS](#functional-analysis)
  - [UC-1: Function Feature](#uc-1-function-feature)
- [NON-FUNCTIONAL ANALYSIS](#non-functional-analysis)
  - [Usability](#useability)
  - [Reliability](#reliability)
  - [Performance](#performance)
  - [Supportability](#supportability)
  - [Design Constraints](#design-constraints)
  - [Documentation](#documentation)
  - [Purchased Components](#purchased-components)
  - [Licensing and Security](#licensing-and-security)
  - [Legal, Copyright and Other Notices](#legal-copyright-and-other-notices)
  - [Applicable Standards](#applicable-standards)
  - [Internationalization and Localization](#internationalization-and-localization)
  - [Physical Deliverables](#physical-deliverables)
  - [Installation and Deployment](#installation-and-deployment)
- [DESIGN ANALYSIS](#design-analysis)
  - [Communication Interfaces](#communication-interfaces)
  - [Hardware Interfaces](#hardware-interfaces)
  - [Software Interfaces](#software-interfaces)
  - [User Interfaces](#user-interfaces)

# INTRODUCTION

## Purpose

<mark>The purpose outlines the reason for creating the process. It answers the question “why is this being done?” and provides direction, motivation, and clarity for all stakeholders involved. A well-defined purpose sets the overarching goals and desired outcomes, ensuring that everyone understands the intent behind the document.</mark>

## Scope

<mark>The scope specifies the boundaries, extent, and limitations of the process. It answers “what is included and what is excluded?” and defines the deliverables, tasks, responsibilities, and areas covered. Scope ensures that the project remains focused and manageable, preventing unnecessary expansion or deviation from the original goals.</mark>

## Terms

<mark>Breakdown of acronyms and definitions</mark>

## References

<mark>Any outside references that inform this breakdown.</mark>

# FUNCTIONAL ANALYSIS

<mark>An introductory use case model or other architecture diagram that may aid in visualizing the different requirements categories below.</mark>

<mark>Add a new model for each complex Function Feature that may need further pictorial and feature breakdown until it is at its lowest testable functional description.</mark>

## UC-1: Function Feature

<mark>IF Describing via Behavioral Driven Development (BDD) User Story Format</mark>

- **Description:** As a [who], I want [what], so that [why].
- **Scenario 1:** Describe the scenario
    - *Given:* Sets up the initial context, state, or preconditions of the system before any action happens.
    - *When:* Describes the specific action, event, or trigger performed by the user or system.
    - *Then:* Specifies the expected observable outcome or response after the action.
    - *And:* Extends any of the previous statements to add positive or multiple conditions, actions, or results.
    - *But:* Adds a negative condition, exception, or contrasting limitation to the preceding steps
- **Scenario 2:** Describe the scenario
    - *Given:* Sets up the initial context, state, or preconditions of the system before any action happens.
    - *When:* Describes the specific action, event, or trigger performed by the user or system.
    - *Then:* Specifies the expected observable outcome or response after the action.
    - *And:* Extends any of the previous statements to add positive or multiple conditions, actions, or results.
    - *But:* Adds a negative condition, exception, or contrasting limitation to the preceding steps

<mark>IF Describing via Use Case Scenario Format:</mark>

- **Description:** A description of what this use case is all about.
- **Actors:** Who / what is triggering this use case.
- **Trigger:** The ideal setup necessary for the use case scenario to run.
- **Main Success Scenario:** The primary, ideal sequence of steps where everything goes right and the user achieves their goal without errors
- **Alternate Flows:** Different paths or optional behaviors that still lead to success (e.g., a customer pays with PayPal instead of a credit card)
- **Exception Flows:** Paths handling errors, invalid inputs, or system failures (e.g., a declined credit card or an out-of-stock item)
- **Post-Condition:** The expectation when the main success scenario completes.

<mark>IF Describing via EARS Function Requirements Format:</mark>

- Ubiquitous (Always Active): The <system name> shall <system response> (e.g., The mobile phone shall have a mass of less than 150 grams
- State-Driven (Active During a State): While <state>, the <system name> shall <system response> (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
- Event-Driven (Triggered by an Event): When <trigger>, the <system name> shall <system response> (e.g., When the user presses the power button, the device shall turn on)
- Optional Features: Where <feature is present>, the <system name> shall <system response> (e.g., Where the navigation package is installed, the system shall display the map)
- Unwanted Behavior: If <unwanted trigger>, then the <system name> shall <system response> (e.g., If the password is entered incorrectly three times, then the system shall lock the account)

# NON-FUNCTIONAL ANALYSIS

## Usability

<mark>State the requirements that affect usability.</mark>

## Reliability

<mark>State the requirements for reliability</mark>

## Performance

<mark>State the performance characteristics of the system, expressed quantitatively where possible and related to use cases where applicable.</mark>

## Supportability

<mark>State the requirements that enhance system supportability or maintainability</mark>

## Design Constraints

<mark>State the design or development constraints imposed on the system or development process.</mark>

## Documentation

<mark>State the requirements or user and/or administrator documentation.</mark>

## Purchased Components

<mark>List the purchased components used with the system, licensing or usage restrictions, and compatibility/interoperability requirements</mark>

## Licensing and Security

<mark>Describe the licensing and usage enforcement requirements or other restrictions for usage, security, and accessibility</mark>

## Legal, Copyright and Other Notices

<mark>Describe the licensing and usage enforcement requirements or other restrictions for usage, security, and accessibility.</mark>

## Applicable Standards

<mark>Reference any applicable standards and the specific sections of any such standards that apply.</mark>

## Internationalization and Localization

<mark>State any requirements for support and application of different user languages and dialects</mark>

## Physical Deliverables

<mark>Define any specific deliverable artifacts required by the user or customer</mark>

## Installation and Deployment

<mark>Describe any specific deliverable artifacts required by the user or customer</mark>

# DESIGN ANALYSIS

<mark>Define the interfaces that must be supported by the application. Utilize necessary UML and modeling definitions to reflect it.</mark>

## Communication Interfaces

## Hardware Interfaces

## Software Interfaces

## User Interfaces

Process

CMMI stands for Capability Maturity Model Integration. It is a global framework designed to help businesses improve their performance, build key capabilities, and measure work processes CMMI Institute

Per the CMMI: Guidelines for Process Integration and Product Improvement (2nd Ed), any repeating process an organization does should be documented. The CMMI provides a framework defining levels 1 through 5 for an organizations process maturity. To that end, the template below serves a starting point for documenting these processes. It also serves as a good starting point for an AI plan to scope what the AI is to perform and how to do it.

---
title: "My Document Title"
date: YYY-MMM-DD
author: "Jane Doe"
description: ""
tags: []
categories:
---

<center>
  <mark>Company Logo If Available</mark>
  <h1>ID: Title</h1>
</center>

**Table of Contents**

- [INTRODUCTION](#introduction)
  - [Purpose](#purpose)
  - [Scope](#scope)
  - [Terms](#terms)
  - [References](#references)
- [PROCESS](#process)
  - [Role](#role)
  - [Trigger](#trigger)
  - [Inputs](#inputs)
  - [Deliverables](#deliverables)
  - [Procedure](#procedure)

# INTRODUCTION

## Purpose

<mark>The purpose outlines the reason for creating the process. It answers the question “why is this being done?” and provides direction, motivation, and clarity for all stakeholders involved. A well-defined purpose sets the overarching goals and desired outcomes, ensuring that everyone understands the intent behind the document.</mark>

## Scope

<mark>The scope specifies the boundaries, extent, and limitations of the process. It answers “what is included and what is excluded?” and defines the deliverables, tasks, responsibilities, and areas covered. Scope ensures that the project remains focused and manageable, preventing unnecessary expansion or deviation from the original goals.</mark>

## Terms

<mark>Breakdown of acronyms and definitions</mark>

## References

<mark>Any outside references that inform this breakdown.</mark>

# PROCESS

<mark>Mermaid diagram of the process flow</mark>

## Roles

<mark>Identify the participants within this process and what they perform</mark>

## Inputs

<mark>Identify the inputs to this process to allow it to function.</mark>

## Deliverables

<mark>Identify the deliverable artifacts when this process is completed.</mark>

## Procedure

1. The thing
2. The other thing

README

When first making a software repository for a new software component, it is good to have a README.md file that introduces the project. It breaks into four sections. FEATURES introduces what is important aspects of the project and what makes it useful. The GETTING STARTED identifies how you utilize the repo to be successful. Finally, the USAGE begins the basic usage of the repo with larger SDK documentation giving the greater context of full usage of the repo software solution.

---
title: "My Document Title"
date: YYY-MMM-DD
author: "Jane Doe"
description: ""
tags: []
categories:
---

<center>
  <mark>Project logo</mark>
  <h1>Project Title</h1>
</center>

<mark>Introduce the project and why it is important</mark>

**Table of Contents**

- [FEATURES](#features)
- [GETTING STARTED](#getting-started)
- [USAGE](#usage)
- [LICENSE](#license)

# FEATURES

<mark>Identify the important aspects of the project and what makes it cool.</mark>

# GETTING STARTED

<mark>Identify the steps necessary to be successful with the repo.</mark>

# USAGE

<mark>Identify how to use the repo once getting started is done.</mark>

# LICENSE

<mark>Identify the license that governs this repo.</mark>

Test Case

A test case serves as a black-box technique for validating software systems. Usually breaking into Functional (test of system functional requirements) and Regression (non-degradation validation between releases) Test Cases. These can serve as a manual executed by human or with modern tooling, an automated test suite. In either event, this serves a good starting point for these types of tests. These also usually in larger software / system organizations, map to specific requirements in a larger traceability matrix.

---
title: "My Document Title"
date: YYY-MMM-DD
author: "Jane Doe"
description: ""
tags: []
categories:
---

<center>
  <mark>Company Logo If Available</mark>
  <h1>ID: Title</h1>
</center>

**Table of Contents**

- [APPROACH](#approach)
  - [Objectives](#objectives)
  - [Limitations](#limitations)
- [SETUP](#setup)
  - [Pre-Conditions](#pre-conditions)
  - [Test Data](#test-data)
  - [Post-Conditions](#post-conditions)
- [PROCEDURE](#procedure)

# APPROACH

## Objectives

<mark>The specific objectives to be met during testing usually lining up to requirements.</mark>

## Limitations

<mark>Any limitations associated with executing this test case.</mark>

# SETUP

## Pre-Conditions

<mark>The required system state or setup before starting.</mark>

## Test Data

<mark>Specific inputs, usernames, or files needed.</mark>

## Post-Conditions

<mark>The final state of the system when PROCEDURE is completed</mark>

# PROCEDURE

<mark>Step: Clear, numbered actions to perform.</mark>
<mark>Action: The action to perform</mark>
<mark>Expected Result: How the system should behave.</mark>
<mark>Actual Result: What the system actually did (filled during testing).</mark>
<mark>Status: Pass, Fail, or Blocked</mark>

| Step | Action | Expected Result | Actual Result | Status |
| ---- | ------ | --------------- | ------------- | :----: |

TO BE DEVELOPED

March 08, 2026

It was Sunday, March 1, 2026. I am putting the finishing touches to my codemelted.com domains. At the center of those domains is my codemelted_web.js module, the module that ties all the domains together and provides a common app bar between the sites.

This app bar provides access to external services via the icon to the left. The combo box provides the ability to switch between all the domains. The actions to the right provide controls common to each site. The whole goal is to have each domain serve as a dedicated service and can easily integrate into other services. In this case social media linked from your profile.

With all the sites properly working and testing we are a go to begin sharing links. That is where the trouble began. It was about 10:30 pm, been coding and testing all day, and go to utilize the threads mobile app to share a link and low and behold, sites will not render. What!! Well-being 11:00 it was time for bed.

Trying to Debug Someone Else’s App

So while working my normal 9-5 on Monday, March 2, 2026, I had to come up with a way to replicate the error. I tried quick and dirty fixes thinking the problem could be related to a caching issue, but none of those made any difference. Looking at the codemelted_web.js I determined it had to be on the pages' initialization. So I did an alert() call within catch block of to initialize. But I also realized, threads probably blocks pop-ups. So I needed to whip up an Android app with a WebView.

Flutter Android App

So I started a Flutter mobile app. Confirmed it would run on my Pixel 9. Went to pub.dev and installed the webview_flutter package into the project. Set the URL to my codemelted_web_tester.html file and ran the project. Low and behold a bug was caught and shown.

Now with an ability to replicate my sites bugs, I began the debugging task of figuring out what the heck was going on.

The Solution

After a fixing the first unavailable Browser API feature I ran the test again to be met with a different unavailable Browser API feature. It was at this moment I realized I needed to go through all my action buttons and test them from within a mobile view. Lucky for me the core codemelted.js module central to the codemelted.rs Project, I had an ability to detect the different “failing” items. That fix is reflected below.

It turns our that my text-to-speech, share, and printing were unusable from a mobile web view. So I utilized the if_def() from the codemelted.js module and ensured those features were hidden or not setup. This allowed for my website to fully render. Now we were ready for the final test.

Threads Rendering

With my fix in-place and deployed to my website came the moment of truth, will the Threads mobile app render my site. So I loaded it up, cleared its WebView cache and selected my site and low and behold, it rendered properly. It also loaded properly on Instagram which also uses the Android WebView. X never had an issue because it does not utilize a WebView but a Chrome view which is a scaled down Chrome tab tied to the X app.

Conclusion

The work above took the Monday to identify the issue, Tuesday to identify all the fixes, and Wednesday to fully deploy to my site. However, this did not represent the root of the bug. The root is within the codemelted.js module. Now this module is in its alpha release powering my sites, but the mistake made there was detecting if a website is within a Web Browser JavaScript runtime and not the individual features themselves. So while my site can work around the issue, the root of the issue needs to be properly solved in the codemelted.js module. Defects have been identified within the GitHub repo.

Another consideration when debugging a WebView rendering of your page. You must uninstall the test app from your mobile device in order to pick up the latest deployed code to your site. If you don’t do this, you will pick up the last cache’d version of whatever you were testing. So keep that in mind if you find yourself in this situation. I hope this article helps someone in the future.

It was Thursday Jun 26, 2025. I had packed up my Jeep and was making my way over the Pennsylvania turnpike to arrive at my destination with my cousin and his family. Sadly it was about five hours into the drive, thunderstorms abound, so I decided to put up at a hotel. Finish the drive Friday and I arrived. Next on the mission was the Garden State Comic Fest. My time to discover new and independent comic content 😎.

Prequel to the Journey

This story really has a prequel in that after watching Avengers End Game it seems modern content has become rather stale. That is what led me on a journey to discover independent content. This is where I discovered the two YouTubers who also produced independent comic content. These YouTubers are Clownfish TV and Dannphan.

Clownfish TV

These guys run their own YouTube Channel reviewing pop culture and other indie comic news. Hosted by Keon and Geeky Sparkles, they have an animated presentation style where each of their avatars bounce while they present their “rants” of what they are reviewing. What I really enjoyed is they had published their own books featured below.

DannPhan (Burning Star Comics)

Next on my journey of discovering indie creators I stumbled into Trisha. She has her own YouTube Channel where she to talks about the happenings of different comics, anima, and mangas. Her Friday live show is my favorite as it is chill and her audience is very friendly. Of course, she had the biggest collection of comics she has produced over the years on her Burning Star Comics where you can order both print and ebook versions of her work. I ordered the print as featured below.

Fest Time

So as stated earlier I arrived at my cousins in Jersey on Friday. Got cozy for the Saturday event. Got to travel the 95 north bound paying the lovely tolls before finally getting off the 95 to head to the event center. It was an awesome setup next to a zoo in a nice town. Jersey does have some pretty spots in the state 😂.

Ghostbusters

So I got parked and headed to the entrance. At the entrance I was greeted by Eco-1 from the ghostbusters. Not sure who built it, but this converted Hurst was a spot on replica of the ghostbusters automobile. The guys in costume were looking good as well.

Once at the entrance I got my nifty attendee placard and began taking in the fest. It was overwhelming at first, but I am an introvert by nature. So I walked the event floor taking in the cosplayers and seeing what indie comic creators were set up and selling.

Meeting Trisha and Adam

Then I found Trisha and Adam. They were the reason I decided to do the fest, so I got to meet them in person and discuss their work. They were awesome people. That is when I bought my first book.

Discovered Indie Creators

I was at the fest for a little over 6 hours. The pictures below represent the roughly $380 I spent in books and knick-knacks. These are books / comics (including above) I plan to read and write blog reviews on. And if I ever get off my duff, maybe a YouTube video review 😱.

Daemon Manx

He is the author of a 4 part book series. His story got me hooked and while listening I noticed the gem below. It represented all the books in one nicely hardbound book. So of course I had to purchase it. You can check out his website at daemonmanx.com

Blackbox Comics

Going from memory these guys represented one of the bigger displays. I believe it was a husband / wife duo and that had whole complete series of comic in a vast array of genres. In the end I bought the two below. Check out their website at blackboxcomics.net

Maurice Alvarez & Ande Li

These authors produced the below 3 part series along with a prequel. The described story and artwork sold me so I purchased them. You can find them at Maurice Alvarez and Ande Li.

Harpoon Creative Industries

As stated from the book I purchased, “Imagine if your favorite demon hunter had a bit of a drinking problem and a toxic relationship with her mom. Now, ask her to save the world.”

Ok that intro along with the authors' passion for the book sold me so here it is. Check it out at harpooncreativeindustries.com

Dreamscape Publishing

They had the MarcV series of comics from 2024. The story was an interesting premise but what fascinated me about it was the interactiveness woven into the story. Meaning you had a QR coded embedded in the comic pages that allow for an interactive story. A cool way of blending modern tech with a comic. So I thought I would give it a try. Check them out at dreamscapepub.com

Art Pieces

The following was a set of cool pieces I purchased. Unfortunately I cannot find a card from the artist. However, their signature is to the left if anyone can identify them. Their work was perfect as you can see below.

Wrapping Up the Day

So after discovering all the cool content from the fest I ran into Sean Kanan, a.k.a. Mike Barnes from the Karate Kid 3 and Cobra Kai series. He was really fun to talk to along with all the memorabilia he had signed from the original actors of Karate Kid universe. Now I had spent my money at this point and started asking the price of items. Well needless to say they were out of my price range except for hot sauce he was selling. That was in my price range and wrapped up what was an awesome experience. He evened signed the sauce for me 😂.

More about that can be found at badboyeast.com.

From the Bringing an Idea to an MVP slide presentation implemented before COVID, I built an MVP prototype of a Raspberry Pi touch screen system for my 2006 Jeep Wrangler. The goal is to eventually one day travel to Prudhoe Bay, Alaska. Well I have a newer Jeep and the technology has gotten faster. This is the upgrade and evolution of this initial idea. This is the Raspberry Pi build out. Further slides will follow for each of the steps of the build.

View Embedded Content

In my early Internet days my fastest Internet I could get living in rural Colorado was AOL dial-up at 48.8 kilobits. Earthlink and MSN could not even compare. But then one day we got high speed Internet, A whole whopping 9 megabits up / down for a whopping $100 a month. Now we are cooking. This was the early 2000s.

Well when I moved to Indiana, Comcast offered to get me 25 megabits up / down but for $55 a month. They tried to sell me on 50 megabits up / down for $25 more a month, but I did not need it. I just saved a bunch and 4x my speed. This was about 8 years ago. Well has my high speed journey been crazy since COVID. This is the story.

ISP Reviews

The following reviews are of three ISPs in the greater Indiana area stretching from 2016 to 2024.

Comcast

So while living in Indiana, the 25 megabits up / down was more than enough. I had a small stint as a contractor in Baltimore, MD for a year and T-Mobile came in clutch for hotspot 4G LTE Internet in the hotel. Well once back from Baltimore I bought my house and stuck with Comcast. Well COVID hit and as many others, I had to work from home along with my children doing online school.

What happened, data caps. The cost to up the data cap was ridiculous. Also, 25 megabits was no longer cutting it. So I start shopping around and discover Frontier. 500 megabits up / down for $75 a month, no contract, no data caps, fiber. Hell yeah.

Now Comcast is known in online reviews for crappy customer service. I never had this experience. Getting through to a person, well that is a different story but once connected, they were great to work with. Naturally they could not beat the Frontier deal.

Frontier

All in all the 500 megabit fiber service is nothing to complain about. It did as it stated. I was not locked into a contract. The speeds more than got children and I through our new online reality. Life was great. But the reality is, like others, I am looking to cut costs and really no longer need the 500 megabit connection to the Internet for my current needs. Enter T-Mobile and 5G Internet from home. I will discuss that later.

The issue I had with Frontier is with attempting to quit. Now I was not locked into any contracts. I simply wanted to terminate the Internet and return the equipment. This was back in Oct 2024. Well the lady would not take no for an answer. To top it off, I was going to be charged for next month’s Internet and have to pay a $50 restocking fee of the modem. Now to be fair you are not leasing the modem, so I guess this is to make up for that fact, but it was annoying nonetheless. Either way I got two months free and the lady stated to call back in November to then cancel. She stated she was giving me a deal as I would only be charged the $50 restocking fee.

Cut to November 2024 and I call to cancel. Well they cannot identify me with the PIN that was on my bill with the new sales lady. So she has to send me out a paper with a PIN to confirm my identity. Fine. Well it just so happens that the paper comes when the new bill cycle kicks in, so I would be charged for the Internet I have not used for almost two months. I was ticked.

NOTE: I am not stating the lady did that on purpose, the timing was just annoying.

So cut to Dec 2024 and I call. Finally, I was able to cancel the service. The third sales lady was nice and not only canceled the new Internet charge that would hit me, but also waived the $50 restocking fee. But my gosh, why couldn’t I just cancel in the first place!!!!

T-Mobile

What can I say? T-Mobile has been awesome. Their 5G home Internet is awesome. The reason for the switch was I get the home Internet, cell phone plan, and Netflix covered for $100 a month. That’s it. Internet speeds are about 150 megabits up / down, and I have never had any issues with T-Mobile. Trying to get through to their customer support is cumbersome but as a whole, it is just a downright awesome deal with no contract. Isn’t their modem cute? No running of cables or drilling required.

Final Thoughts

• Comcast: If you are looking to bundle cable subscriptions with your Internet and are not worried about data caps, sure. But there are faster services.
• Frontier: If you need speed they can’t be beat for the price. But my goodness, they will not let you quit even though you are not in a contract. And a restocking fee for the modem, come on.
• T-Mobile: WINNER. For the price, no contract, no data caps, cell phone and a streaming subscription covered, quit at any time. Yeah, they have more than earned my commitment.

NOTE: The opinions expressed in this article are my own. You cannot draw any statistical significance with a sample size of one. So do your research. 😁

Before COVID I had a plan with my 2005 Jeep TJ to make a trip to Prudhoe Bay, Alaska. Unfortunately we all know what happened with that. But the idea spurned a fun project I did for work that is carrying over into a new design with a hopeful new trip in 2023 or 2024 time frame.

View Embedded Content

In every software engineering career you will encounter a job that leaves a lasting impression because things went well, or you had good teammates. You will also encounter jobs where nothing goes right, the manager is a pain, and nobody on the team pulls their wait. Then there is the mythical unicorn. A beast that does not exist in software engineering, but I got to experience one time. Where the project was delivered ahead of time, hit all quality metrics established by the contract, and under budget. You never get all three. You typically on a good project will get two out of the three. The presentation below is a presentation I gave at one of my jobs documenting this unicorn and the things I believed were the reason for this encounter. Enjoy.

View Embedded Content