Search
Results for “backend-engineering”
- software-engineering
9-Step Rollback-Ready Release Checklist for Small Engineering Teams
Turn release management into a repeatable, executable checklist with test evidence, named approvers, deployment ownership, measurable rollback triggers, and post-release verification.
- software-engineering
How to Investigate Node.js Latency With Event-Loop Metrics, Not CPU Alone
Learn to distinguish a blocked Node.js event loop from slow downstream I/O using event-loop delay, event-loop utilization, request timing, and CPU measurements. Includes instrumentation code, a diagnosis matrix, and concrete remediation decisions.
- software-engineering
GitHub Releases vs Git Tags: A Practical Workflow for Prereleases and Latest Releases
A Git tag, a GitHub prerelease, and the Latest badge answer three different questions. Use this release engineering workflow to decide when to tag a commit, publish a prerelease, promote stable builds, and explain why tag and release dates differ.
- software-engineering
A Practical Checklist for Publishing Tamper-Resistant GitHub Releases with Immutable Tags and Assets
Separate temporary CI artifacts from the files users download, then publish a GitHub release whose assets and associated Git tag cannot be changed afterward. This checklist covers build promotion, checksums, release workflows, and the operational tradeoffs of immutability.
- software-engineering
A Pre-Launch GenAI Risk Checklist for Internal Chatbots and Developer Tools
Turn NIST’s generative AI risk guidance into a practical release gate for a coding assistant, repository chatbot, or internal support bot. Use this checklist to test data exposure, harmful outputs, human review, evaluation coverage, and incident response before enabling real users.
- software-engineering
GitHub Protected Tags vs Immutable Releases: How to Design a Release Process That Protects Both
A protected tag can stop a version name from being moved, while an immutable release protects the published package and its associated tag after publication. Learn where each control begins and ends, and how to combine them in a practical GitHub release workflow.
- technology
Migrate download-artifact to v4: Test Paths, Compatibility, and Deploy Contracts
A practical before-and-after migration for GitHub Actions artifact workflows. Learn how v4 changes artifact compatibility, availability, and download directories—and add checks that catch broken deploy paths before production.
- software-engineering
GitHub Changelog Triage: A Weekly Workflow for Releases, Improvements, and Retirements
Turn GitHub product changes into a 30-minute weekly operating process. Learn how to subscribe, classify releases, improvements, and retirements, assign accountable owners, run proportionate tests, and preserve decisions in a searchable log.
- software-engineering
Build Once, Publish GitHub Release Assets, and Verify the Download in GitHub Actions
Turn a tagged build into a reproducible GitHub Release: upload one immutable build bundle as a workflow artifact, attach that exact bundle to the release, then download and checksum the published asset as a consumer would.
- software-engineering
Migrate GitHub Protected Tags to Rulesets: Checklist, API Replacement, and Tag Target Verification
GitHub’s legacy tag-protection rules were migrated to tag rulesets after scheduled API brownouts in 2024. Use this checklist to translate patterns and permissions, create or audit repository rulesets through the supported path, and verify that release tags still point to the intended commits.
- software-engineering
A Practical Scorecard for Measuring Open-Source Dependency Reuse
As dependency reuse grows, a package list is not enough. This engineering scorecard turns inventory, update cadence, provenance review, and abandoned-package exposure into measurable controls that teams can use in planning and release reviews.
- software-engineering
CI/CD Security Tools in 2026: A Minimal Stack for GitHub Actions Without Overlapping Scanners
Build CI/CD security around the pipeline controls that matter: source, dependencies, secrets, workflow behavior, artifacts, and deployment. Compare practical tools for each control and choose a lean GitHub Actions stack for a small project or a growing engineering organization.