Every modern technological development project of a system is based on development time. However, after its completion, the developed software remains stagnant for a long time of use. Here, then, are the concepts of temporality and timelessness.
Why bring up this idea?
At the threshold of each delivery, quality is compromised in a hidden way by developers who seek to maintain their work, for which deliveries must be made imperatively. The sacrifice is due to functionality, which has its implementation limited to the most precious resource of a project during its execution: TIME! This is paradoxically irrelevant after the completion of the said project!
The negative impact of this fact is enormous. Forcing people to use limited functionality in software (or even with bugs in many cases) for an indefinite period no longer makes sense. But the delivery was made! Considering that we find absurdities in the opposition of meanings: the fact is exposed!
Secondly, conventional management of software development projects does not consider the increase in complexity over time: Well, if there are no features developed, 100% of the time is spent developing them. But, on the other hand: if there are already many features developed, most of the time is divided between analyzing what already exists and, on the other hand, developing the new one.
The issue is not creating disharmony between the two, the old and the new universe. The current moment needs harmony between the parts to sustain itself in a balanced way. If the system is too complex and disorganized, versioning collapses will often occur.
Regardless of this, inadequate systems development environments direct most of their teams' efforts towards solving problems, leaving no energy left for developing truly necessary and efficient features of the system in question.
E1: In Search of Lost Time by Marcel Proust. The Sync Schema synchronizes entities and processes at certain levels of abstraction. There must be consensus on the defined schema that cannot belong to a single person (in the case of non-individual collaborative bases).
E2: Sync Schema relatively synchronizes the artifacts produced during the period.
E3: All model construction begins in the middle of the Sync Schema.
E4: All actions and artifacts are based on this schema. There cannot be a valid element and action that is not included in the aforementioned schema. The schema follows an evolutionary cycle that represents the knowledge generated in its spiral. New cycles allow for new schemas.
E5: Analyzing the modification of schemas over time, there must be compatibility of the artifacts developed. It is therefore important that the schema is evolutionary. Disruptive schemas must be implemented in new graph md to avoid execution problems with algorithms already developed. This is certainly the most important decision of a cycle: defining its schema.
E6: The schema allows development from a central point, at the level defined by the graph md. Interfaces are defined by local states and global contexts.
E7: Less complex and less mature models can have a faster modification frequency.
E8: The synchronization schema is the key to the Synthesis development methodology. Because it unifies the two temporal and timeless universes. Preserving the best of both worlds.
E9: For a better understanding of the concepts of temporality and timelessness, we strongly recommend reading the book: In Search of Lost Time by Marcel Proust. The author builds a time machine from his own life, giving us the key to open the windows of the soul and travel through memories in search of our lost time.
E10: It is worth noting that at the beginning of his life, with all the energy in his body, Proust did not think he was capable of writing a single line. He died asking his maid to fetch him, already without strength and time, in his last moments, another piece of paper to compose the final ideas of his masterpiece before they were lost.
A whole history is dedicated to the development of technology to help people be healthier.
My contact with the medical field came during my master's degree in computer science and my doctorate in neuroscience.
We started with the development of the PACS image server at PUCRS's São Lucas Hospital and an integrated and embedded system (chip) for processing and recognizing medical image patterns to support diagnosis. During this period, research and development were focused on building dynamic models that predicted not only the patient's current state but also made physiological projections to measure the patient's future health state, analyzing their behaviors. Along with the concept that each behavior can contribute to the continuous construction of knowledge bases and be applied through intelligent agents.
The Knowledge Synthesis project evolved in conjunction with my academic career in the health field. The greatest privilege was having been chosen countless times as a guest professor for Computer Science courses for classes taught in the disciplines of Logic, Programming, and AI.
Journal and Conference Reviewer: (a) Reviewer for the Journal of Health Informatics (JHI); (b) Technical reviewer for the Journal of Computer Methods in Biomechanics and Biomedical Engineering: Imaging & Visualization (JCM-BBE: IV); (c) Member of the Technical Programming Committee of the Symposium on Computing Applied to Health (SBCAS); (d) Member of the Technical Programming Committee and Chair of the Technical Session on Covid-19 of the School of Computing Applied to Health (ERCAS/USP); (e) Member of the Technical Programming Committee of the Congress on Health Informatics (SBIS)
Academic background: (a) PhD in Medicine and Health Sciences; The Pontifical Catholic University of Rio Grande do Sul, PUCRS, Porto Alegre, Brazil; Title: Computational model to support the diagnosis of Epilepsy, Year: 2012; Studied for two years starting in 2010 and continuing until 2016. (b) Master's degree in Computer Science from PUCRS (2005 - 2007); Title: Indexing architecture applied to PACS servers for image processing; Advisor: Eduardo Augusto Bezerra. (c) Bachelor's degree in Computer Science from PUCRS (2004). Title: Model for storage and retrieval of medical images with diagnostic support.
contact@graph.md to get more information on graph md points of view.
Av. João Pessoa, 731 - Sala 802 - Cep: 90.040-000 - Porto Alegre, Brazil