Putting a separate judge in front of an LLM-based CV screener: Laravel Judgment asks Jev whether a CV contains instructions aimed at the machine, and the application decides what to do with the answer.
How to let a model assess free-text refund requests with Laravel Judgment while the application keeps the decision, first on the hosted Jev and then on a self-hosted Laya server.
How a line of hidden text in a CV can steer an LLM-based screener, and the countermeasures from LLM Application Engineering that limit it: separate instructions, checks before and after the call, least privilege and approval gates.
PHP 8.1 introduced the new Fiber class (see the proposed RFC here https://wiki.php.net/rfc/fiber), which allows running coroutines inside your script, i.e. two functions executing simultaneously
This article describes a way of implementing Strategy design pattern using a database-based runtime configuration. The approach allows to dynamically (re)configure class behavior without requiring code-based rearrangements.
Classes with a lot of lines of code are generally bad. Too many responsibilities, low cohesion, or both. However, sometimes it is not possible to make functions smaller. Reasons could be various. What can be done in this circumstance?
Very often you find yourself in situations where you need to make your data pass some kind of checks or filters before doing something with them. This post shows how to make a first attempt approach better and cleaner