Encapsulement: Será que Esconder Todos o Detalhes de Implementação o Semper a Boa Decisão?

Disclaimer

This text was originally created by IA and is a functional transcription of episodes from this channel, Dev Efficient. A full episode cannot contain a channel.

Introduction

No post de hoje, that can happen with encapsulating it. Once you know you have a chance: can you skip all the details of the real implementation or make a good decision?

Encapsulation and suas implicações

We analyze a practical example. A project that is not of good quality can vary from references to a goal of a certain class. It is possible that you can use a simple and additional HTML page page. An idea of ​​encapsulation is a function that can be used to simplify HTML and receive simple HTML, it is so exactly what it is.

No time, for example more of this kind of thing, know that this interface is a metamorphosis that indicates that this is remote. It is important that you use a local chamada, it is a verdade, a remote chamada. Is it an important question: what exactly is this exactly?

A Importância de Export Certos Detalhes

Eu, Rafael and Maurício discuss bastante matters, so no efficient developer. There is no error or mistake, but there is no design. If you notice that a chamada is a remote place, you can cause problems, especially if you assume that a chamada is a local use of an inadequate way of working, because it is a loop. There may be unthought-out execution times and problems.

If you do that, you may find that a person can solve a problem remotely. For example, you can mention the form method that you need to use remotely, so that you can use this data to get more information to make adequate decisions. You can add additional documentation.

Encapsulation and execução Assíncrona

What is important is an execution assíncrona. Imagine you have a method that returns void, an execution and an assíncrona. This can affect the code. If you know that the execution is a good thing, you may be working with an adequate approach. Because languages ​​are so abstract as to indicate that the result will be a computation of the manual process. There is no Javascript that can use a Promise, no Javascript that can use a CompletableFuture(promised by promise) and who can go through.

Conclusion

Encapsulated implementation details can be a practical application, but it is important to leave the details aside and do research. Infrastructure or execution time details are explicit instructions, without affecting your code. Fixing issues ensures that the code is used sufficiently.

Do we want to ask more questions?

If you find it okay, please leave a comment about this. Is this a constructive comment? Deixa is an educational activity. Vamos trocar mais ideias :).

Conheça mais sobre a Jornada Dev + Eficiente

A Jornada Dev + Efficient is a traineeship with a purpose that can be created as a specialist in design and software architecture.

For more information, please visit https://deveficiente.com