# Software Survivor Full LLM Source Map

Antonio Perez is a Principal Platform Engineer who designs adaptable commerce, integration, API, and operational platforms that enable businesses to evolve without costly rewrites.

Software Survivor is both an architecture consulting presence and a practical software architecture knowledge base built from real engineering experience.

This file lists the primary crawlable consulting hubs, case studies, and published articles for Software Survivor.
Use it as a source map only. The linked pages are the authoritative content.

## Core Pages

- [Homepage](https://softwaresurvivor.com/): Identity, verified proof, platform capabilities, design principles, selected work, and consulting fit.
- [Consulting](https://softwaresurvivor.com/services): Decision-first platform consulting with focused architecture reviews, integration audits, AI workflow assessments, bounded automation pilots, and fractional Principal Engineer support.
- [Design Principles](https://softwaresurvivor.com/design-principles): Eight practical architecture principles for adaptable platforms, reliable systems, lower cognitive load, and engineering leverage.
- [About Antonio Perez](https://softwaresurvivor.com/about): Platform experience, point of view, public leadership, and working style.
- [Architecture Case Studies and Selected Work](https://softwaresurvivor.com/portfolio): Deep case studies with business constraints, architecture decisions, and outcomes, separated from additional product and client work.
- [Practical Architecture Writing](https://softwaresurvivor.com/blog): Engineering judgment for systems that need to survive change.

## Consulting Hubs

- [Platform Architecture & Custom Software Development](https://softwaresurvivor.com/custom-software-development): Custom software development for workflows that existing products cannot handle well. Build around your business needs and keep future changes manageable.
- [AI Workflow Integration Consulting](https://softwaresurvivor.com/ai-workflow-automation-consulting): AI workflow automation consulting to reduce manual work, with human approval, controlled data access, and a clear way to recover when a step fails.
- [Enterprise Systems Integration Consulting](https://softwaresurvivor.com/systems-integration-consulting): Systems integration consulting to connect business software, reduce duplicate entry, and give your team a clear way to resolve failed updates.
- [Shopify NetSuite Integration Consultant](https://softwaresurvivor.com/shopify-netsuite-integration-consulting): Shopify and NetSuite integration consulting to keep orders, payments, inventory, and refunds consistent, with clear recovery steps when updates fail.
- [Platform Modernization & Migration Consulting](https://softwaresurvivor.com/software-modernization-consulting): Software modernization consulting to make valuable systems safer and easier to change. Plan improvements and migrations without committing to a full rewrite.
- [Fractional Principal Engineer & CTO Advisory in Fresno](https://softwaresurvivor.com/fractional-cto-fresno): Fractional CTO and Principal Engineer advisory in Fresno and across the US. Get senior guidance on software architecture, vendors, hiring, and delivery.
- [Technical Architecture Review & Assessment](https://softwaresurvivor.com/technical-architecture-review): Independent technical architecture assessment before a rewrite, migration, or vendor commitment. Get ranked risks, explicit tradeoffs, and a practical next step.

## Case Studies

- [Designing a Commerce Platform Around Capabilities, Not Vendors](https://softwaresurvivor.com/portfolio/commerce-platform-capability-architecture): How a commerce platform kept business rules separate from vendor details as providers and channels changed. The platform supported 2.19M+ orders and $158.6M+ in revenue since September 2020. This anonymized case study explains the decisions and tradeoffs.
- [How Adapter Boundaries Enabled a Zero-Downtime MongoDB-to-PostgreSQL Migration](https://softwaresurvivor.com/portfolio/zero-downtime-mongodb-postgresql-migration): How a business-critical Node.js platform moved from MongoDB to PostgreSQL while the application stayed available. This anonymized case study explains the code boundaries, data checks, and plan to reverse the switch if needed.
- [Candid Moments](https://softwaresurvivor.com/portfolio/candid-moments): An ongoing founder-built SaaS that combines no-account guest photo and video uploads with private galleries, host controls, moderation operations, payments, observability, and a wedding-first acquisition strategy.
- [Tlaloc Harvest](https://softwaresurvivor.com/portfolio/tlaloc-harvest): A launch-ready product foundation for coordinating surplus food redistribution across residents, businesses, volunteers, and community partners.
- [Inbox2Order](https://softwaresurvivor.com/portfolio/inbox2order): An AI-assisted workflow that turns unstructured email inquiries into structured order data with validation and review before business systems are updated.

## Published Articles

- [Planning for the Unknown, Within Reason](https://softwaresurvivor.com/blog/planning-for-unknown-within-reason) (2026-10-09): How to leave room for plausible business changes while keeping speculative flexibility, discovery work, and present delivery costs in proportion. Type: principle. Strategic status: supporting. Design principles: optimize-for-change, prefer-practical-simplicity, architecture-should-compound. Tags: software-development, e-commerce.
- [Zoom In, Zoom Out: Reasoning About Software Systems](https://softwaresurvivor.com/blog/zoom-in-zoom-out-software-systems) (2026-10-02): Using individual capabilities and complete business workflows together to understand a system, expose missing decisions, and judge whether its pieces actually fit. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, optimize-for-the-next-engineer, reliability-is-a-feature. Tags: software-development, e-commerce.
- [“All the Lego Pieces Are Around”: How I Approach Feature Estimates](https://softwaresurvivor.com/blog/lego-pieces-feature-estimates) (2026-09-25): How I use existing capabilities to reason about feature timelines, separating reuse from adaptation, new work, and the unknowns that need investigation. Type: leadership. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity, design-for-small-teams. Tags: software-development, e-commerce.
- [Why a Modular Monolith Is Often the Right Platform for a Small Team](https://softwaresurvivor.com/blog/modular-monolith-for-small-teams) (2026-09-15): How small teams can build clear capability boundaries without taking on the operational cost of distributed systems before the business has earned it. Type: architecture. Strategic status: flagship. Design principles: prefer-practical-simplicity, design-for-small-teams, optimize-for-the-next-engineer. Tags: software-development, api.
- [How I Use AI to Make Software Easier to Own](https://softwaresurvivor.com/blog/how-i-use-ai-to-make-software-easier-to-own) (2026-09-09): How I use AI to investigate, implement, challenge assumptions, and remove unnecessary complexity while retaining responsibility for engineering decisions. Type: architecture. Strategic status: supporting. Design principles: optimize-for-the-next-engineer, prefer-practical-simplicity, optimize-for-change. Tags: ai, software-development.
- [Configuration Beats Code Only When Variation Is Bounded](https://softwaresurvivor.com/blog/configuration-beats-code-when-variation-is-bounded) (2026-09-08): A decision framework for moving business rules into governed configuration without creating an untyped programming language that nobody can operate safely. Type: principle. Strategic status: flagship. Design principles: configuration-beats-code, optimize-for-change, reliability-is-a-feature. Tags: software-development, e-commerce.
- [Adapter Boundaries That Make Change Cheaper](https://softwaresurvivor.com/blog/adapter-boundaries-that-enable-change) (2026-09-01): How adapter boundaries make vendor changes easier while preserving payment outcomes, recovery decisions, and differences the business needs to know. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, optimize-for-change, optimize-for-the-next-engineer. Tags: software-development, api.
- [One Model, Many Conversations: LLM Serving, Memory, and Reasoning](https://softwaresurvivor.com/blog/one-model-many-conversations-llm-serving-reasoning) (2026-08-26): How serving engines share one model across users, isolate KV caches, batch token generation, preserve context, and spend more inference compute on reasoning. Type: architecture. Strategic status: flagship. Design principles: optimize-for-the-next-engineer, prefer-practical-simplicity. Tags: ai, software-development.
- [From GGUF to GPU: How llama.cpp Actually Runs a Model](https://softwaresurvivor.com/blog/from-gguf-to-gpu-how-llama-cpp-runs-a-model) (2026-08-26): Trace llama_decode through GGML graphs, CUDA kernels, GPU memory, and next-token generation—and see why expensive LLM inference can still be fast. Type: architecture. Strategic status: flagship. Design principles: optimize-for-the-next-engineer, prefer-practical-simplicity. Tags: ai, software-development.
- [An LLM Is Not the Program: What Is Actually Inside the Model File](https://softwaresurvivor.com/blog/an-llm-is-not-the-program) (2026-08-26): Follow an LLM request past the API and into GGUF tensors, learned parameters, attention, and the transformer layer that turns model data into logits. Type: architecture. Strategic status: flagship. Design principles: optimize-for-the-next-engineer, prefer-practical-simplicity. Tags: ai, software-development.
- [Membership Reconciliation: When an Audit Stops at 10,000 Records](https://softwaresurvivor.com/blog/when-a-complete-audit-stops-at-10000-records) (2026-08-26): How a silent 10,000-record cap, ambiguous identities, and competing sources of truth changed a production membership reconciliation. Type: case-study. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity, reliability-is-a-feature. Tags: e-commerce, api.
- [Build Around Business Capabilities, Not Vendor Features](https://softwaresurvivor.com/blog/build-around-business-capabilities) (2026-08-25): Why durable business capabilities should define platform boundaries, while commerce, payment, and ERP vendors remain replaceable implementation details. Type: principle. Strategic status: flagship. Design principles: build-around-business-capabilities, optimize-for-change. Tags: software-development, e-commerce.
- [pg-boss in Production: Reliable Background Jobs for Node.js](https://softwaresurvivor.com/blog/pg-boss-production-reliable-background-jobs-nodejs) (2026-08-11): What I learned running pg-boss in a high-volume Node.js backend: why PostgreSQL made the queue dependable, how PM2 protected web traffic, and why every job still needed to be safe to retry. Type: architecture. Strategic status: flagship. Design principles: prefer-practical-simplicity, design-for-small-teams, reliability-is-a-feature. Tags: software-development, automation.
- [The Complete Guide to AI Workflow Automation for SMBs](https://softwaresurvivor.com/blog/complete-guide-ai-workflow-automation-smb) (2026-08-04): Choose between existing tools, ordinary automation, and an AI pilot. A practical SMB guide to workflow decisions, human review, costs, and failure recovery. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity, reliability-is-a-feature. Tags: ai, automation, software-development.
- [Idempotency in NetSuite Integrations: Retries Without Duplicate Records](https://softwaresurvivor.com/blog/netsuite-integration-idempotency) (2026-07-28): A production-oriented NetSuite idempotency design using deterministic keys, persistent operation state, unique constraints, safe retries, replay, and reconciliation. Type: architecture. Strategic status: supporting. Design principles: prefer-practical-simplicity, reliability-is-a-feature. Tags: e-commerce, api.
- [How to Prevent Duplicate NetSuite Orders in Ecommerce Integrations](https://softwaresurvivor.com/blog/preventing-duplicate-netsuite-orders) (2026-07-28): How stable idempotency keys, external IDs, database constraints, operation state, ambiguous-failure handling, and reconciliation prevent duplicate NetSuite orders. Type: architecture. Strategic status: supporting. Design principles: prefer-practical-simplicity, reliability-is-a-feature. Tags: e-commerce, api.
- [Production Checklist for AI-Built or AI-Assisted Software](https://softwaresurvivor.com/blog/production-checklist-ai-assisted-software) (2026-07-28): A production readiness checklist for software built with AI assistance, covering architecture, tests, security, observability, data handling, and maintenance. Type: architecture. Strategic status: supporting. Design principles: optimize-for-the-next-engineer, reliability-is-a-feature. Tags: ai, software-development.
- [Shopify ERP Integration Architecture: What Changes When Ecommerce Becomes Business-Critical](https://softwaresurvivor.com/blog/shopify-erp-integration-architecture) (2026-07-28): A practical architecture for business-critical Shopify and ERP integrations across ownership, orders, customers, inventory, payments, fulfillment, returns, retries, and operations. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, optimize-for-change, reliability-is-a-feature. Tags: e-commerce, software-development.
- [Shopify + NetSuite Inventory Sync: Choosing the Source of Truth](https://softwaresurvivor.com/blog/shopify-netsuite-inventory-sync) (2026-07-28): Diagnose Shopify and NetSuite inventory sync discrepancies: separate quantity definitions, location mappings, timing, and failed updates before replacing a connector. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, optimize-for-change, reliability-is-a-feature. Tags: e-commerce, software-development.
- [Shopify to NetSuite Order Sync: Architecture That Survives Production](https://softwaresurvivor.com/blog/shopify-netsuite-order-sync-architecture) (2026-07-28): How to design a reliable Shopify-to-NetSuite order pipeline with durable ingestion, idempotency, failure classification, reconciliation, observability, and manual recovery. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity, reliability-is-a-feature. Tags: e-commerce, api.
- [Designing Reliable Shopify → NetSuite Refund Integrations](https://softwaresurvivor.com/blog/shopify-netsuite-refund-integration) (2026-07-28): Design Shopify-to-NetSuite refunds that track payments, accounting records, and inventory separately, so a failed update does not refund a customer twice. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, optimize-for-change, reliability-is-a-feature. Tags: e-commerce, api.
- [What a Fractional CTO Actually Does for a Growing Business](https://softwaresurvivor.com/blog/fractional-cto-growing-business) (2026-07-21): A practical explanation of fractional CTO work: technical strategy, vendor review, architecture decisions, hiring support, risk reduction, and delivery oversight. Type: leadership. Strategic status: supporting. Design principles: design-for-small-teams, architecture-should-compound. Tags: software-development, local-business.
- [GIS and Data Tools for California Water and Agriculture Teams](https://softwaresurvivor.com/blog/gis-data-tools-california-water-agriculture) (2026-07-14): How web-based GIS, shapefile tools, and operational dashboards can support California water agencies, agriculture teams, and local land management workflows. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity. Tags: data, web-development, local-business.
- [Candid Moments: Durable Media Processing and Moderation](https://softwaresurvivor.com/blog/candid-moments-durable-media-processing-moderation) (2026-07-07): How Candid Moments uses direct S3 uploads, durable PgBoss jobs, Rekognition, persisted state, and host controls to process event media safely. Type: case-study. Strategic status: flagship. Design principles: prefer-practical-simplicity, design-for-small-teams, reliability-is-a-feature. Tags: projects, cloud, ai.
- [How to Build a Safe AI Agent Around Business Data](https://softwaresurvivor.com/blog/build-safe-ai-agent-around-business-data) (2026-06-30): A practical architecture for AI agents that can read business data, draft actions, and stay inside controlled permission boundaries. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, prefer-practical-simplicity, reliability-is-a-feature. Tags: ai, software-development.
- [API Monitoring for Revenue-Critical Order Flows](https://softwaresurvivor.com/blog/api-monitoring-revenue-critical-order-flows) (2026-06-23): How to monitor order APIs, fulfillment integrations, payment flows, and background jobs before customers or finance discover the failure. Type: architecture. Strategic status: flagship. Design principles: reliability-is-a-feature, architecture-should-compound. Tags: api, automation.
- [A Practical Buy vs. Build Guide for Fresno Businesses](https://softwaresurvivor.com/blog/buy-vs-build-guide-fresno-businesses) (2026-06-16): How Central California businesses can decide when to buy software, customize an existing platform, or build a custom system. Type: architecture. Strategic status: supporting. Design principles: optimize-for-change, prefer-practical-simplicity. Tags: local-business, software-development.
- [Does Andy Grove's Management Model Still Work for Knowledge Teams?](https://softwaresurvivor.com/blog/does-andy-grove-management-model-still-work-knowledge-teams) (2026-06-16): Where Andy Grove's systems-oriented management model still helps modern knowledge teams, and where software leaders need a looser approach. Type: leadership. Strategic status: supporting. Design principles: optimize-for-the-next-engineer, design-for-small-teams, architecture-should-compound. Tags: software-development.
- [Performance, Feedback, and Accountability for Engineering Leaders](https://softwaresurvivor.com/blog/performance-feedback-accountability-engineering-leaders) (2026-06-14): Why engineering leaders need direct feedback, honest performance management, and clear accountability instead of management avoidance. Type: leadership. Strategic status: flagship. Design principles: optimize-for-the-next-engineer, architecture-should-compound. Tags: software-development.
- [Management Leverage for Software Leaders: What Andy Grove Still Gets Right](https://softwaresurvivor.com/blog/management-leverage-software-leaders-andy-grove) (2026-06-12): How software leaders can use Andy Grove's idea of management leverage to improve decisions, remove bottlenecks, and raise team output. Type: leadership. Strategic status: flagship. Design principles: optimize-for-the-next-engineer, design-for-small-teams, architecture-should-compound. Tags: software-development.
- [Legacy Software Modernization in the AI Era](https://softwaresurvivor.com/blog/legacy-software-modernization-ai-era) (2026-06-09): How AI changes the economics of legacy modernization, and why architecture, data ownership, and incremental migration still matter. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, optimize-for-change, prefer-practical-simplicity. Tags: software-development, ai.
- [From Inbox to Order: How Email-to-Order Automation Actually Works](https://softwaresurvivor.com/blog/from-inbox-to-order-email-to-order-automation) (2026-06-02): A practical look at email-to-order automation: parsing requests, validating products, handling missing information, and creating reliable orders from messy inbox data. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, reliability-is-a-feature. Tags: automation, e-commerce, projects.
- [AI Workflow Automation for Small Businesses: Where to Start](https://softwaresurvivor.com/blog/ai-workflow-automation-small-business-where-to-start) (2026-05-26): Choose a first AI workflow pilot by comparing simpler options, checking review effort, and defining evidence to continue, revise, or stop. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, prefer-practical-simplicity, reliability-is-a-feature. Tags: ai, automation.
- [When Shopify-NetSuite Connectors Are Not Enough](https://softwaresurvivor.com/blog/when-shopify-netsuite-connectors-are-not-enough) (2026-05-19): Decide whether to configure, extend, or replace a Shopify-NetSuite connector using business requirements, recovery needs, and operating costs. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, configuration-beats-code, reliability-is-a-feature. Tags: e-commerce, api.
- [Shopify to NetSuite Integration: What Breaks After the Connector Goes Live](https://softwaresurvivor.com/blog/shopify-to-netsuite-integration-what-breaks-after-connector-goes-live) (2026-05-12): Diagnose Shopify-to-NetSuite failures by tracing order evidence, separating rejected and uncertain writes, and choosing a safe recovery action. Type: architecture. Strategic status: flagship. Design principles: build-around-business-capabilities, optimize-for-change, reliability-is-a-feature. Tags: e-commerce, software-development.
- [Find Partially Fulfilled Sales Orders in NetSuite with SuiteQL](https://softwaresurvivor.com/blog/find-partially-fulfilled-sales-orders-netsuite-suiteql) (2026-05-04): Build a NetSuite SuiteQL report for partially fulfilled sales orders by calculating ordered, fulfilled, and pending quantities at the line-item level. Type: reference. Strategic status: supporting. Design principles: build-around-business-capabilities, reliability-is-a-feature. Tags: e-commerce, software-development.
- [Track NetSuite Item Fulfillments and Shipping Packages with SuiteQL](https://softwaresurvivor.com/blog/track-netsuite-item-fulfillments-shipping-packages-suiteql) (2026-05-03): Use SuiteQL to connect NetSuite item fulfillments back to sales orders, fulfillment lines, shipment packages, tracking numbers, and carrier metadata. Type: reference. Strategic status: supporting. Design principles: build-around-business-capabilities, reliability-is-a-feature. Tags: e-commerce, software-development.
- [Query NetSuite Sales Orders and Line Items with SuiteQL](https://softwaresurvivor.com/blog/query-netsuite-sales-orders-line-items-suiteql) (2026-05-02): Learn how to query NetSuite sales orders and line items with SuiteQL, including order number search, line joins, status labels, and pending fulfillment filters. Type: reference. Strategic status: supporting. Design principles: build-around-business-capabilities. Tags: e-commerce, software-development.
- [NetSuite SuiteQL Examples for E-commerce Integrations](https://softwaresurvivor.com/blog/netsuite-suiteql-examples-ecommerce-integrations) (2026-05-01): Practical NetSuite SuiteQL examples for sales orders, fulfillment tracking, pending items, inventory, and e-commerce integration workflows. Type: reference. Strategic status: flagship. Design principles: build-around-business-capabilities, reliability-is-a-feature. Tags: e-commerce, software-development.
- [CloudWatch Nginx Logs to CloudFront Log format](https://softwaresurvivor.com/blog/nginx-firehose-transform) (2025-12-10): A deep dive into transforming CloudWatch Nginx logs using a Lambda data transform that reduces multi-line batches into a single prioritized event for downstream HTTP ingestion. Type: reference. Strategic status: supporting. Design principles: prefer-practical-simplicity, reliability-is-a-feature. Tags: cloud, automation.
- [Building Inbox2Order: Human-Reviewed Email-to-Order Automation](https://softwaresurvivor.com/blog/building-inbox2order-email-to-order-automation) (2025-11-14): How Inbox2Order turns unstructured email requests into validated order drafts while keeping business-system writes under human control. Type: case-study. Strategic status: supporting. Design principles: build-around-business-capabilities, reliability-is-a-feature. Tags: projects, automation, e-commerce, ai.
- [Reading NetSuite Inventory Availability with SuiteQL](https://softwaresurvivor.com/blog/reading-netsuite-inventory-with-suiteql) (2025-11-02): Node.js helper to reading NetSuite inventory availability through the SuiteQL REST endpoint with a production-ready listIssueInventoryNumber helper. Type: reference. Strategic status: supporting. Design principles: build-around-business-capabilities, reliability-is-a-feature. Tags: e-commerce, software-development.
- [The Pitfalls of AI Vibe-Coded Projects in Production](https://softwaresurvivor.com/blog/ai-vibe-coded-project-pitfalls) (2025-10-09): Why "vibe-coded" AI experiments collapse under production pressure and how partnering with an experienced consultant keeps your launch on track. Type: architecture. Strategic status: supporting. Design principles: prefer-practical-simplicity, reliability-is-a-feature. Tags: ai, software-development.
- [Building Scalable and Reliable Systems: An Enterprise Architecture Guide](https://softwaresurvivor.com/blog/building-scalable-reliable-systems-enterprise-architecture-guide) (2025-09-05): A comprehensive guide to building scalable and reliable enterprise systems, covering load balancing, data management, caching strategies, and resilience patterns used by industry leaders like Netflix, Uber, and Google. Type: architecture. Strategic status: archive-candidate. Design principles: prefer-practical-simplicity, reliability-is-a-feature. Tags: software-development, local-business.
- [Legacy vs. Modern Systems: When to Modernize, Replace, or Leave It Alone](https://softwaresurvivor.com/blog/from-legacy-systems-to-modern-architecture-technical-migration-guide) (2025-09-01): A practical decision framework for determining whether a legacy system should be left alone, stabilized, incrementally modernized, or replaced. Type: architecture. Strategic status: supporting. Design principles: build-around-business-capabilities, optimize-for-change, prefer-practical-simplicity. Tags: software-development.
- [Tlaloc Harvest: Designing a Multi-Sided Food Redistribution Platform](https://softwaresurvivor.com/blog/introducing-tlaloc-harvest-community-food-waste-revolution) (2025-07-16): The product and architecture decisions behind a launch-ready platform foundation for coordinating surplus food, participants, partners, and logistics workflows. Type: case-study. Strategic status: supporting. Design principles: build-around-business-capabilities, optimize-for-change. Tags: projects, web-development.
- [From Text to Intelligence: My Fresno DevFest Keynote on Embeddings](https://softwaresurvivor.com/blog/fresno-devfest-embeddings-keynote) (2025-07-06): Expanded recap of my Fresno DevFest keynote using personal notes and slides to explore embeddings, vector databases, and AI-powered search. Type: speaking. Strategic status: flagship. Design principles: build-around-business-capabilities, prefer-practical-simplicity. Tags: ai, local-business.
- [The Growing Software Development Ecosystem in Fresno, CA](https://softwaresurvivor.com/blog/fresno-software-development-ecosystem) (2025-07-01): Exploring the emerging software development scene in Fresno, California, and how local businesses are leveraging technology to grow in the Central Valley. Type: architecture. Strategic status: archive-candidate. Design principles: build-around-business-capabilities. Tags: local-business, software-development.
- [On The Art Of Software Time Estimates](https://softwaresurvivor.com/blog/on-the-art-of-software-time-estimates) (2019-09-09): Estimate software work with explicit assumptions, summed effort ranges, and a delivery plan that accounts for dependencies and team availability. Type: leadership. Strategic status: supporting. Design principles: prefer-practical-simplicity, design-for-small-teams. Tags: software-development.
- [Create a HMAC Authorization Header in NodeJS](https://softwaresurvivor.com/blog/create-a-mac-authorization-header-in-nodejs) (2019-07-29): Complete guide to implementing HMAC authorization headers in Node.js for API authentication, including MAC string normalization and cryptographic verification techniques. Type: reference. Strategic status: supporting. Design principles: reliability-is-a-feature. Tags: api.
- [An AWS Code Build spec for your typescript node project](https://softwaresurvivor.com/blog/an-aws-code-build-spec-for-your-typescript-node-project) (2019-06-15): Complete guide to setting up AWS Code Build for TypeScript Node.js projects with buildspec.yml configuration for automated deployment to Elastic Beanstalk. Type: reference. Strategic status: archive-candidate. Design principles: optimize-for-the-next-engineer, prefer-practical-simplicity. Tags: software-development, cloud.
- [Woocommerce Multistep Product Variation Picker](https://softwaresurvivor.com/blog/woocommerce-multistep-product-variation-builder) (2018-10-22): A WooCommerce plugin for WordPress that enables a multistep product variation picker with file upload, area measurement pricing, and customizable options for enhanced customer experience. Type: case-study. Strategic status: archive-candidate. Design principles: configuration-beats-code, prefer-practical-simplicity. Tags: web-development, api, e-commerce.
- [A Scalable React Native Project Structure](https://softwaresurvivor.com/blog/a-scalable-react-native-project-structure) (2018-03-14): A comprehensive guide to organizing a scalable React Native project with feature-based folder structure, component organization, and navigation setup for mobile app development. Type: architecture. Strategic status: archive-candidate. Design principles: optimize-for-the-next-engineer. Tags: web-development.
- [GIS Shapefile Online Viewing & Editing (Sneak Peak)](https://softwaresurvivor.com/blog/gis-shapefile-online-editor) (2017-12-27): Development of an online GIS shapefile viewer and editor for SGMA Solutions, enabling users to view and edit compressed shapefiles directly in the browser with real-time boundary mapping capabilities. Type: case-study. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity. Tags: data, web-development.
- [Sigma Solutions - A Groundwater Management web app](https://softwaresurvivor.com/blog/sigma-solutions-ecoverse) (2017-09-14): Overview of Sigma Solutions, a groundwater management web application built to simplify SGMA compliance for California water agencies with interactive mapping and data management tools. Type: case-study. Strategic status: supporting. Design principles: build-around-business-capabilities, prefer-practical-simplicity. Tags: data, web-development.
- [Hello world!](https://softwaresurvivor.com/blog/hello-world-2) (2016-01-13): Introduction to my programming blog and personal journey in software development, from TI-83 calculator programming to full-stack development. Type: case-study. Strategic status: historical. Tags: projects.