This paper proposes a new structural pattern for software development designed to address the challenges posed by the increasing use of Large Language Models (LLMs) in coding. The core idea is to build **"legible" software** – code that has a direct and clear relationship between its structure and its observable behavior.
The theory centers around two key elements:
* **Concepts:** These are independent, user-facing units of functionality with well-defined purposes (like "Post," "Comment," or "Upvote"). They act as self-contained services.
* **Synchronizations:** These are granular, event-based rules that mediate interactions *between* concepts. They orchestrate data and control flow *without* creating direct dependencies between the concepts themselves. A new, simplified synchronization scheme is proposed, focusing on causal relationships triggered by actions and concept states.
**The goal is to achieve:**
* **Incrementality:** The ability to add new features with localized changes.
* **Integrity:** Preventing new code from breaking existing functionality.
* **Transparency:** Clear understanding of what changes have been made and what actions are happening at runtime.
By decoupling functionality into concepts and orchestrating them with granular synchronizations, the authors believe software will be more modular, easier to understand, and better suited for LLM-assisted development. The paper includes a specification format for concepts, a language for synchronizations, and a design for an execution engine, demonstrated through a case study using the RealWorld blogging application benchmark.
In essence, the theory advocates for a shift towards a more declarative and event-driven architecture to improve software maintainability and leverage the potential of LLMs in a more reliable way.
The theory centers around two key elements:
* **Concepts:** These are independent, user-facing units of functionality with well-defined purposes (like "Post," "Comment," or "Upvote"). They act as self-contained services.
* **Synchronizations:** These are granular, event-based rules that mediate interactions *between* concepts. They orchestrate data and control flow *without* creating direct dependencies between the concepts themselves. A new, simplified synchronization scheme is proposed, focusing on causal relationships triggered by actions and concept states.
**The goal is to achieve:**
* **Incrementality:** The ability to add new features with localized changes.
* **Integrity:** Preventing new code from breaking existing functionality.
* **Transparency:** Clear understanding of what changes have been made and what actions are happening at runtime.
By decoupling functionality into concepts and orchestrating them with granular synchronizations, the authors believe software will be more modular, easier to understand, and better suited for LLM-assisted development. The paper includes a specification format for concepts, a language for synchronizations, and a design for an execution engine, demonstrated through a case study using the RealWorld blogging application benchmark.
In essence, the theory advocates for a shift towards a more declarative and event-driven architecture to improve software maintainability and leverage the potential of LLMs in a more reliable way.
Web developers are increasingly using sync engines, an old-school technology, to enhance the performance of modern web applications. Sync engines are software designed to synchronize data between multiple devices or services, providing high-quality user interfaces by enabling instant reads and writes without progress bars. This resurgence in popularity is driven by the shift to web-based software, better local storage capabilities, and the influence of high-profile apps utilizing sync engines.
An exploration of the importance of time in distributed databases and systems, discussing logical clocks, physical clocks, synchronization, and their implications on event ordering and consistency.
