AmanERP
मुफ़्त अर्ली एक्सेस पाएं

इंजीनियरिंग

इंजीनियरिंग

AI-native software, verification, audit trails और public rigor पर AmanERP की engineering notes।

  • A horizontal timeline with four marks — a license flipping upstream, the dependency adopted, the audit that catches it, and a wide migration span — showing the cost of the unasked license question.

    OPEN SOURCE LICENSING

    The AGPL Trap That Forced an Identity Provider Migration

    Why AGPL license risk forced a six-week identity-provider migration: the Go static-linking trap, the two-axis license matrix, and the rule that keeps product code safe.

    5 मिनट पढ़ें

  • A dark editorial control room interface where structured prompt cards route work through clear engineering gates.

    AI ENGINEERING

    Prompting Is a Control Plane, Not a Vibe

    Treat prompts as an engineering control plane: scope the task, point to sources, name checks, state constraints, and make evidence mandatory.

    5 मिनट पढ़ें

  • A precise blueprint table showing scope, acceptance criteria, and definition of done before any code is written.

    SPEC DISCIPLINE

    Spec Before Speed: The Cheapest Place to Catch Scope

    Before an AI agent writes code, make the ticket engineering-ready: objective, boundaries, acceptance criteria, definition of done, and deliverables.

    5 मिनट पढ़ें

  • A top-down coordination board with four agent lanes, file ownership boundaries, and a supervisor lane preventing collisions.

    AGENT ORCHESTRATION

    Parallel Agents Need Air-Traffic Control

    Parallel AI engineering needs sequencing, file ownership, a concurrency ceiling, and supervisor discipline before it needs more agents.

    6 मिनट पढ़ें

  • A verification console where command output, exit codes, and screenshots are pinned above a blocked completion stamp.

    VERIFICATION

    Evidence Beats Assertion in AI Engineering

    AI agents should report commands, outputs, exit codes, and screenshots, not confidence. Verification is a contract, not a mood.

    5 मिनट पढ़ें

  • Two independent review panels compare a pull request, highlighting production risks before the merge path opens.

    CODE REVIEW

    The Adversarial Review Loop That Keeps AI Useful

    A useful AI review loop separates planning, adversarial critique, implementation, branch review, and only the high-confidence fixes.

    6 मिनट पढ़ें

  • A root-cause investigation board showing logs, hypotheses, a failing reproduction, and the confirmed cause converging into one fix.

    DEBUGGING

    Debugging Starts After the First Counterexample

    Disciplined AI debugging starts with evidence, ranked hypotheses, a reproduction, and a root-cause fix rather than patching the symptom.

    5 मिनट पढ़ें

  • A test dashboard where one meaningful red assertion blocks a row of shallow green checks.

    SOFTWARE TESTING

    Tests Must Be Able to Fail for the Right Reason

    Useful AI-generated tests assert behavior, cover acceptance criteria, avoid fake mocks, and prove they can fail for the right reason.

    5 मिनट पढ़ें

  • A context window meter allocates limited space to decisions, changed files, tests, and next actions while noisy transcripts fade out.

    CONTEXT HYGIENE

    Context Is a Budget, Not a Backpack

    Treat context as a finite operating budget: offload broad investigation, write handoffs, preserve decisions, and restart before drift becomes rework.

    4 मिनट पढ़ें

  • A pull request review surface with exact staged files, risk notes, rollback notes, and distinct gate status rows.

    PR HYGIENE

    Clean PRs Are an Engineering Interface

    AI-written code still needs human-reviewable commits and PRs: exact staged scope, clear intent, risk, rollback, and distinct gate status.

    4 मिनट पढ़ें

  • A product screen audit board marking hierarchy, spacing, states, and missing workflow cues as operational defects.

    ENTERPRISE UX

    Premium UX Review Is Not Taste, It Is Operations

    Premium UX critique should inspect workflow, hierarchy, state coverage, interaction, copy, and information availability, not generic styling opinions.

    5 मिनट पढ़ें

  • Two terminal panels describing one server — a health endpoint returning status ok beside a psql \dt output reading "Did not find any relations."

    RELIABILITY ENGINEERING

    Your Server Said 'Healthy.' The Database Had Zero Tables.

    A database connection proves TCP and auth, not that the schema exists. The silent empty-database failure, and the one health-check that actually catches it.

    2 मिनट पढ़ें

  • A three-row matrix showing unit tests, mock acceptance tests, and integration tests, each with a column of what it proves and a column of what it cannot see — the cannot-see cells lining up into a single visible gap.

    SOFTWARE TESTING

    181 Tests Passed. Zero Features Worked.

    181 tests passed while the app had zero tables, dead metrics, and broken auth. What mock-only tests prove, what they miss, and the layer that closes the gap.

    6 मिनट पढ़ें

  • A minimal terminal card showing a pathspec git commit stopped by a pre-commit check reporting unstaged lines.

    AI-NATIVE VERIFICATION

    git commit -- file.go Doesn't Limit Scope. It Does the Opposite.

    git commit pathspec re-stages the file's whole working tree. With parallel AI agents sharing one git index, that means ghost commits. Here's the fix.

    6 मिनट पढ़ें

  • A minimal terminal card showing a mutation report: 100.0000% effective efficacy directly above mutants_killed = 0 and mutants_timed_out = 603, the contradiction carried by the numbers alone.

    AI-NATIVE VERIFICATION

    100% Mutation Efficacy, Zero Mutants Killed: A Gate That Asserts Nothing

    A mutation-testing gate reported 100% efficacy with 0 mutants killed — all 603 were timeouts. A gate that asserts nothing scores perfectly. Why filed ≠ solved.

    6 मिनट पढ़ें

  • A structured drill receipt with its recovery-time row blank, a ghosted zero being stamped into the gap beneath a green pass verdict.

    ENGINEERING DISCIPLINE

    Schema-Aware Gates: Validate, Don't Coerce

    Schema-aware gates should validate and fail closed. Defaulting missing fields to zero turns a correctness gate into false evidence.

    6 मिनट पढ़ें

  • A rejected one-page proposal ending in a four-item revisit-if checklist, three boxes ticked, with the rejected reasoning preserved at the fork of an untaken path.

    ARCHITECTURE DECISIONS

    RFC Before ADR: The 'Maybe' Layer That Saves Bad Decisions

    An RFC layer between idea and ADR records rejected options, open questions, and constraint tradeoffs before decisions become permanent.

    7 मिनट पढ़ें

मालिकों, ऑपरेशंस प्रमुखों और उनके अकाउंटेंट्स के लिए लेख: ब्लॉग पढ़ें