agilemanifesto.org/principles.html
Our highest priority is to satisfy the customer
through early and continuous delivery of valuable software.
Welcome changing requirements
even late in development. Harness change for the customer's competitive advantage.
Deliver working software frequently
from a couple of weeks to a couple of months, with a preferences to the shorter timescale.
Business people and developers must work together
daily throughout the project.
Build projects around motivated individuals
Give them the enironment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information
to and within a development team is face-to face conversation.
Agile process promote sustainable development
The sponsors, developers, and users should be able to maintain a constant pace indefinitley.
Continious attention to technical excellence and good design
enhances agility.
Simplicity
The art of maximizing the amount of work not done is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how to be more effective
then tunes and adjusts its behavior accordingly.
Working software is the primary measure of progress.
| Accessibility
--overview | API
--REST best practices --REST demo --REST vs RPC --Wikipedia API | Blockchain
--overview | Blog
--The 'Brute Force' Mistake --The Bezosian Protocol: Eliminating Learned Helplessness --The Humility Protocol: Reality Over Reputation --The Jobsian Protocol: Systems Analysis as a War on Entropy --The Jordan Framework: Engineering a Competitive Edge --Time Management as an Operational System: The Tracy Framework --Tracy on Goals: Vector Alignment & Execution | Cloud
--AWS overview | CSS/HTML
--Admissions Portal Simulation Lab --Bootstrap carousel --Grid demo --markdown demo | DevOps
--Agile Principles --DevOps overview --Drupal, containerized --Prometheus & Grafana --RKE2: Deploying the Rancher Kubernetes Engine | Encoding
--Overview | Ergonomics
--Desk configuration --Device fleet --Input device array --keystroke mechanics --Phones & RSI | ERP
--Anthology overview --Ellucian Banner --Higher Ed ERP Simulation Lab --PeopleSoft Campus Solutions --PESC standards --Slate data model | Git
--Authoring & Deploying the Post-Receive Hook --Pipeline Optimization, Web-Root Migration, & Dependency Remediation --syntax overview --troubleshooting libcrypto | Hardware
--Device fleet --Electricity fundamentals --Homelab diagram | Identity & Access
--Automating Enterprise IAM Lifecycles --Deploying Entra Connect --Foundations --OIDC Integration --Provisioning Okta Dev Tenant | Java
--Fundamentals | Javascript
--Advanced Interaction: jQuery & UI Frameworks --input prompt demo --misc demo --Time and Date functions --Vue demo | Linux
--Auditing the live interface state using ethtool --grep demo --HCI and Proxmox --Persistent Infrastructure Telemetry: TMUX --Proxmox install --xammp ftp server | Mail flow
--DKIM, SPF, DMARC --MAPI | Microsoft
--AZ-800: Administering Windows Server Hybrid Core Infrastructure --BAT scripting --Group Policy --IIS --robocopy --Server 2022 setup - Virtualbox | Misc
--Applications --Computer Science Foundations --Field Notes: RainPoint Bluetooth Hose Timer --Protocols, TLS & Distributed Scale --regex --Resources --Runtimes, ASTs & Data Structures --Sustainable Computing --Terminology --Tribute to Computer Scientists | Networks
--BGP Peering & Security Hardening Lab --CCNA Lammle Study Guide --Cisco 1921/K9 router --NGFW vs. Legacy --routing protocols --throughput calculations | PHP/SQL
--Cookies --database interaction --demo, OSI Layers quiz --Foreign key constraint demo --fundamentals --MySQL and PHPmyAdmin setup --pagination --security --session variables --SQL fundamentals --structures --Tables display | Python
--fundamentals | Security
--Kerberos: Protocol Architecture --NTP Overview --Overview- GRC (Governance, Risk, and Compliance) --Security Blog --SSH fundamentals | Serialization
--JSON demo --YAML demo