Eduard Leandro @3du4rd

¡Aprobé el Curso de n8n Self-Hosted para Empresas en @platzi! #NuncaParesDeAprender platzi.com/p/3du4rd/curso…

¡Aprobé el Curso de Automatizaciones con n8n en @platzi! #NuncaParesDeAprender platzi.com/p/3du4rd/curso…

Lecciones clave del éxito de Patrick: 1. La simplicidad supera a la complejidad 2. Centrarse en la felicidad del desarrollador 3. Piensa en juegos que duren una década 4. Mantente humilde, sigue construyendo 5. Resolver problemas reales Esta es la visión de Patrick sobre el futuro de Internet:

The slides from my "The C4 model - misconceptions, misuses, and mistakes" talk at @dev_bcn can be downloaded from static.simonbrown.je/devbcn2024-c4-… #devbcn

Los 20 anuncios más creativos e icónicos que jamás hayas visto: 1. Raid - Insecticida

▶️UNA HISTORIA QUE TE HARÁ PENSAR EN TODAS LAS OPORTUNIDADES QUE TE DA LA VIDA No había en el pueblo peor trabajo que ser portero del prostíbulo. ¿Pero qué otra cosa podría hacer aquel hombre?

Maiden launch of Falcon Heavy, the most powerful operational rocket on Earth, with the first dual rocket landing

I found three guys who go around asking multimillionaires how they made their wealth. Surprisingly all of them said the one same thing. Here are the best 7 videos:

keyboard_arrow_left Previous keyboard_arrow_right Next

Las mejores webs para leer y/o descargar libros gratis. Guárdalos o te arrepentirás.

The Ultimate List of Best Software Architecture Books (2024) 📗 workingsoftware.dev/the-ultimate-l…

Si te falta "autoconfianza", lee esto: - Hilo de Psicología -

¡Quedé en el primer lugar de la División Bronce en @duolingo!

¡Estoy aprendiendo inglés en Duolingo! Es gratis, divertido y efectivo.

𝗪𝗵𝗮𝘁 𝗜 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 𝗧𝗵𝗲 𝗛𝗮𝗿𝗱 𝗣𝗮𝗿𝘁𝘀 I recently read the book "𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: 𝗧𝗵𝗲 𝗛𝗮𝗿𝗱 𝗣𝗮𝗿𝘁𝘀" by Neal Ford, Mark, Richards, Pramod Sadalage & Zhamak Dehghani. The book is mainly related to breaking monolith applications into microservices and could be an excellent companion to the book "Monolith to Microservices," by Sam Newman. The book emphasizes the step-by-step approach of breaking down monolith, with different patterns for each step, and balancing tradeoffs for those patterns. The book is titled "Hard Parts," yet most of the concepts in the book are familiar. Here are 𝘁𝗵𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗜 𝗹𝗶𝗸𝗲𝗱 from the book: 1. The most essential architecture skill is how to make decisions and balance trade-ffs 2. Advice on how to do a modern tradeoff analysis: 🔹 Find what parts are entangled together. 🔹 Analyze how they are coupled to one another. 🔹 Assess tradeoffs by determining the impact of change on interdependent systems 3. The main modularity drivers are: 🔹 Speed-to-market, achieved by architectural agility, i.e., the ability to respond quickly to a change. 🔹 Scalability, where the need for more scalability support increased user activity 🔹 Fault tolerance, the ability of an application to fail and continue to operate 4. Breaking down monolith with the two methods: 🔹 Component-based decomposition (if monolith is modular): it applies different refactoring patterns for extracting components to form a distributed architecture in an incremental way 🔹 Tactical forking (if the monolith is a big ball of mud): copy the whole monolith and remove the part not needed 5. Sizing components 🔹 Calculate the total number of statements (with ;) with a given component—the ideal size of 1 to 2 standard deviations from the average component size. Here are 𝘁𝗵𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗜 𝗺𝗶𝘀𝘀𝗲𝗱 in the book: 1. Although the book is abstract (as expected from architects), it doesn't go into any implementation details or technologies or mention architectural patterns. 2. The book follows Sysops SAGA's fictional story, whereas a real-life example would be more worthwhile. In this way, some things would sound artificial or forced. 3. I need to catch the data, as the book makes many assumptions. As it is not backed with any real-life project (pricing, etc.), we are still determining what metrics we would get. 4. I missed the structured approach. It started well with essential concepts, such as modularity and decomposition, and then twelve immediately into components and pulled apart data. Then, it went to service granularity and reuse patterns and data ownership and access patterns later. #softwaredesign

8 Japanese Techniques To Overcome Laziness 1)

𝗖𝗮𝗽𝘁𝘂𝗿𝗶𝗻𝗴 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀 𝘄𝗶𝘁𝗵 𝗔𝗗𝗥𝘀 There are several ways to 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲, such as UML, 4+1 view model, C4 model, and 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗥𝗲𝗰𝗼𝗿𝗱𝘀 (𝗔𝗗𝗥𝘀). ADRs document the decisions made during the design and implementation of a software system or application. An ADR is a brief document that captures the rationale behind a particular architectural decision, the alternatives that were considered, and the trade-offs involved. ADR represents 𝗮 𝗹𝗼𝗴 𝗲𝗻𝘁𝗿𝘆 about an architectural decision that has been made that led to the state of architecture then (the why). Typical 𝗔𝗗𝗥 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 consists of:  🔹 𝗧𝗶𝘁𝗹𝗲. A short descriptive title that summarizes the decision being documented.    🔹 𝗦𝘁𝗮𝘁𝘂𝘀. Proposed, Accepted, etc.  🔹 𝗖𝗼𝗻𝘁𝗲𝘅𝘁. A description of the technical, business, or organizational context that led to the need for the decision.  🔹 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻. A statement that describes the decision made, along with any relevant details or options considered.  🔹 𝗖𝗼𝗻𝘀𝗲𝗾𝘂𝗲𝗻𝗰𝗲𝘀. A description of the potential consequences of the decision, including any trade-offs or risks involved.  🔹 𝗔𝗹𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝘃𝗲𝘀. A list of considered alternative options, along with their pros and cons.  🔹 𝗚𝗲𝗻𝗲𝗿𝗮𝗹 𝗶𝗻𝗳𝗼, such as date and authors. A good recommendation is to store ADRs in your 𝗚𝗜𝗧 𝗿𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆, close to your code, or on the Wiki page if you want to be visible to non-developers too. One of the best uses of ADRs is the 𝗲𝗻𝘁𝗿𝘆 𝗽𝗼𝗶𝗻𝘁𝘀 𝗳𝗼𝗿 𝗱𝗶𝘀𝗰𝘂𝘀𝘀𝗶𝗼𝗻𝘀 𝗮𝘀 𝗮𝗻 𝗥𝗙𝗖 (Request for Comments). RFS represents an idea that can be reviewed by other team members with approval. Some different templates and tools can be used for ADRs. Check them in the comments. #technology #softwareengineering #programming #techworldwithmilan #softwarearchitecture

@Colombia Chuspa

CÓMO RECORDARLO TODO Hilo

@hasantoxr AI

@Damn_coder JS