Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 203
  1. The Petstore scores 65

    The most copied OpenAPI document in the world is a bad API for an agent, and it takes a third of a second to find out.

  2. Your endpoint, as an agent sees it

    An agent never reads your API.

  3. From 2029 every UK VAT invoice has to be structured data that passes about eleven hundred rules.

  4. The PHP Foundation made the case for funding upstream maintenance through procurement.

  5. The Second Pattern: The Ones I Left Out

    Five patterns I know well, that come up constantly, and would not reach for in PHP.

  6. The Second Pattern: Blackboard

    A pipeline works until one step both needs and improves the same piece of information.

  7. The Second Pattern: Event-Carried State Transfer

    A consumer that receives an ID and immediately asks you for the record has not been decoupled from you.

  8. The Second Pattern: Process Manager

    Everyone calls it a Saga.

  9. Designing CLIs people want to use

    API design is a user experience problem and nobody argues any more.

  10. The Second Pattern: Bulkhead

    Carrier B did not go down, it got slow, and every worker sat inside an eleven second call that returned a valid 200.

  11. The Second Pattern: Claim Check

    A payload that is 40KB almost always and 12MB occasionally cannot be sized for.

  12. The Second Pattern: Idempotent Receiver

    Select then insert handles the easy half of duplicate delivery and misses the concurrent case, which is the half that actually fires.

  13. The Second Pattern: Transactional Outbox

    Commit then notify loses messages.

  14. The Second Pattern: Anti-Corruption Layer

    Carrier B speaks GraphQL, so the response arrives shaped like your query and feels like it belongs to you.

  15. The Second Pattern: Specification

    Nine optional parameters is the symptom.

  16. Your Test Suite Is an Architecture Report

    A slow Laravel test suite gets treated as a tooling problem.

  17. The Rewrite You Should Not Do

    You have run the diagnostics and you have a list.

  18. The Job And The Controller Disagree

    The same operation runs from two entry points and they have quietly drifted.

  19. The Interface With One Implementation

    You added it so the thing could be swapped out later.

  20. Nobody Wants To Touch That Model

    Every Laravel codebase has a model people route around.

  21. It Was Fine Until We Added A Second One

    Every trigger in this series has been a second something.

  22. Every Feature Touches Ten Files

    Ten files open for a one line change is either layering working correctly or one idea smeared across a codebase.

  23. Building Research

    A desktop research workspace in Laravel and NativePHP.

  24. [Automatically generated using robots and AI, accuracy may not be 100%] Two weeks of Laravel 13: a read-through filesystem driver for zero-downtime storage migrations, a global queue pause switch, debounced listeners, and Redis cluster fixes worth upgradi…

  25. Accepting Data You Don't Control

    Webhooks and callbacks you did not design.

  26. Specs, ADRs and path-scoped rules.

  27. The Obsidian vault I use as a system of record for every project, why the checkouts inside it are gitignored, and why half of it is generated from my NixOS flake.

  28. The Streamable HTTP transport replaced HTTP+SSE and quietly made MCP servers stateless.

  29. How auto-imported flake-parts modules, wrapped desktop packages, and a single base16 palette file shape one NixOS config - and where each one bites.

  30. Seven Days in Ten Milliseconds

    A workflow that sleeps for three days is not a workflow you can test by waiting.

  31. Building an order fulfilment workflow in Laravel

    Build a real order fulfilment workflow in Laravel: signals from webhooks, timeouts, retries, branching, sleep and saga compensation, one step at a time.

  32. Strangling Procedural Legacy PHP into Laravel

    Replace a procedural PHP monolith with Laravel one route at a time.

  33. Stop letting undocumented fields into your Laravel API.

  34. The Laravel AI SDK is provider-agnostic, but its built-in web tools aren't.

  35. The Right Agent at the Right Time

    How to run AI across the whole dev lifecycle: the right agent at each stage, human gates on judgement, and decision records that keep architecture honest.

  36. Fibers give PHP concurrency.

  37. A Proper Look at Tabstack

    A developer's review of Tabstack, the Mozilla-backed web API that gives AI agents clean extraction, browser automation, and cited research without a scraper.

  38. The Polling API gives PHP 8.6 native epoll and kqueue at last.

  39. A hands-on look at Mozilla's tabstack CLI: a single Go binary that turns any URL into clean Markdown or JSON, runs browser automation, and scripts neatly.

  40. Practical tips for building Laravel APIs developers trust: contract-first design, versioning, RFC 9457 errors, idempotency and more.

  41. Testing Actions, Not Mocks

    Mocking your own Actions tests the wiring, not the behaviour.

  42. Meet Sevalla; Cloud Hosting Without the Headache

    Sevalla simplifies cloud hosting by providing intuitive app deployment, database hosting, and object storage.

  43. Learn how to build device-based rate limiting in Laravel with Fingerprint.dev, Redis caching, and custom middleware to avoid the limits of IP-based throttling.

  44. The Reason I Love Tempest for APIs

    Tempest makes API development feel lightweight by combining typed request objects, attribute-based validation, discovery-driven routing, and built-in mapping with minimal ceremony.

  45. The Art Of Keeping Business Logic Honest

    Use state machines and workflow engines in Laravel to keep business rules explicit, auditable, and resilient across async processes.

  46. Your First ERD

    Map entities and relationships before you write migrations so your schema starts on solid ground.

  47. Writing Features Not Tasks

    Turn vague tasks into user-focused features with clearer outcomes and better stories.

  48. Thinking In Layers

    Use layered thinking to place logic in the right part of your application before it turns into a mess.

  49. The Mid-Level Mindset

    A practical mindset shift for turning thinking-first habits into mid-level engineering judgment.

  50. Stop Writing Code First

    Think through requirements, assumptions, and structure before you open your editor.