Libene Fernandes > Recent Status Updates

Terminei o primeiro livro de Macabeus.
⭐️⭐️⭐️

Terminei o livro de Ester.

Terminei o livro de Judite.

Terminei o livro de Tobias.

Terminei o livro de Neemias.

Terminei o livro de Esdras.

Terminei o segundo livro de Crônicas.

Terminei o primeiro livro de Crônicas.

Terminei o segundo livro de Reis.

Terminei o primeiro livro de Reis.

Terminei o segundo livro de Samuel.

Terminei o primeiro livro de Samuel.

Terminei o livro de Rute.

Terminei o livro de Juízes

Terminei o livro de Josué.

Terminei o livro de Deuteronômio

Terminei o capítulo Números.

Terminei o Levítico.

o desejo é esse buraco em torno do qual a gente fica girando
girando girando e falando
numa eterna tentativa de nomear e dar sentido
e que a gente não sabe direito o que que é mas que
sempre puxa a gente de alguma forma

sob os pés
a cabeça oca
no corpo invertido
que olha olha e pouco vê
míopes os caminhos
tortas as classes

A Repository “mediates between the domain and data mapping layers using a collection-like interface for accessing domain objects.”

...Data Transformers might be a better approach on specific cases. These are just black boxes with Domain concepts (Aggregates, Entities, etc.) as inputs and read-only representations (XML, JSON, CSV, etc.) as output.

...DTOs are a clean and simple solution that could be passed to template engines for different representations, but this might complicate the logic of this last step of data transformation, as the logic for such templates could become a problem to maintain, test, and understand...

Consider a similar case for a blog. We might expose our potential as writers in HTML to the world, but some people will be interested in consuming our articles through RSS. The use cases — Application Services — remain the same. The representation doesn’t...

A good software architecture allows decisions about frameworks, databases, web- servers, and other environmental issues and tools, to be deferred and delayed. A good architecture emphasizes the use-cases and decouples them from peripheral concerns.

Tell-Don’t-Ask is a principle that helps people remember that object-orientation is about bundling data with the functions that operate on that data. It reminds us that rather than asking an object for data and acting on that data, we should instead tell an object what to do. This encourages to move behavior into an object to go with the data.

Modules are a way to communicate, as they provide us with insights about how the Domain Model works internally, along with helping us increase the cohesion and decrease the coupling between the concepts. Modules are not just a way to group related concepts in the model, but also a way to express part of the design of the model.

The essence of a Domain Event is that you use it to capture things that can trigger a change to the state of the application you’re developing or to another application in your Domain that’s interested in those changes. These Event objects are then processed to cause changes to the system and stored to provide an audit log.

When developing a single application, Events come in handy for decoupling components. When developing a whole Domain in a distributed way, Events are very useful for decoupling each service or application that plays a role in the Domain. The key points are the same, but on a different scale.

The way to avoid falling into an Anemic Domain Model is to, when starting a new project or feature, think of the behavior first. Databases, ORMs, and so on are just implementation details, and we should strive to push the decision to use these tools as late in the development process as we can. In doing so, we can focus on the one true attribute that matters: the behavior.