Tagged articles
Spec
16 articles · Page 1 of 1
This article details the six core artifacts of AI-Native SDLC—Intent, Spec, Plan, Task, Eval, and Evidence—explaining their design principles, versioning, lineage, and how they form a verifiable chain that replaces traditional documentation with machine-readable engineering objects to ensure Agent accountability and automated governance.
AI-Native SDLCAgent GovernanceEval
0 likes · 41 min read

The article argues that traditional PRDs are obsolete because AI now consumes requirements; it introduces SPEC — precise, boundary-locked specs for AI — and shows how Spec Coding lets product managers handle five requirements in one morning, shifting PM value from document writing to strategic judgment.
AI workflowAI-assisted developmentPRD
0 likes · 15 min read

The article explains how PRD, design documents, and SPEC each answer distinct questions—what, why, and how—while outlining their constraints, typical structures, real‑world examples, when to use or skip them, and how they fit into a seamless development pipeline.
AI agentsDesign DocumentPRD
0 likes · 22 min read

Although teams now have powerful models like GPT, Claude, Gemini, and DeepSeek, AI project efficiency often stalls because teams still manage AI like human programmers, lacking clear constraints and governance; OpenAI's Harness Engineering addresses this by defining specs, evaluations, guards, and traces to make AI agents reliable, auditable, and safely autonomous.
AI agentsAI governanceEvals
0 likes · 9 min read

An in‑depth look at the long‑standing contradiction in the Go spec that labeled the predeclared bool type as a defined type, the heated community debate it sparked, Robert Griesemer’s personal apology, the historical reasons behind the mistake, and the practical impact on generics, method sets, and API design.
GenericsGoSpec
0 likes · 10 min read

The article critically examines the hype around Agentic Coding by showing that detailed specifications are essentially code, using OpenAI’s Symphony as a case study, and demonstrates that spec‑driven generation is unstable, error‑prone, and often no faster than writing code directly.
AIAgentic CodingSpec
0 likes · 14 min read

The article examines Go’s claim of eradicating undefined behavior, showing that while the language defines many formerly UB cases such as integer overflow and out‑of‑bounds access, it still harbors UB in concurrent data races, interface type confusion, and certain unspecified behaviors.
ConcurrencyData RaceGo
0 likes · 18 min read

The article contrasts the chaotic, prompt‑driven "Vibe coding" approach with Kiro's Spec‑driven development, explaining how a two‑session model—Vibe for creative exploration and Spec for deterministic engineering—structures AI projects from project‑level documentation to runtime execution, improving reliability and traceability.
AI EngineeringKiroRunner
0 likes · 10 min read

This article explains the concept of data‑center compute power, reviews mature evaluation methods such as TOP500/FLOPS for supercomputers and SPEC CPU, SPECpower, and MLPerf for conventional servers, introduces the PUE efficiency metric, and summarizes the four core components that together define a data‑center's computing capability.
Compute powerHPCMLPerf
0 likes · 9 min read

This article reviews the evolution of mainstream CPU performance benchmarks such as SPEC and TPC, compares their methodologies and tools, discusses challenges in evaluating heterogeneous CPUs, and outlines future research directions, providing a comprehensive overview for researchers and practitioners.
CPUSpecTPC
0 likes · 10 min read

The article explains Docker's new cross‑platform Compose specification, highlights its concise syntax and cloud‑native benefits over Kubernetes, showcases example configurations, and describes related open‑source projects and Lingque Cloud's contributions to the spec development.
Docker ComposeKubernetesSpec
0 likes · 5 min read

The OAM v1alpha2 specification, released after three months of iteration, introduces a more Kubernetes‑friendly reference model, replaces ComponentSchematic with Component, embeds full CRDs for workloads and traits, adopts jsonPath for parameter injection, removes variables and consolidates core workloads into a ContainerizedWorkload, while clarifying Scope handling and outlining upcoming enhancements.
Application ConfigurationCRDKubernetes
0 likes · 16 min read

The article explains the origins, metrics, and test suites of TPC and SPEC benchmarks, describes their various models for CPU, web, HPC and storage performance, shows how to query official results, and notes a promotional bundle of technical e‑books.
CPUOperationsSpec
0 likes · 9 min read

The article explains the origins, purpose, and key test models of the TPC and SPEC benchmark suites, describes how they assess server CPU, web, and storage performance, and outlines methods for querying official SPEC results, highlighting their relevance for enterprise system procurement.
Hardware EvaluationSpecTPC
0 likes · 11 min read

The article summarizes the SPEC 2016 Asian Summit, explains SPEC's role in defining server and cloud performance benchmarks—including CPU, web, and file‑system tests—and highlights the introduction of the SPEC Cloud IaaS 2016 benchmark for evaluating cloud infrastructure performance.
CPU performanceSpecbenchmark
0 likes · 7 min read

The article presents an interview with SPEC chairman Walter Bays at the 2016 SPEC Asia Summit in Beijing, discussing SPEC’s role, its benchmark standards, the organization’s focus on China, and the introduction of cloud‑IaaS and big‑data performance benchmarks for future computing needs.
Asia SummitSpecbenchmarking
0 likes · 6 min read
