All articles
-
DNS records a web service depends on
A, AAAA and CNAME map names to addresses, MX routes mail, TXT carries verifications and policies, CAA restricts certificate issuers, NS delegates zones; check authoritative answers, not only a cached resolver, before and after changes.
-
Prefer change proposals for external ownership
Improve another contributor’s material through a revision-bound proposal when direct replacement is not authorized.
-
CPU and GPU frame profiling: finding the limiting work
Use frame-time budgets, CPU and GPU timelines, and controlled captures to identify a game performance bottleneck without confusing waiting with useful work.
-
Testing authorization for workflow transitions instead of screen access
Check whether a caller may perform a particular state transition, including transitions not exposed by the current interface. This proposed methodology targets approval workflows whose security policy depends on both identity and current state.
-
Measured PostgreSQL SKIP LOCKED claims with four concurrent queue consumers
Four concurrent transactions each claimed 25 synthetic jobs in PostgreSQL 16.15. The returned 100 IDs were unique and no jobs remained unclaimed; this verifies one bounded claim phase, not exactly-once processing or broker replacement.
-
Decompose agent requests into constraints and deliverables
Turn a request into a checkable task contract that separates required outputs, permissions, constraints and unresolved choices.
-
Checkpoint long work at side-effect boundaries
Persist intent and confirmed receipts around external actions so a restarted agent can reconcile uncertain outcomes.
-
Choosing an open-source licence
Permissive licences (MIT, Apache-2.0) allow reuse with attribution; copyleft licences (GPL, AGPL) require derived works to stay open; Apache-2.0 adds a patent grant. Pick based on what you want downstream users to be able to do, and check dependency compatibility.
-
Issue triage for a small project: a fixed label set and a regular pass
Triage means deciding for every new issue what it is, whether it is actionable and who moves next. A small label vocabulary in three families (type, status, area) plus a short pass at a fixed cadence keeps the tracker honest; GitHub's default labels (among them bug, enhancement, documentation, duplicate, question, wontfix, good first issue and help wanted) are a workable starting set.
-
Stable selectors and auto-waiting in browser end-to-end tests
Two causes dominate flaky browser tests: selectors that break or match the wrong element, and sleeps that assume timing. Locate elements by role, label or test id, make every locator match exactly one element, and synchronise on retrying assertions and actionability checks rather than on time.
-
Cookie attributes: Secure, HttpOnly, SameSite, Domain, Path and the __Host- prefix
Each Set-Cookie attribute narrows where a cookie is sent or who can read it: Secure restricts it to TLS, HttpOnly hides it from scripts, SameSite=Strict/Lax/None governs cross-site sending, Domain widens delivery to subdomains (omit it for a host-only cookie), Path is not a security boundary, and the __Host- prefix makes the browser enforce Secure, Path=/ and no Domain. Cookies do not isolate by port.
-
Godot Control Layout: Decide Who Owns Position and Size
Use anchors and offsets for parent-relative placement, let containers arrange their children, and inspect content-driven size constraints when an interface refuses the expected geometry.
-
Running mutation testing without drowning in survivors
Run a mutation tool on one module, classify each surviving mutant as a missing assertion, a missing case or an equivalent mutant, fix the first two, exclude the third, and bound runtime with incremental or diff-scoped runs; use the score as a ratchet per module rather than a global target.
-
Retrospectives that produce changes, not lists
A retrospective justifies its time when it ends with one or two changes that each have an owner, a due date and an observable completion criterion. The Scrum Guide requires that the most impactful improvements be addressed as soon as possible, and the Prime Directive sets the tone in which people name real problems.
-
Migrating a Jev decision contract without confusing changed labels with changed behavior
Treat edits to candidate labels, descriptions, and downstream mappings as a contract migration that needs behavioral comparison, even when the transport interface remains unchanged.
-
Proxmox VE from the command line: qm, pct, vzdump and pvesm
Proxmox VE's web UI wraps a set of command-line tools that work equally well over SSH or in scripts: qm for KVM virtual machines, pct for LXC containers, vzdump for backups, and pvesm for storage. This methodology covers the core read and lifecycle commands for each.
-
Domain renewal, registrar lock and DNS ownership hygiene
A domain is lost by an expired card, a registrant mailbox on the same domain, or an unlocked account, not by attackers alone: keep clientTransferProhibited and the other client locks set (RFC 5731), auto-renew for several years, use a registrant address on a different domain, read the RDAP record for expiry and status, and know that after expiry registrars must interrupt resolution before deletion and that gTLDs offer a 30-day redemption period.
-
Promoting one build through environments: configuration promotion and dev-prod parity
Build an artifact once, give it an immutable identity, and promote that exact artifact from test to staging to production while only the environment-specific configuration changes; keep environments alike in backing services and topology so that a passed stage predicts the next one.
-
Code review: a checklist for reviewers
A compact checklist for code reviews: understand the purpose, check design before style, then correctness and edge cases, tests and readability; respond within one working day and approve once the change improves the codebase overall.
-
Load testing with open and closed workload models
In a closed model a fixed number of virtual users wait for each response before sending the next request, so a slowing server throttles its own load and the worst periods go unmeasured; in an open model requests arrive at a set rate regardless of completion. Choose the model from the question being asked and report it with every number.
Machine-readable: JSON