DEV.to

精选 RSS · 科技

3 个榜单40分钟前更新默认榜单

DEV.to · 精选 RSS

40分钟前更新
  • 01
    Node.js Fintech Metrics Dashboard: StatsD-Style API Comparison for Incident Reconstruction
    TL;DR: Choose the dashboard shape by asking which evidence must survive an incident, not which chart looks cheapest on day one. For a Node.js fintech experiment split across tenant cohorts, keep operational counters separate from experiment events, attach a stable experiment revision and tenant pseudonym at collection time, and preserve enough raw evidence to recompute disputed aggregates. A StatsD-style API, Prometheus Pushgateway, Mixpanel dashboards, and Datadog can each occupy a boundary inEthanBrooks1647
  • 02
    Stop letting examples lie: make your OpenAPI spec the single source of truth for docs, mocks, and agents
    Every API team says the spec is the source of truth, then maintains five copies of what a response actually looks like: one in the docs, one in a mock server, one in a shared collection, one in test fixtures, and one in the prompt context given to an AI assistant. Within a quarter they disagree. The docs show a field the API no longer returns, the mock invents an envelope the real service never wraps in, and the agent confidently calls a shape that 404s. The fix is not better discipline around cJeff
  • 03
    REST API versioning in 2026: paths vs headers, additive changes, and OpenAPI diffs in CI
    Teams argue for weeks about where a version number should live and spend almost no time on the two questions that actually protect consumers: which changes are genuinely breaking, and how an old version is retired. A versioning strategy is really a change-management strategy with a routing convention on top. Get the change classification and deprecation path right and the choice between paths and headers becomes a minor operational preference. Where the version can live Four mechanisms show up iJeff
  • 04
    PicoCTF Wave a Flag Writeup — Read a Remote Binary's Help Output
    This introductory challenge teaches the most basic reflex in offensive security: read a program's help before using it. By connecting to the remote binary and typing ./flag --help , the flag is displayed directly. Platform: picoGym Category: General Skills / Misc Points: 50 pts Difficulty: Beginner Technique: Reading a program's help (--help) Challenge description The prompt provides a connection command to a remote shell: nc saturn.picoctf.net 54981 Once connected, we land in a minimal Linux enCTFDojo
  • 05
    Document API authentication in OpenAPI 3.1: Bearer, API keys, OAuth 2, and mTLS without the usual mistakes
    Authentication is the part of an API contract that consumers hit first and that documentation most often gets quietly wrong. A security scheme that is defined but never referenced, a bearer token modeled as an ordinary header, or OAuth scopes that do not match the authorization server all produce a spec that renders nicely and fails at first request. OpenAPI 3.1 gives you a precise vocabulary for the mechanisms in common use, including mutual TLS; the discipline is in applying it consistently. DJeff
  • 06
    Automating Weekly Multi‑Channel Drafts with a Node‑JS Content Generator
    Automating Weekly Multi‑Channel Drafts with a Node‑JS Content Generator TL;DR: I built a tiny Node script that pulls data from ClickUp, renders markdown templates, and drops ready‑to‑publish drafts into content/…/medium_*.md and substack_*.md . The change lets the repo self‑generate a weekly newsletter and platform‑specific articles on every push, cutting manual copy‑paste to zero. The Problem Every Monday I had to copy the same set of metrics (alerts, deadline breaches, Chromecast disconnect coRoberto Luna
  • 07
    Property-Based Tests Are the Guardrail Agents Need
    Originally published at tddbuddy.com . Related reading: Examples Pin Intent. Properties Pin the Invariants. named the two-axis specification; this post pins the specific role properties play as an agent guardrail. Tamper-Resistant Test Design Is What the Suite Now Owes the Codebase and The Contract Test Is the Only Witness the Agent Cannot Author are the companion defenses at the test and seam layers. An example test the agent can read is an example the agent can hardcode past. That mechanism isTravis Frisinger
  • 08
    Reusable JSON Schema components in OpenAPI: DRY models without $ref spaghetti
    The first OpenAPI document most teams write inlines every request and response schema next to its operation. It is fast to start and painful by month three: the same customer object is shaped three different ways across create, retrieve, and update, and fixing a field means hunting through dozens of paths. The second document over-corrects and extracts every trivial shape into components , producing a maze where reading one operation requires chasing ten references. Good component design sits beJeff
  • 09
    AST vs AI for reverse-engineering OpenAPI: where static analysis stops and the model earns its place
    Two pitches dominate the "generate API docs from code" space. One says "point an LLM at the repo, it will understand everything." The other says "static analysis is deterministic, just parse the files." Both fail on real backends, for opposite reasons. The designs that actually hold up in production use a strict division of labor: static analysis owns the closed world of routes and types, and the model is allowed to touch only the narrow pieces that static analysis can prove it cannot know. WhyJeff
  • 10
    Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass Submission 🌿
    Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass Submission 🌿 Trailhead: a hiking planner that works where the internet doesn't Two months ago I stood at a trailhead with one bar of signal, a dead cloud-AI app spinning on "thinking…", and a paper map I couldn't read in the wind. The chatbot that happily plans my week in the city is a brick exactly where I need it most: outside. So for Week 1 I built Trailhead — a hiking trip planner that runs a real open-weight model entirely on your oMuse
  • 11
    Generate OpenAPI from FastAPI and Django REST without decorating every view
    Python backends split into two schema philosophies. FastAPI puts the contract next to the handler, in type annotations and model classes, so a lot of the OpenAPI document is already written in a form a parser can read. Django REST Framework (DRF) puts the contract in Serializer classes and ViewSet actions, which is expressive but considerably more dynamic. A code-to-OpenAPI scanner has to handle both honestly: recover everything that is statically provable, and mark the genuinely runtime parts aJeff
  • 12
    Generate OpenAPI from Express and NestJS code without writing annotations by hand
    Node teams usually reach a spec in one of two painful ways: they hand-write OpenAPI and watch it drift from the code, or they decorate every handler and watch the decorators drift from the actual types. Both treat the document as a second thing to maintain. There is a third path: treat the running framework code as the source of truth, prove what it does statically, and reverse-engineer a validated OpenAPI 3.2 document from it. The difference between a scanner that works on real Express and NestJeff
共 12 条热搜查看完整榜单

DEV.to · 今日热门

42分钟前更新
共 50 条热搜查看完整榜单

DEV.to · 最新发布

38分钟前更新
共 50 条热搜查看完整榜单
DEV.to热榜 | 什么火了