- You can store a price in a floating point variable.
- All currencies are subdivided in 1/100th units (like US dollar/cents, euro/eurocents etc.).
- All currencies are subdivided in decimal units (like dinar/fils)
- All currencies currently in circulation are subdivided in decimal units. (to exclude shillings, pennies) (counter-example: MGA)
- All currencies are subdivided. (counter-examples: KRW, COP, JPY... Or subdivisions can be deprecated.)
- Prices can't have more precision than the smaller sub-unit of the currency. (e.g. gas prices)
- For any currency you can have a price of 1. (ZWL)
- Every country has its own currency. (EUR is the best example, but also Franc CFA, etc.)
| server { | |
| # Server name | |
| server_name example.com; | |
| # Server Port | |
| listen 80; | |
| # Webroot | |
| root /var/www/; |
| <?php | |
| namespace YourApp\Repository\Query; | |
| use Doctrine\DBAL\Connection; | |
| use Doctrine\DBAL\Schema\Identifier; | |
| /** | |
| * Class BulkInsertQuery | |
| * |
WordPress is popular because it's easy to setup without much technical know-how. However, to build a more robust PHP project with command line deployments, updates and ongoing maintenance, working with WordPress out-of-the-box raises specific challenges:
- How can we make our WordPress projects portable between developers?
/!\ Be very carrefull in your setup : any misconfiguration make all the git config to fail silently ! Go trought this guide step by step and it should be fine 😉
- Generate your SSH keys as per your git provider documentation.
- Add each public SSH keys to your git providers acounts.
- In your
~/.ssh/config, set each ssh key for each repository as in this exemple:
| # Make sure to modify "-Xms", "Xmx", "CICompilerCount", and "ParallelGCThreads" according to your PC hardware configuration... | |
| # ------------------------------------------- | |
| # Memory Settings (High-Memory Workstation) | |
| # ------------------------------------------- | |
| # Set the initial heap size (this reduces resizing overhead) | |
| -Xms2048m | |
| # Set the maximum heap size (adjust depending on your system; 2048m or 4096m is good for modern machines) |
Date: 2026-01-25 Analysis: Side-by-side comparison of Claude Flow V3 swarm architecture (developed by rUv) and Claude Code's TeammateTool (discovered in v2.1.19)
A detailed analysis reveals striking architectural similarities between Claude Flow V3's swarm system and Claude Code's TeammateTool. The terminology differs, but the core concepts, data structures, and workflows are nearly identical.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.