Pigfox

Blog

Field notes on OSINT, security checks, SEO, and safer hiring and vendor due diligence.

  • Using Go 1.25 Flight Recorder in Production

    2026-08-12

    Go 1.25’s flight recorder changes production tracing from a reactive tool into a rolling source of pre-incident evidence. Here is how to use it to inspect scheduler pressure, contention, GC assist work, and short-lived failures in Go services and blockchain infrastructure.

  • What Green Tea GC Means for Production Go Systems

    2026-08-11

    Go’s upcoming Green Tea garbage collector is a prompt to recheck how your Go services allocate, scan, and schedule work. For blockchain and AI systems, the wins depend less on hype and more on allocation rate, pointer density, and disciplined upgrade testing.

  • How to evaluate Go 1.26 in production systems

    2026-08-08

    Go 1.26 matters most in the runtime, toolchain, and dependency edges it changes under your production workloads. This article lays out a practical upgrade plan for teams running AI and blockchain services in Go.

  • Modernizing Go Code with Mechanical Fixes

    2026-08-07

    Go modernization works best as an engineering workflow, not a cleanup sprint. Use toolchain-aware rewrites, verify behavior with tests and benchmarks, and extend the same approach to your own internal APIs.

  • Go stack allocation, escape analysis, and hot-path design

    2026-08-06

    Go performance often turns on one compiler decision: stack or heap. This article shows how to inspect escape analysis, verify allocation behavior with benchmarks and profiles, and shape Go APIs to keep hot-path data off the heap.

  • What Go’s source-level inliner changes for hot paths

    2026-08-05

    Go’s new source-level inliner changes how you approach performance work in hot Go paths. The win is not the missing call itself, it is the compiler visibility you gain across the boundary, and the maintenance cost you take on in return.

  • Go Type Cycles and What They Mean for System Design

    2026-08-04

    Go’s rules for recursive types shape more than compilation. They affect memory layout, encoding, and data-model design in production systems such as blockchain clients and AI services.

  • Using the pkg.go.dev API in Go dependency review

    2026-08-03

    The pkg.go.dev API gives Go teams a stable way to pull package metadata into CI, dependency review, and SBOM workflows. The value comes from using it for module identity, license checks, and review triggers, then joining it with native Go tooling.

  • How I Vet Job Outreach as an Infrastructure Problem

    2026-08-02

    A job message is easier to judge when you treat it as infrastructure instead of copy. These field notes map the technical and process signals worth checking across email, domains, documents, and hiring workflows.

  • Verify-first signals in recruiter and job-offer workflows

    2026-08-01

    A safer hiring workflow starts by checking infrastructure, documents, and sequence, not just the wording of a recruiter message. These field notes focus on the technical and operational signals that help practitioners verify outreach before trust is extended.