> For the complete documentation index, see [llms.txt](https://claudiu-stanciu.gitbook.io/software-craft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claudiu-stanciu.gitbook.io/software-craft/principles.md).

# Software Principles

## DRY

* don’t repeat yourself => don’t duplicate code ..

## KISS

* keep it simple => don’t add extra fluff

## YAGNI

* you aren't going to use it => don’t add extra fluff

## SOLID

* Single responsibility = module/class should have a single responsibility
* Open/closed = module/class should be open for extension and closed for modification
* Liskov substitution = objects from a class/type can be replaced by objects of the subclass/subtype
* Interface segregation = many specific interfaces are better than 1 general-purpose interface
* Dependency inversion = depend on abstractions and not on implementation details
* Materials
  * <http://www.dimecasts.net/Casts/ByTag/SOLID%20Principle>

## Inversion of Control & Dependency Inversion

* the flow is managed by a framework, which calls the custom code( written/applicative code)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://claudiu-stanciu.gitbook.io/software-craft/principles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.