AI Compliance Checklist
AlexAtkinson
/ AI_Prompt_Vendor_Economics.md
Last active
February 21, 2026 09:21
AI Prompt: Vendor Economics
- The "Loss-Model" State
- Current Market Trend: (e.g., Aggressive land-grab vs. focus on operational efficiency)
- Primary Growth Driver: (e.g., Infrastructure scaling, R&D spend, or enterprise adoption)
- The Profitability Split: Briefly distinguish between "Pure-Play Labs" (OpenAI/Anthropic) and "Ecosystem Providers" (Google/Meta/Microsoft).
Important
Disclaimer: This IS NOT legal advice.
Until the mid-2010's the "technology industry" was widely considered to be unregulated, resulting in tremendous harm. The colloquialism "move fast and break things" is from these times, and despite being a proven travesty, continues to influence leadership across industry.
Fortunately, today, both data and related business operations are regulated.
Unfortunately, there are many in leadership roles who see the compliance-related fines and penalties as acceptable business risks -- especially as their expected tenure ostensibly limits personal exposure to said risks.
These primers are designed to improve user AIX, optimize AI cost, and bias toward ethical, legal, and organizationally approved engineering practices.
Prompt
Act as my engineering assistant. Your primary directive is to read, adhere to, and apply the rules defined in AI_Prompt_Primers.md located at:
https://gist.githubusercontent.com/AlexAtkinson/0967496361367d0279d1b70843e7b0e3/raw/AI_Prompt_Primers.md
Once you have processed the rules, begin by assessing this project and generating a prioritized TODO list."
RELATED: Git Branching Strategies, Versioning, Artifacting
These processes comprise the bulk of the technical footprint necessary for developing and releasing software products.
Important
Like Git, there are too few who understand this material -- especially in startups.
While this material may not initially be as appealing to non-technical leadership as shipping a feature, it becomes imperative with the first major outage, failed InfoSec audit, or data breach.
AlexAtkinson
/ Git_Branching_Strategies.md
Last active
February 27, 2026 19:19
An actionable overview of branching strategies.
RELATED: SDLC, ALM, & SDLC, Versioning, Artifacting
From the merge hell of SVN and the early days of Git to the refined tactics we enjoy today, there have been many developments in branching strategies, but only a few remain relevant. This document covers these strategies as well as their adoption considerations.
The first three strategies are the most commonly used, with the fourth highlighting a critical anti-pattern, and the last being used for Linux kernel development; and some other large projects. Skip learning about the last two for now, but know that they exist.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/usr/bin/env bash | |
| # v1: https://gist.github.com/AlexAtkinson/7a60dc26a8dd94fb910e01529b379ae2 | |
| # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| # PW Material Generator | |
| # Notes: | |
| # - Used by genpass | |
| # - Generates 20 characters per invocation | |
| # - Takes ~1ms per character generated on an average | |
| # system | |
| # - Will _always_ lead with an ALPHA character |
NOTICE: iptables is being deprecated. See nftables.
Understanding the architecture of netfilters is helpful, but not necessary to make use of the information here.
Redirect operations are quite involved. Here are a few of the highlights:
- The files: '/dev/std{in,out,err}', are symlinks to file descriptors.
- File descriptors (aka file handles) are numbers that identify open files.
- A file is an object that stores data, information, settings, or commands.
- The numbers commonly seen in the redirect '2>&1' are file descriptors.
- Running 'file /dev/std*' outputs: /dev/stdin: symbolic link to /proc/self/fd/0
NewerOlder