I have just finished reading Data and Reality by William Kent. This book is not very popular and was written in 1978, so programming practices and database technology were quite different at the time. The most popular database system back then was IBM IMS (Information Management System), while CODASYL was gaining popularity. IBM IMS offered a simple way to store and retrieve data using a tree structure, whereas CODASYL implemented a graph-based (network) model, providing an alternative way to relate entities without relying on joins.

The book focuses mainly on the idea that reality cannot be fully expressed in systems or databases. It presents many examples that are still valid today. Nowadays, we have many ways to store data and a wide variety of underlying algorithms, yet we are always searching for more optimal ways to store and retrieve information. For example, we use SQL databases, NoSQL databases, graph databases, spreadsheets, and cache databases. The author anticipated that the tools we have are not sufficient to replicate reality in our systems, and the most interesting aspect of this book is that even today, in 2026, the tools we use are still not enough to fully represent reality.

One example showing that reality is hard to express in a system is a book that could be printed in two physical volumes because it is too large and stored in different places, but in the system it would be represented as a single book entity.

Another example: a husband and wife may work at the same company and, when considering medical benefits, they must be treated separately. Or suppose a person has two jobs within the same company. In reality, these situations can happen, but they are hard to represent correctly in a system.

In terms of changes to entities, an important question arises: When does an entity remain the same entity? For example, owning a car could mean registering the engine block, while all other parts can be removed or changed without affecting the identity of the car in the system.

The author explains that it is often better to treat objects as eternal for practical purposes. Objects can be stored for analytical reasons, or they can be recreated with the same values (for example, rehiring the same person). This expresses the idea that, in reality, objects can be destroyed, but in a system they conceptually always exist.

In a system, the administrator ultimately decides what “reality” is. For example: Should we allow numbers in names? Should we include middle names? Should we allow capital letters? Should we include hyphens or commas? These are decisions that define the reality of your system. The same applies to things like telephone numbers.

He has a chapter dedicated to the record model, which is closer to the relational model. However, he shows many examples where modeling can be challenging without the practices we use today. For example, when modeling a many-to-many relationship, it is necessary to create a separate record for the relationship. Theoretically, you could also create relationship records even if the relationship is not many-to-many. He also discusses considerations such as deleting data, dependencies between entities, and data validation.

I can imagine why the author felt limited when trying to represent data reality in older systems such as IMS, which used a tree-based algorithm to store and retrieve data. Today, SQL is the most popular language with a relational model behind it. This prediction was written by William Kent in his book when he mentioned that, in the future, data would be modeled by entities and relationships instead of data items and records.

Key Takeaways

• Reality is more than the current tools can represent.
• As a data models what part of reality you want to represent in your system.
• No single data model fits all problems; trade-offs are unavoidable.
• During the 70’s the most popular data models were based on tree and network system.

He terminado de leer este libro recientemente. Como mexicano, encuentro en él una interesante reseña sobre el consumo de drogas en el último siglo. El libro narra cómo México ha lidiado con las drogas desde 1900 hasta principios del 2000. No había leído antes un libro sobre este tema en México y este me pareció muy bueno.

La forma en que Luis Astorga describe la historia de las drogas en el país es desde un punto de vista neutro, y menciona muchos nombres de personas involucradas, como jefes de cárteles, policías, presidentes municipales y otros cargos políticos. Puede ser un poco abrumador ver tantos nombres y personajes involucrados a lo largo de un siglo, pero cada una de esas personas tuvo un impacto en las políticas y estrategias de México para enfrentar a los cárteles.

En general, está lleno de contenido histórico y referencias a periódicos, lo cual hace de este libro un excelente trabajo.

Me parece muy interesante cómo, a pesar de que ha pasado un siglo, la situación de México no ha cambiado realmente. Varios presidentes han pasado y varios señores del narco han surgido y desaparecido, y pareciera que es el destino de México vivir en esta situación. El problema de las drogas no es exclusivo de México; varios países lo tienen. Sin embargo, México se distingue especialmente por la brecha económica entre Estados Unidos y México, y esto ha hecho que el país sea un proveedor de muchos productos para Estados Unidos, incluyendo drogas, alcohol, frutas, verduras y partes de autos.

Entre las primeras cosas que encontré interesantes está que, desde el siglo XIX, se elaboraban tónicos a base de vino con pepsina, coca (hoja de un arbusto), kola (una nuez) y otros ingredientes. Estos fueron los orígenes de bebidas como Pepsi y Coca-Cola. Además de estos tónicos, había otras sustancias, píldoras e inyecciones para diferentes enfermedades. En aquellos años no existían regulaciones sobre el uso de sustancias nocivas y muchas personas abusaron de sus efectos.

El uso de estas drogas ha estado presente en la historia de la humanidad durante muchos años, solo que a principios del siglo XX surgió una tendencia entre los imperios por intentar “perfeccionar” la raza. En ese contexto, el uso de drogas — incluyendo tabaco y alcohol — empezó a considerarse como algo que degradaba a la población. El consumo de sustancias se asociaba específicamente con accidentes, muertes por sobredosis y la incapacidad de participar en labores.

Los principales estados mencionados son Sinaloa, Chihuahua y Sonora. Se habla más sobre Sinaloa, pues se menciona que hubo asentamientos de chinos en México y que solían consumir opio. Durante un tiempo, se les culpó del incremento en el consumo de esta droga.

El autor también menciona los diferentes precios de los narcóticos a través de los años. En general, estos precios han cambiado con el tiempo, pero el costo de las drogas en Estados Unidos siempre ha sido significativamente mayor que en México.

El libro contiene bastantes datos históricos, pero me gustaría concluir este blog con algunos datos más recientes que he encontrado en internet.

• Se estima que el jefe de la droga más poderoso tiene alrededor de 15 mil millones de dólares.
  Además, entre 18 mil y 29 mil millones de dólares en efectivo pueden generar los cárteles al año.
• Una hectárea cultivada de coca puede producir aproximadamente 7 kilos de cocaína. Si consideramos un precio de 40 mil USD por kilo, una sola hectárea podría generar 280 mil USD. Esto significa que una hectárea puede producir cerca de 6 millones de pesos.
• El salario promedio anual en México es de alrededor de 140 mil pesos. Lo cual significa que una sola hectárea de coca podría cubrir el salario anual de 42 mil mexicanos.

Estos números muestran el enorme impacto económico de esta industria en México, pues prácticamente puede influir en sembradores, comerciantes, transportistas, policías, cargos políticos y ciudadanos.

Adjunto una imagen con información actualizada que muestra el precio de la cocaína por país. En ella se aprecia que, en 2019, 1 kilo de cocaína en México costaba alrededor de 12,000 USD, mientras que en Estados Unidos su precio rondaba los 69,000 USD. También se observa que el precio en Colombia era significativamente menor — 1500 USD . Esta información refuerza la enorme diferencia de valor a lo largo de la cadena de producción y distribución, lo cual explica por qué esta industria tiene un impacto tan fuerte en la región.

https://eltiempolatino.com/2022/11/09/opinion/cuanto-cuesta-la-cocaina-en-el-mundo/

Con varias controversias al final del año pasado, en 2024, en México se aprobó una reforma para que los ciudadanos pudieran elegir a los miembros del poder judicial. Se dice que una de las principales razones por esta reforma es porque, según investigaciones, solo un pequeño grupo selecto llega al poder y no cuentan con un filtro meritocrático. Además, se dice que el poder judicial no es tan eficiente como se espera. El contexto también tiene que ver con desacuerdos entre el expresidente Andrés Manuel y la presidenta de la Suprema Corte de Justicia, Norma Piña.

Aunque muchos afirman que esta reforma va a solucionar los problemas actuales, otros sugieren que no se están atacando los principales problemas. Por ejemplo, se dice que esta reforma no toca las fiscalías, las cuales son una parte importante porque son quienes recaban las evidencias para que los jueces puedan tomar decisiones. Debido a la gran cantidad de casos de delincuencia, la fiscalía no puede proporcionar las evidencias necesarias para procesar un caso correctamente.

La reforma al poder judicial plantea poder elegir a los jueces de forma popular. Aunque suena bien del lado democrático, también genera otros problemas, porque la mayoría de las personas no conocemos a quienes se postulan. La verdad es que investigar a cada una de las personas requiere un esfuerzo inhumano. Si fuera a votar el día de hoy, lo más probable es que elija al azar a cada uno de los candidatos.

Por esta razón decidí utilizar herramientas de deep thinking como Gemini y ChatGPT para analizar a cada uno de los candidatos. Utilizar inteligencia artificial para seleccionar candidatos suena como dejar que la IA nos controle, pero debido al poco tiempo que tengo, creo que usar IA es mejor que votar al azar.

Usar una IA para analizar los candidatos no es tan simple como pedir los nombres para votar. Debemos ser claros en nuestros requerimientos y también aplicar deep thinking para que profundice en el análisis de cada candidato. Hay algunas desventajas en este tipo de análisis, porque muchos candidatos pueden no tener mucha información en internet, lo cual podría sesgar la decisión.

Vamos a empezar generando un prompt. La forma en que lo hice fue a través de ChatGPT Pro y Gemini: le di contexto sobre la elección judicial y le pedí múltiples veces que analizara el prompt y lo mejorara. Este fue el resultado, excluyendo alguna información como el análisis de cada uno. Además, modifiqué el prompt de acuerdo a la boleta.

Nuestro principial objectivo es obtener la lista de los candidatos mejores calificados para el perfil.

TLDR;

Morado Mujeres: 09, 14, 17, 05, 04.
Morado Hombres: 35, 55, 38, 43.
Verde mujeres: 02, 09, 01.
Verde hombres: 30, 23.
Azul Mujer: 03.
Azul Hombre: 13.
Beige Mujeres: 02, 07.
Beige Hombres: 11.

PROMPT

Rol Principal: Actúa como un Analista Jurídico experto, especializado en el riguroso proceso de selección de MINISTRAS Y MINISTROS DE LA SUPREMA CORTE DE JUSTICIA DE LA NACIÓN

Tu Misión: Evaluar la idoneidad de cada candidato/a para ocupar una vacante en este prestigioso tribunal. Tu análisis se basará exclusivamente en la información que te proporcionaré (entrevistas, declaraciones públicas, CVs, y documentación relevante).

Proceso por Candidato/a:

Para cada candidato/a que te presente, realizarás el siguiente análisis individual:

A. Evaluación por Criterios Fundamentales:

Otorga una calificación de 1 a 10 (donde 1 = muy deficiente y 10 = excelente) para cada uno de los siguientes criterios. Justifica brevemente cada valoración, destacando los puntos fuertes y débiles observados para ese criterio específico, similar al ejemplo proporcionado:

Ética (1–10):

Principios rectores: Integridad personal intachable, independencia de criterio demostrada, compromiso con los principios constitucionales y el respeto irrestricto a los derechos humanos.

Conducta: Ausencia total de conflictos de interés (pasados o potenciales) y de conductas públicas o privadas que hayan sido cuestionadas fundadamente.

Justificación Breve: (Ej. “Demuestra sólida integridad en su trayectoria [mencionar evidencia], aunque se observa una [ligera crítica o punto a considerar si existe, o ‘sin puntos débiles evidentes en este rubro’]”).

Conocimientos Jurídicos (1–10):

Dominio técnico: Profundo conocimiento del derecho constitucional y electoral, así como de disciplinas afines.

Capacidad analítica: Calidad y solidez en la argumentación jurídica, claridad conceptual y precisión técnica.

Contribución intelectual: Relevancia y calidad de sus aportes (artículos de investigación, libros, dictámenes, ponencias, sentencias si aplica).

Justificación Breve: (Ej. “Sobresaliente dominio del derecho electoral evidenciado en [publicación X / cargo Y]. Su capacidad argumentativa es [calificativo]. Podría profundizar en [área específica si aplica]”).

Trayectoria Profesional (1–10):

Desarrollo y coherencia: Estabilidad y progresión lógica en su carrera profesional.

Relevancia de cargos: Importancia e impacto de los cargos desempeñados en el ámbito jurídico, especialmente en materia electoral o constitucional.

Logros y contribuciones: Aportaciones significativas al desarrollo del derecho, la academia o la función pública.

Reconocimientos: Distinciones oficiales, académicas o profesionales relevantes.

Justificación Breve: (Ej. “Carrera ascendente y coherente en [sector]. Su rol como [cargo] fue clave para [logro]. Se echa en falta experiencia en [ámbito X], si aplica”).

Experiencia Judicial o Jurídica Relevante (1–10):

Práctica directa: Participación activa y demostrable en la función judicial (preferentemente electoral), litigio estratégico en la materia, docencia jurídica especializada a nivel superior, o desempeño de funciones públicas/privadas con alta incidencia y relación directa con el derecho electoral y constitucional.

Justificación Breve: (Ej. “Amplia experiencia como [rol judicial/litigante/docente]. Su participación en [caso/proyecto Z] es destacable. Sería deseable mayor experiencia en [aspecto específico]”).

B. Estructura del Informe Individual por Candidato/a:

Informe Descriptivo del Perfil (Máximo 350 palabras):

Realiza una valoración cualitativa integral sobre la idoneidad del candidato/a para el cargo.

Integra tus observaciones de los cuatro criterios, destacando las principales fortalezas y debilidades del perfil en su conjunto.

Nota Adicional Obligatoria (si aplica): Si durante tu análisis detectas posibles riesgos significativos, conflictos de interés no resueltos, o conductas controversiales documentadas que podrían impactar su desempeño como Magistrado/a, inclúyelos de forma clara y concisa aquí.

Lenguaje: Profesional, objetivo, claro y accesible, evitando tecnicismos innecesarios.

Tabla Comparativa de Calificaciones:

| Criterio | Calificación (1–10) | Justificación Breve (incluyendo fortalezas y debilidades específicas del criterio) |

| : — — — — — — — — — — — — — — | : — — — — — — — — — | : — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — |

| Ética | | |

| Conocimientos jurídicos | | |

| Trayectoria profesional | | |

| Experiencia judicial/jurídica | | |Si algún criterio no puede ser evaluado fehacientemente por falta de información específica y crucial, indícalo explícitamente con “Información Insuficiente” en la calificación y explica brevemente en la justificación.

Síntesis de Pros y Contras del Perfil (General):

Pros: Lista de 3–5 aspectos más destacados y fortalezas relevantes del candidato/a, considerando el conjunto de los criterios evaluados y su adecuación al cargo.

Contras: Lista de 3–5 debilidades, vacíos o alertas más significativos detectados en el perfil, fundamentados estrictamente en la información disponible (evita especulaciones o hipótesis externas).

C. Proceso de Entrega de Información y Reporte Final:

Selecciona top 4 de hombre y top 5mujer.

Lista de candidatos:

MUJERES MINISTRAS Y MINISTROS DE LA SUPREMA CORTE DE JUSTICIA DE LA NACIÓN

ESTRADA TENA FABIANA

• Calificación Promedio: 9.25
• Argumentos Clave para Alta Valoración: Su profundo conocimiento del Poder Judicial Federal y de la SCJN, acumulado a lo largo de 26 años en roles de alta responsabilidad como Coordinadora General de Asesores de la Presidencia, se complementa con su papel protagónico como jefa del equipo redactor de la reforma judicial de 2021, lo que evidencia su dominio técnico y visión estratégica. Además, cuenta con una sólida formación académica (Licenciada en Derecho UNAM, Maestra en Derecho U. de Virginia) y experiencia docente en instituciones de prestigio.
• Calificaciones destacadas: Ética 9.0, Conocimientos 9.5, Trayectoria 9.5, Experiencia 9.0.
• Punto en contra: Su experiencia, aunque vasta, se ha desarrollado predominantemente dentro de la estructura interna del Poder Judicial Federal, con menor visibilidad de experiencia en litigio externo o en otros sectores del ámbito jurídico.

GONZALEZ TIRADO ROSA ELENA

• Calificación Promedio: 9.25
• Argumentos Clave para Alta Valoración: Posee una trayectoria excepcionalmente amplia y diversificada de más de 34 años en el Poder Judicial de la Federación, donde ocupó cargos desde Secretaria de Estudio y Cuenta en la SCJN hasta Jueza de Distrito y Consejera de la Judicatura Federal, lo que le otorga un profundo conocimiento integral del sistema. Su sólida formación académica, con maestría especializada en materia constitucional y administrativa, se suma a una clara postura pública sobre la importancia de la ética judicial, la transparencia y el combate a la corrupción.
• Calificaciones destacadas: Ética 9.0, Conocimientos 9.0, Trayectoria 9.5, Experiencia 9.5.
• Punto en contra: Si bien ha participado en la presentación de obras jurídicas y es autora de artículos , la información no detalla una extensa obra doctrinal individual (libros) en temas constitucionales de vanguardia.

IBARRA OLGUIN ANA MARIA

• Calificación Promedio: 9.2
• Argumentos Clave para Alta Valoración: Su perfil destaca por una excepcional y pertinente formación académica (Lic. CIDE, Mtra. y Doctoranda U. de Virginia, Máster U. Panamericana) y su actual rol como Directora del Centro de Estudios Constitucionales de la SCJN, que la posiciona en la vanguardia del pensamiento constitucional. Esto se complementa con una prolífica producción intelectual en derechos humanos y su experiencia directa en la SCJN como Secretaria de Estudio y Cuenta, donde contribuyó a importantes líneas jurisprudenciales.
• Calificaciones destacadas: Ética 9.5, Conocimientos 9.8, Trayectoria 9.0, Experiencia 8.5.
• Punto en contra: Su experiencia profesional, aunque de muy alto nivel intelectual y estratégico dentro de la SCJN, no incluye una trayectoria extensa como jueza o magistrada en la resolución directa de casos en órganos jurisdiccionales inferiores.

CASTAÑEDA PEREZ MARISOL

• Calificación Promedio: 9.0
• Argumentos Clave para Alta Valoración: Cuenta con una sólida y extensa trayectoria dentro del Poder Judicial de la Federación, con experiencia como Jueza de Distrito y Magistrada de Circuito en diversas materias, respaldada por una robusta formación académica que incluye un Doctorado en Derecho Penal y Maestrías en Derecho Fiscal y Constitucionalismo. Su liderazgo es reconocido al haber sido Presidenta de la Asociación Mexicana de Juzgadoras y distinguida como una de las “Abogadas más Influyentes en México”.
• Calificaciones destacadas: Ética 8.5, Conocimientos 9.0, Trayectoria 9.0, Experiencia 9.5.
• Punto en contra: Aunque las denuncias y quejas en su contra fueron declaradas improcedentes , su existencia podría ameritar una revisión más detallada si se dispusiera de mayor información contextual.

BONILLA GARCIA JAZMIN

• Calificación Promedio: 8.875
• Argumentos Clave para Alta Valoración: Su perfil combina una sólida y especializada formación académica (Maestra en Derechos Humanos y Democracia FLACSO, doctoranda en Derecho UP) con un profundo conocimiento del funcionamiento interno de la SCJN, adquirido como Secretaria de Estudio y Cuenta y Secretaria de Acuerdos de Sala. Ha demostrado una trayectoria coherente y ascendente en el Poder Judicial Federal, culminando como Magistrada de Circuito comisionada en la SCJN, y ha presentado propuestas concretas para la modernización de la justicia, además de contribuciones intelectuales publicadas.
• Calificaciones destacadas: Ética 9.0, Conocimientos 9.0, Trayectoria 8.5, Experiencia 9.0.
• Punto en contra: Su nombramiento como Magistrada de Circuito es reciente (2024) , por lo que su experiencia directa en la resolución de casos como juzgadora titular de un órgano colegiado es limitada en tiempo, aunque su experiencia en la SCJN es extensa.

HOMBRE MINISTRAS Y MINISTROS DE LA SUPREMA CORTE DE JUSTICIA DE LA NACIÓN

JAIME ALLIER CAMPUZANO

• Calificación Promedio: 9.45
• Argumentos Clave para Alta Valoración: Su perfil es excepcionalmente sólido debido a una extensa y completa carrera judicial dentro del Poder Judicial de la Federación, donde ha ascendido desde mecanógrafo hasta Magistrado de Circuito, demostrando un profundo conocimiento práctico del sistema. Esta experiencia se complementa con una robusta formación académica, que incluye un Doctorado en Derecho con promedio perfecto , y una prolífica producción intelectual de diez libros jurídicos y numerosos artículos en diversas áreas del derecho, incluyendo laboral, constitucional y amparo. Su propuesta de “humanismo judicial” y su reflexión sobre las virtudes republicanas del juzgador evidencian una filosofía judicial clara y un fuerte compromiso ético.
• Calificaciones destacadas: Ética 9.0, Conocimientos 9.5, Trayectoria 9.5, Experiencia 9.8.
• Punto en contra: Su enfoque en la justicia social y la interpretación más allá de la “ley a rajatabla” , aunque positivo, podría requerir un cuidadoso equilibrio para evitar percepciones de activismo judicial excesivo.

SERGIO JAVIER MOLINA MARTÍNEZ

• Calificación Promedio: 9.0
• Argumentos Clave para Alta Valoración: Su extensa y multifacética carrera dentro del Poder Judicial de la Federación, que incluye roles como Juez de Distrito, Magistrado y Consejero de la Judicatura Federal, le otorga una profunda experiencia y una visión estratégica del sistema judicial. Su robusto perfil académico, con un Doctorado en Derecho y múltiples especializaciones , se ve reforzado por una significativa producción académica centrada en la reforma laboral, donde ha demostrado liderazgo intelectual. Las distinciones por sentencias que protegen derechos humanos y aplican perspectiva de género subrayan su calidad como juzgador.
• Calificaciones destacadas: Ética 8.0, Conocimientos 9.0, Trayectoria 9.5, Experiencia 9.5.
• Punto en contra: Fue señalado como “traidor” por críticos de la reforma judicial debido a su voto decisivo en el Consejo de la Judicatura Federal , y se mencionó su cercanía con la ministra Yasmín Esquivel Mossa (su esposa trabaja en la ponencia de dicha ministra) como un potencial conflicto de interés.

EDGAR CORZO SOSA

• Calificación Promedio: 8.625
• Argumentos Clave para Alta Valoración: Combina una sólida formación académica internacional (Doctor en Derecho Constitucional por la UNAM y la Universidad Autónoma de Madrid; Maestría en París I Panthéon-Sorbonne) con una relevante experiencia en derechos humanos a nivel nacional (Quinto Visitador General en la CNDH) e internacional (representante de México ante la ONU). Su paso por la SCJN como asesor y Secretario de Estudio y Cuenta le proporciona un valioso conocimiento interno del máximo tribunal , y su rol como Investigador Titular en el IIJ-UNAM (SNI Nivel III) respalda su autoridad académica con publicaciones centradas en derechos humanos, migración y justicia constitucional.
• Calificaciones destacadas: Ética 8.5, Conocimientos 9.0, Trayectoria 8.5, Experiencia 8.5.
• Punto en contra: Su experiencia directa como juez o magistrado no es explícita en la información proporcionada, centrándose más en la academia, la asesoría y la defensa de derechos humanos.

GIOVANNI AZAEL FIGUEROA MEJÍA

• Calificación Promedio: 8.0
• Argumentos Clave para Alta Valoración: Su perfil académico es sobresaliente, con un Doctorado en Derecho Constitucional (Sobresaliente Cum Laude) por la Universidad Complutense de Madrid y reconocimiento como Investigador Nacional Nivel II del SNI. Su vasta producción académica, que incluye 3 libros como autor único, la coordinación de 12 obras colectivas y cerca de 50 textos académicos , ha influido en sentencias judiciales y ha sido citada en la Iniciativa de Reforma Constitucional al Poder Judicial, demostrando la relevancia de sus contribuciones doctrinales. Aunque carece de experiencia directa como juez, sus roles como asesor en el TEPJF y el CJF, y como director de escuela judicial, le otorgan una comprensión profunda del sistema.
• Calificaciones destacadas: Ética 6.0, Conocimientos 9.5, Trayectoria 8.5, Experiencia 8.0.
• Punto en contra: Fue sancionado con una amonestación pública por el TEPJF debido a la presentación extemporánea de su declaración patrimonial, calificada como falta no grave pero con señalamiento de “reiteración de conducta”, y no rindió informe durante el procedimiento administrativo

MAGISTRADAS Y MAGISTRADOS DEL TRIBUNAL DE DISCIPLINA JUDICIAL

TOP 3 MUJERES

EVA VERONICA DE GYVES ZARATE

• Calificación Promedio: 8.75
• Argumentos Clave para Alta Valoración: Su perfil destaca por una extensa y profunda carrera judicial, habiendo desempeñado roles como Juez, Magistrada y, notablemente, Consejera de la Judicatura Federal (2019–2024). Esta trayectoria se complementa con una sólida formación académica que incluye una Licenciatura en Derecho por la UNAM y múltiples especializaciones y maestrías en áreas cruciales como Derecho Penal, Amparo y Derecho Procesal Penal Acusatorio. En sus declaraciones, ha manifestado un firme compromiso con la independencia judicial, la imparcialidad y la lucha contra la impunidad, principios fundamentales para el Tribunal de Disciplina Judicial.
• Calificaciones destacadas: Ética 8.5, Conocimientos Jurídicos 9.0, Trayectoria Profesional 8.5, Experiencia Judicial/Jurídica 9.0.
• Punto en contra: Si bien su experiencia en el ámbito penal y procesal es vasta, la información disponible no detalla con la misma profundidad contribuciones específicas o experiencia directa en materia electoral, aunque su rol en la Judicatura Federal presupone una visión amplia del sistema.

CELIA MAYA GARCIA

• Calificación Promedio: 8.5
• Argumentos Clave para Alta Valoración: Posee una trayectoria judicial sumamente extensa y de alto nivel, habiendo sido Magistrada del Tribunal Superior de Justicia del Estado de Querétaro por más de tres décadas (1986–2019) y Juez en materia civil (1979–1985). Su preparación académica es robusta, ostentando un Doctorado en Derecho, Maestría en Derecho Fiscal y licenciaturas en Derecho y Contaduría Pública. Sus propuestas para el Tribunal se centran en la prevención de la corrupción, la promoción de la ética, la equidad y la justicia accesible, demostrando una visión integral para la disciplina judicial.
• Calificaciones destacadas: Ética 8.5, Conocimientos Jurídicos 8.5, Trayectoria Profesional 8.0, Experiencia Judicial/Jurídica 9.0.
• Punto en contra: Su perfil incluye múltiples candidaturas a cargos de elección popular por diferentes partidos políticos (PRD, Morena) , lo que, a pesar de su extensa carrera judicial, podría generar interrogantes sobre su independencia política percibida para un cargo que exige neutralidad absoluta.

ARIADNA CAMACHO CONTRERAS

• Calificación Promedio: 7.25
• Argumentos Clave para Alta Valoración: Cuenta con una sólida formación académica, que incluye dos Maestrías en Derecho, una en Litigio con especializaciones en Derecho Constitucional, Administrativo y Fiscal, y otra por la Southwestern Law School. Ha acumulado más de 15 años de experiencia en roles jurídicos de alta dirección dentro del Poder Ejecutivo a nivel federal y local, como Directora General de Asuntos Jurídicos en la Secretaría de Turismo y Subprocuradora en la SAFCDMX. Ha presentado propuestas articuladas para el Tribunal, enfocadas en la eficiencia, transparencia, perspectiva de género y combate a la corrupción.
• Calificaciones destacadas: Ética 6.5, Conocimientos Jurídicos 8.0, Trayectoria Profesional 7.5, Experiencia Judicial/Jurídica 7.0.
• Punto en contra: Un incidente durante su campaña, relacionado con una queja ante el INE por publicidad pagada por un tercero (“Político MX”) en su beneficio que fue ordenada a retirar , genera un punto de atención sobre la percepción de probidad. Además, carece de experiencia judicial directa como jueza o magistrada.

TOP 2 HOMBRES

GILDARDO GALINZOGA ESPARZA

• Calificación Promedio: 8.875
• Argumentos Clave para Alta Valoración: Su perfil se distingue por una carrera de 35 años íntegramente dentro del Poder Judicial de la Federación, ascendiendo desde Oficial Administrativo hasta Magistrado de Circuito, cargo que ocupa actualmente. Posee una robusta formación académica que incluye un Doctorado en Derecho, tres Maestrías (una en Derecho Judicial por la Universidad Panamericana) y una Especialidad en Derecho Administrativo por la Escuela Federal de Formación Judicial. Sus propuestas enfatizan la transparencia en los procedimientos disciplinarios y la lucha contra la corrupción.
• Calificaciones destacadas: Ética 8.0, Conocimientos Jurídicos 9.0, Trayectoria Profesional 9.0, Experiencia Judicial/Jurídica 9.5.
• Punto en contra: Aunque su compromiso con la transparencia y la lucha contra la corrupción es claro en sus propuestas , la información disponible no detalla logros específicos de alto impacto en materia anticorrupción más allá del ejercicio inherente a sus funciones judiciales.

BERNARDO BATIZ VAZQUEZ

• Calificación Promedio: 8.625
• Argumentos Clave para Alta Valoración: Cuenta con una notable experiencia en cargos de alta responsabilidad, habiendo sido Procurador General de Justicia del Distrito Federal (2000–2006) y Consejero de la Judicatura Federal (2019–2024). Su trayectoria incluye una extensa carrera legislativa como Diputado Federal en cuatro ocasiones, participando activamente en comisiones de Justicia y Gobernación. Ha manifestado una sólida postura ética respecto a la independencia judicial y un compromiso con la justicia. Es autor de varios libros de temática jurídica y profesor universitario.
• Calificaciones destacadas: Ética 8.5, Conocimientos Jurídicos 8.5, Trayectoria Profesional 9.0, Experiencia Judicial/Jurídica 8.5.
• Punto en contra: Su larga trayectoria política, con militancia en diversos partidos (PAN, PRD y posteriormente Morena) , podría ser vista por algunos como un factor que podría influir en la percepción de su imparcialidad, a pesar de su experiencia en roles judiciales y de procuración de justicia.

MAGISTRADAS Y MAGISTRADOS DE LA SALA SUPERIOR DEL TRIBUNAL ELECTORAL DEL PODER JUDICIAL DE LA FEDERACIÓN.

ADRIANA MARGARITA FAVELA HERRERA

• Calificación Promedio: 9.5
• Argumentos Clave para Alta Valoración: Cuenta con una excepcional y extensa trayectoria en los más altos niveles de los órganos electorales, tanto administrativos (Consejera del INE durante 9 años) como jurisdiccionales (Magistrada de Sala Regional del TEPJF). Demuestra un profundo conocimiento del derecho electoral, respaldado por su Doctorado en Derecho, múltiples publicaciones especializadas y vasta experiencia práctica en la materia. Posee un reconocido y sólido compromiso con la igualdad de género y la protección de los derechos de grupos vulnerables, además de experiencia directa en la organización de procesos electorales y la resolución de quejas y denuncias como Consejera del INE. No se identificaron señalamientos éticos en la información analizada.
• Calificaciones destacadas: Ética 9, Conocimientos Jurídicos 9, Trayectoria Profesional 10, Experiencia Judicial/Jurídica 10.
• Punto en contra: No se identificaron contras significativos en la información analizada para este perfil.

JORGE SÁNCHEZ MORALES

• Calificación Promedio: 9.5
• Argumentos Clave para Alta Valoración: Posee una trayectoria excepcionalmente amplia y diversa que abarca todos los ámbitos de la materia electoral: administrativo (Consejero Presidente del Instituto Electoral del Estado de Puebla), jurisdiccional local (Magistrado del Tribunal Electoral del Estado de Puebla) y jurisdiccional federal (Magistrado y Presidente de la Sala Regional Guadalajara del TEPJF, y actualmente Director General en el TEPJF). Cuenta con una sólida formación académica a nivel doctoral, complementada con múltiples estudios de posgrado en instituciones internacionales de prestigio, y es autor de varios libros y numerosos artículos sobre temas electorales relevantes como la reelección y la ciudadanía intercultural. Ha demostrado experiencia en la organización de elecciones a diversos niveles (presidenciales, senadores, diputados y gobernadores) y es el único candidato que ha llegado por segunda ocasión a la etapa final del proceso de selección para Magistrado de la Sala Superior. No se identificaron señalamientos éticos en la información analizada.
• Calificaciones destacadas: Ética 9, Conocimientos Jurídicos 9, Trayectoria Profesional 10, Experiencia Judicial/Jurídica 10.
• Punto en contra: No se identificaron contras significativos en la información analizada para este perfil.

MAGISTRADAS Y MAGISTRADOS DE LA SALA REGIONAL DEL TRIBUNAL ELECTORAL DEL PODER JUDICIAL DE LA FEDERACIÓN.

IRINA GRACIELA CERVANTES BRAVO

• Calificación Promedio: 9.75
• Argumentos Clave para Alta Valoración: Posee una excepcional formación académica que incluye un Doctorado en Derecho Procesal (sobresaliente cum laude) por la Universidad Complutense de Madrid y un Máster en Derecho Constitucional y Ciencia Política por el Centro de Estudios Políticos y Constitucionales de Madrid. Es miembro del Sistema Nacional de Investigadores Nivel 1 y cuenta con una prolífica producción intelectual con múltiples libros y artículos en materia constitucional y electoral. Su trayectoria profesional es sólida y ascendente, habiendo sido Magistrada y Presidenta del Tribunal Electoral de Nayarit, Secretaria de Estudio y Cuenta en el TEPJF, y Presidenta de la Asociación de Tribunales Electorales de la República Mexicana. Actualmente, se desempeña como Defensora Pública Electoral Especializada en violencia política de género, lo que añade una alta relevancia social y jurídica a su perfil. Ha recibido reconocimientos como el Premio AMIJ 2020.
• Calificaciones destacadas: Ética 9, Conocimientos Jurídicos 10, Trayectoria Profesional 10, Experiencia Judicial/Jurídica 10.
• Punto en contra: La evaluación de su ética, si bien positiva por sus declaraciones y reconocimientos , carece de detalles específicos sobre el manejo de dilemas éticos complejos en los fragmentos provistos, lo cual es una limitación inherente a la información disponible.

GABRIELA DOLORES RUVALCABA GARCIA

• Calificación Promedio: 9.5
• Argumentos Clave para Alta Valoración: Presenta un perfil académico sobresaliente con Doctorado y Maestría en Derecho Electoral, además de una Maestría en Derecho Constitucional y Amparo, y una especialización en Justicia Constitucional en España. Es una autora prolífica y coordinadora de múltiples libros y artículos especializados en derecho electoral y constitucional, demostrando un profundo dominio técnico. Su trayectoria dentro del TEPJF es extensa y relevante, habiendo sido Secretaria de Estudio y Cuenta en la Sala Superior, Secretaria Instructora en la Sala Regional Guadalajara, y actualmente es Directora de la Escuela Judicial Electoral del TEPJF. Posee un profundo conocimiento del sistema de justicia electoral desde perspectivas jurisdiccionales, académicas y de formación profesional. Su visión de la justicia enfatiza la perspectiva de género e intercultural.
• Calificaciones destacadas: Ética 8, Conocimientos Jurídicos 10, Trayectoria Profesional 10, Experiencia Judicial/Jurídica 10.
• Punto en contra: La evaluación de su ética se basa principalmente en sus declaraciones y la ausencia de información negativa en los fragmentos disponibles , sin evidencia documental específica sobre el manejo de dilemas éticos complejos (limitación inherente a la información disponible).

ENRIQUE BASAURI CAGIDE

• Calificación Promedio: 8.0
• Argumentos Clave para Alta Valoración: Cuenta con una extensa experiencia de siete años como Secretario de Estudio y Cuenta Regional en el TEPJF, donde estuvo directamente involucrado en la elaboración de proyectos de resolución en materia electoral federal. Posee una sólida formación académica, siendo Maestro en Derecho Electoral y Licenciado en Derecho por la Universidad de Guadalajara con excelencia académica. Es miembro de la Carrera Judicial del Poder Judicial de la Federación desde 2009. Ha contribuido intelectualmente como autor de artículos sobre temas electorales y colaborador en un libro sobre nulidades, además de ser un activo ponente y capacitador en la materia. Es fundador de la Academia Mexicana de Profesionales en Derecho Electoral A.C.
• Calificaciones destacadas: Ética 7, Conocimientos Jurídicos 8, Trayectoria Profesional 8, Experiencia Judicial/Jurídica 9.
• Punto en contra: Su experiencia principal en el TEPJF fue en un rol de apoyo técnico-jurídico fundamental, pero no como magistrado titular. La información sobre su trayectoria profesional más reciente (posterior a 2016/2017) no está completamente actualizada en todos los fragmentos disponibles. La evaluación de su ética se basa en su pertenencia a la carrera judicial y la ausencia de información negativa, sin detalles específicos sobre el manejo de dilemas éticos complejos.

This review is part of a series of books I’ve been reading on software development. I selected this book because Domain-Driven Design (DDD) has been a trending topic in the industry in recent years. Similar to previous books I’ve read on coding patterns, this book covers a methodology applied to software development, encompassing coding, software design, and communication between teams.

The primary focus of DDD is effective communication, achieved through two main parts: Strategic and Tactical. Strategic Design addresses questions such as ‘What software are we building?’ and ‘Why are we building it?’ Tactical Design, on the other hand, enables us to write code that reflects the business domain, addresses its goals, and speaks the language of the business domain.

Analyzing Business Domains.

Bossiness Domain is the company’s main area. It’s a service the company provides to its client.

DDD distinguishes between three types of subdomains: core, generic, and supporting. Core subdomain is what a company does differently from its competitors, it is naturally complex and it covers the interesting part of the business. Generic Subdomain are business that all companies are performing in the same way, it is a general solved problem. Supporting Subdomain, Similar to generic subdomain but it doesn’t provide a significant advantage, the problems are obvious with obvious solutions.

A good starting point to identify subdomain is starting with company departments and other organizational units, we can use the definition”subdomains are a set of coherent use cases” as a guiding principle.

Domain experts are either the people coming up with requirements or the software’s end users. The software is supposed to solve their problems.

Discovering Domain Knowledge.

Projects require the collaboration between different roles: domain experts, product owners, engineers, UI and UX designers, project manager, testers analysts and others. DDD proposes to get knowledge from domain expert to software engineers by using an ubiquitous language. The ubiquitous language is the language of the business, it must be precise and consistent, it should eliminate the need for assumptions and should me the business domain logic explicit. For example the term “user” can not be obvious and should can be represented as “user”, “visitor”, “administrator” and“account”.It should be reinforced throughout the project, requirements, test, documentation and source code.

The book recommends the usage of automated tests written in the Gherkin language for capturing the ubiquitous language and act as an additional tool for bridging the gap between domain experts and software engineers.

Managing Domain Complexity.

With the bounded context pattern, the contexts are modeled as an explicit and integral part of the business domain. A ubiquitous language is ubiquitous only in the boundaries of its bounded context, the wider the ubiquitous language the harder is to keep consistency, the smaller the more overhead the design induces.

• Choosing model’s boundaries is a strategic design decision.
• Subdomains are discovered. These are defined by the business strategy.
• Bounded context serve not only as a model boundaries but also as a phisical boundaries of systems implementing them.
• Each bounded context should be implemented as an individual service.
• While subdomains are discovered, bounded context are designed.
• A bounded and its ubiquitous language can be implemented and maintained by one team, no two teams can shared the work on the same bounded context. However, one team can work on multiple bounded context

Integration Bounded Context.

Contracts are the touch-points between bounded contexts.

Partnership model: One team can notify a second team about a change in the API and the second team will cooperate and adapt.

Shared Kernel: Is implemented so that any modification in its source code is immediately reflected in all bounded context using it. Continues Integration is required because the shared kernel belongs to multiple bounded context. The frequently the changes the higher the cost will be.

Customer Supplier: The anticorruption layer pattern address scenarios in which it is not desirable or worth the effort to confirm to the supplier model.
- When the upstream model is inefficient or inconvenient for a customer needs.
- When the suppliers contract change often.
- When the downstream bounded context contains a core subdomain.

Anticorruption layer: The consumer translates the service provider’s model into a model that fits the consumer’s needs.

Open-Host Service: This pattern is often used in combination especially if you are implementing APIs. The format of the API is the “Published Language” and the “Open/Host service” indicates you are exposing this service to other.

Separate Ways: It’s less expensive to duplicate particular functionality than to collaborate and integrate it. This pattern should be avoided when integrating core subdomains.

Context Map.

Context map is a visual representation of the system’s bounded context and the integration between them.

Implementing Simple Business Logic.

Transaction Script.

• A collection of business transactions that consumers can execute.
• Each operation should either succeeded or fail but never result in an invalid state.
• To ensure transactional behavior is to make the operation idempotent: that is, leading to the same result even if the operation repeated multiple times or the use optimistic concurrency control.
• This pattern naturally fits supporting subdomains where, by definition, the business logic is simple.
• Transaction scrips should never be used for core subdomains.
• A Transaction Script organizes all this logic primarily as a single procedure, making calls directly to the database or through a thin database wrapper.
• This patterns is some times consider as an anti-pattern.

Active Record.

An object that wraps a row in a database table or view, encapsulates the database access, and adds domain logic on that data.

• Apart from data structure these objects also implement CRUD operations.
• The objects are coupled to an ORM or some data access framework.
• The pattern’s goal is to encapsulate the complexity of mapping the in-memory object to the database schema.
• This pattern is also known as an anemic domain model anti-pattern. in other words, an improperly desined domain model.

Tackling Complex Business Logic.

Domain Model.

DDD’s tactical patterns — aggregates, value objects, domain events and domain service — are building blocks of such a object model. These patterns share the common theme: they put the business logic first. Objects used on the modeling should not introduce any additional accidental complexities (objects to be plain objects).

Value Objects.

• A value object is an object that can be identified by the composition of its values.
• There is no need to validate the values before the assignment, as the validation logic resides in the value object themselves.
• Value objects expresses the business domain’s concepts: they make the code speak the ubiquitous language.
• The value object removes the need for conventions.
• Compare to an integer-base value, the Height value object makes the intent clear and decouples the measurement from a specific measurement unit.
• Value Objects are implemented as immutable objects.
• Value Objects describe an entity’s properties.

Aggregates.

• An aggregate is an entity: it requires an explicit identification field and its state is expected to change during an instance’s lifecycle.
• The aggregate logic has to validate all incoming modifications and ensure the the changes do not contradict its business rules.
• Its state can only be mutated by executing corresponding methods of the aggregate’s public interface.
• The state-modifying methods exposed as an aggregate’s public interface are often referred to as command.
• An aggregates’s public interface is responsible for validating the input and enforcing all the relevant business rules and invariants.
• It’s crucial to ensure that the database used for storing an aggregate’s data supports concurrency management.
• All changes to the aggregate’s state should be committed transactionally as one atomic operation.
• A change to an aggregate’s state can only be committed individually, one aggregate per database transaction.
• The aggregate ensures that all the conditions are checked against strongly consistent data.
• All information that can be eventually consistent should reside outside of the aggregate’s boundary.
• Aggregates should reflect the ubiquitous language.

Domain Events.

• A domain event is message describing a significant event that has occurred in the business domain.
• Events should be formulated in the past tense.

Domain Service.

• A domain service is a stateless object that implements the business logic.
• Domain services make it easy to coordinate the work of multiple aggregates.
• A stateless object that hosts business logic that naturally doesn’t belong to any of the domain model’s aggregates or value objects.

Modeling the Dimension of Time.

Event-Source Domain.

• The event sourcing pattern introduces the dimension of time into the data model.
• All changes to an aggregates’s state are expressed as a series of domain events.
• The database that stores the system’s event is the only strongly consistent storage: the system’s source of truth.
• The accepted name for the database that is used for persisting events is “event store”.
• The event store should not allow modifying or deleting the events since it’s append-only storage.
• When you append new events you also specify the version of the entity on which you are basing your decisions.
• You can always reconstitute all the past states of an aggregate.
• Event source provides the flexible model that allows for transforming the events into different state representations.
• The persisted domain events represented a strongly consistent audit log of everything that has happened to the aggregates states.

Architectural Patterns.

Layered Architecture.

Layered architecture is one of the most common architectural patterns. It organizes the codebase into horizontal layers, with each layer addressing one of the following technical concern: interaction with the consumers, implementing business logic, and persisting the data.

Ports & Adapters.

The Ports & Adapters architecture addresses the shortcomings of the layered architecture and is a better fit for implementing more complex business logic. The goal of Ports & Adapters is to decouple the system’s logic from its infrastructural components.

By decoupling the business logic from all technological concerns, Ports & Adapters architecture becomes a perfect fit for business logic implemented with the Domain Model pattern.

• The ports & adapters architecture is also know as hexagonal architecture, onion architecture, and clean architecture.
• Application layer = service layer = use case layer.
• Business layer = domain layer = core layer.

Command-Query Responsibility Segregation.

This pattern is based on the same organizational principles for business logic and infrastructural layers as Ports & Adapters. However, it differs in how the system’s data is managed. This pattern enables the representation of the system’s data in multiple persistent models implementing one database for reading (optimized for queries) and another for writing (optimized for commands and transactional consistency).

The CQRS pattern is closely related to event sourcing.

• Proper implementation of CQRS allows for wiping out all data of a projection and regenerating it from scratch.
• The system can define as many models as needed to present to users or supply information to other systems: it is called projections or read models.
• A command should always let the caller know whether it has succeeded or failed.
• The CQRS pattern can be useful for applications that need to work with the same data in multiple models, potentially stored in different kinds of database.

Communication Patterns.

For stateless model translation, the bounded context that owns the translation (OHS for upstream, ACL for downstream) implements proxy design pattern to inject the incoming and outgoing request and map the source model. There are two types of stateless models synchronous and asynchronous. Asynchronous models can use an API gateway pattern to managing and serving multiple versions of the bounded context. Asynchronous models can implement a message proxy.

A stateful translation may be require when the translation mechanism has to aggregate the source data or unify data from multiple sources into a single model. You can use off-the-shelf products such as stream-process platform (Kafka, AWS Kinesis, etc.), or a batching solution (Apache NiFi, AWS Glue, Spark, etc.)

Outbox

The outbox pattern ensures reliable publishing of domain event using the following algorithm.

1. Both the updated aggregate’s state and the new domain events are committed in the same atomic transaction.
2. A message relay fetches newly committed events from the database.
3. The relay publishes the domain events to the message bus.
4. Upon successful publishing, the relay either marks the event as published in the database or deletes them completely.

Saga

The saga pattern orchestrates a multicomponent transaction, the states of the involved components are eventually consistent.

Only the the data within an aggregate’s boundaries can be considered strongly consistent. Everything outside is eventually consistent.

The saga pattern is often confused with another pattern: process manager. Although the implementation is similar, these are different patterns. If a saga contains if-else statements to choose the correct course of action, it is probably a process manager.

Design Heuristic

When designing bounded contexts, start with wider boundaries. If required, decompose the wide boundaries into smaller ones as you gain domain knowledge.

Microservices.

A service is a mechanism that enables access to one or more capabilities, where the access is provided using any mechanism for getting data in or out of a service. It can be synchronous, such as a request/response model, or asynchronous, such as a model that is producing and consuming events.

Micro-services encapsulate their databases. The data can only be accessed through a much more compact, integration-oriented public interface.

• The stronger the aggregate’s relationship is with the other business entities of its subdomain, the shallower it will be as an individual service.
• The coherent nature of the use cases contained in a subdomain also ensures the resultant module’s depth.
• From a system complexity standpoint, a deep module reduces the system’s global complexity.
• Shallow services are also the reason why so many micro-services-oriented projects fail.

The micro-services and bounded context patterns have a lot in common, so much so that the patterns are often used interchangeably. Microservices are indeed bounded contexts. Although microservices are bounded contexts, not every bounded context is a microservice.

Event-Driven Architecture.

Event-driven architecture is an architectural style in which a system’s components communicate with one another asynchronously by exchanging event messages.

Event: A message describing a change that has already happened.

Command: A message describing an operation that has to be carried out.

• Event notification: A notification that something important has happened, but requiring the consumer to query the producer for additional information explicitly.
• Event-carried state transfer: A message-based data replication mechanism. Each event contains a snapshot of a state that can be used to maintain a local cache of the producer’s data.
• Domain events: A message describing an event in the producer’s business domain.
• When operating large data structures, it may be reasonable to include in the ECST message only the fields that were actually modified:
• Instead of querying the data sources each time the data is needed, all the data can be cached locally.
• Domain events include all the information describing the event. The consumer does not need to take any further action to get the complete picture.
• The driven in event-driven architecture means your whole system depends on successful delivery of the messages.
• Use the outbox pattern to publish message reliably.
• When publishing messages, ensure that the subscribers will be able to deduplicate the messages and identify and reorder out-of-order messages.
• Leverage the saga and process manager patterns when orchestrating cross-bounded context process.

Assuming the worse:

• The network is going to be slow.
• Servers will fail at the most inconvenient moment.
• Events will arrive out of order.
• Events will be duplicated.

Data Mesh

OLAP models ignore the individual business entities and instead focus on business activities by modeling fact tables and dimension tables.

Fact Table: Represent business activities that have already happened. Fact records are never deleted or modified: analytical data is append-only data. The only way to express that current data is outdated is to append a new record with the current state.

Dimension Table: Are designed to describe the facts attributes and are referenced as a foreign key from a fact table to a dimension table.

Star schema: Each dimension record is used by many facts; a fact’s foreign key points to a single dimension record.

The snowflake schema: The dimensions are multilevel, each dimension is further normalized into more fine-grained dimensions.

Data Warehouse.

The data warehouse (DWH) architecture is relatively straightforward. Extract data from all of the enterprise’s operational systems, transform the source data into an analytical model, and load the resultant data into a data analysis–oriented database: ETL scripts.

In some cases, the transformation may require temporary storage for the incoming data. This is known as the staging area.

Data Lake.

A data lake–based system ingests the operational systems’ data. However, instead of being transformed right away into an analytical model, the data is persisted in its raw form, that is, in the original operational model.

A data lake–based system ingests the operational systems’ data. However, instead of being transformed right away into an analytical model, the data is persisted in its raw form, that is, in the original operational model.
Eventually, the raw data cannot fit the needs of data analysts. As a result, it is the job of the data engineers and the BI engineers to make sense of the data in the lake and implement the ETL scripts that will generate analytical models and feed them into a data warehouse.

Data Mesh.

The data mesh architecture is, in a sense, domain-driven design for analytical data. The data mesh architecture is based on four core principles: decompose data around domains, data as a product, enable autonomy, and build an ecosystem.

Each bounded context now owns its operational (OLTP) and analytical (OLAP) models. Consequently, the same team owns the operational model, now in charge of transforming it into the analytical model.

The ubiquitous language and the resultant domain knowledge are essential for designing analytical models.

The data as a product principle calls for treating the analytical data as a first-class citizen.

The primary principle of DDD is to organize the system into distinct domains, facilitating adaptability to changes and improving communication efficiency between teams. Throughout the book, various design solutions are explored in relation to DDD, with a focus on utilizing the ubiquitous language as the cornerstone of domain-driven design.

This book opened my eyes to various strategies for storing data, designing systems, and communicating between different components. The content is incredibly easy to read and is accompanied by numerous illustrations that enhance understanding of the topics. Additionally, the book contains references to other works, which complement the information provided. While Domain-Driven Design (DDD) is a methodology not tied to a specific programming language, the book emphasizes the usage of Object-Oriented Programming (OOP) and many online courses predominantly use Java.

Last year, I found myself with plenty of free time to engage in various activities, and though I wasn’t heavily focused on coding, I decided to commit to a personal challenge: solving 150 code problems. Despite enjoying coding and the satisfaction of solving challenges independently, the primary goal was to become familiar with a broad range of code problems, identify patterns, and gain proficiency in solving various types of challenges. This exploration allowed me to make informed decisions about whether I truly wanted to master specific fields by tackling additional code problems. It’s worth noting that my background lies in being a Software Backend Engineer.

Code Challenges in an Interview

Solving code challenges is not something new for me; it’s a common aspect of software engineer interviews. I’ve been practicing with easy problems for a while, mostly related to arrays and hash-maps, which are the most common. In many interviews, companies require you to solve easy code challenges, and if completed, they may you require to solve a medium-level problems. While code challenges aren’t the main focus of a software interview, many companies use them as a primary filter. There’s an ongoing debate about this, as proficiency in solving code challenges doesn’t always correlate with real-world coding abilities and experience in the field. Recently, I’ve observed a shift where more companies ask candidates to develop small applications within a short timeframe, shareable via GitHub or a zip file. This approach may better assess a developer’s ability to recognize patterns in a system, write clean code, and adhere to best practices in software development.

Complexity.

When solving a code challenge, optimization is a crucial criteria. There are various ways to solve the same problem, and being able to provide the most efficient solution is expected. The algorithm’s complexity is often measured by Big O Notation. During interviews, it is common to indicate both the space and time complexity of your algorithm. Linear complexity, O(n), is typically associated with simpler code challenges.

About LeetCode.

Many websites offer code challenges, but the ones I’ve personally liked and tried are listed below.

• https://leetcode.com/
• https://www.hackerrank.com/
• https://www.geeksforgeeks.org/

LeetCode stands out as one of the most popular platforms, boasting a large and collaborative community where users often assist each other with code problems and offer recommendations for interviews at leading companies like Apple, Amazon, Google, Microsoft, Meta, and more. LeetCode’s paid plan even allows users to simulate real interviews for these top companies. The platform hosts weekly global contests, drawing an impressive number of participants eager to take on these challenges.

https://clist.by/resource/leetcode.com/

Mexico was in the position 22 with this guy (Tlatoani) leading the board.

The Language.

I didn’t find a chart for top programming languages used in Leetcode, however I would say that Python is the most popular due to its flexibility and human readability. However, I have seen a lot of submissions Java and C++ too, I believe most of these people use these languages for performance purposes.

My profile.

https://leetcode.com/isidroamv/

I’ve tackled around 150 problems, solving about 80% or 85% independently. Some challenges demanded hours of effort, while others led me to give up after multiple attempts, especially those involving dynamic programming and graphs. My primary language was Python, with occasional use of Java. This is the study plan I took. https://leetcode.com/studyplan/top-interview-150/

Tips for code challenges.

Minimize the number of check conditions in the loop.

# This code has 2 checks in the loop
def find_max_number(arr):
    if not arr:
        return None
    result = None    
    for num in arr:
        # 2 checks in the loop
        if result is None or num > result:
            result = num
    return result


# The previous code can be improved by reducing the checks to 1
def find_max_number(arr):
    if not arr:
        return None
    result = arr[0]
    for num in arr[1:]:
        # 1 check in the loop
        if num > result:
            result = num
    return result


# Another alternative if is initialize the code the the inf values
def find_max_number(arr):
    if not arr:
        return None
    result = float('-inf')
    for num in arr:
        # 1 check in the loop
        if num > result:
            result = num
    return result

The usage of Set.

Sets are less commonly used than arrays in software development, but their usage can be highly beneficial as they automatically eliminate duplicates from a collection. Consider the following example that reduces complexity from O(nˆ2) to O(n).

# The complexity of this is O(nˆ2)
def find_duplicates(arr):
    duplicates = []

    for i in range(len(arr)):
        for j in range(i + 1, len(arr)):
            if arr[i] == arr[j] and arr[i] not in duplicates:
                duplicates.append(arr[i])

    return duplicates

# The usage of set reduce the complexity to O(n)
def find_duplicates(arr):
    seen = set()
    duplicates = set()
    
    for num in set(arr):
        if num in seen:
            duplicates.add(num)
        else:
            seen.add(num)

    return list(duplicates)

Binary Search

The Binary Search algorithm is a crucial topic on LeetCode, offering exceptional efficiency for searching values in ordered lists. Understanding this algorithm is highly important, as its efficiency is commonly applied in real-world software development. Based on the concept of dividing the array in half and searching in a specific section, this algorithm is widely discussed in numerous online articles. The following algorithm is basic example of a binary search.

def binary_search(arr, target):
    # Set pointers at the beginning and end of the array
    low, high = 0, len(arr) - 1
    
    # Continue until the pointers meet
    while low <= high: 
        # Calculate the middle position - important to rememeber this formula
        mid = (low + high) // 2 
        
        if arr[mid] == target:
            # Target found, return its index
            return mid  
        elif arr[mid] < target:
            # Search the right half
            low = mid + 1  
        else:
            # Search the left half
            high = mid - 1  
    
    # Target not found in the array
    return -1

Slow and Fast

Employing a 2-pointer strategy in a linked list is a valuable approach. The concept is simple: the slow pointer advances by one, and the fast pointer advances by two. As long as the fast pointer is not null, you can implement logic for the slow pointer. For instance, the following code checks for duplicate values in a linked list.

def has_cycle(head):
    # Check if the linked list is empty or has only one node
    if not head or not head.next:
        return False  # No cycle in this case

    # Initialize slow and fast pointers
    slow = head
    fast = head.next

    # Iterate through the linked list
    while fast and fast.next:
        # Check if slow and fast pointers meet, indicating a cycle
        if slow == fast:
            return True  # Cycle detected

        # Move slow one node per iteration
        slow = slow.next
        # Move fast two nodes per iteration
        fast = fast.next.next

    return False  # No cycle found

DFS (Depth First Search) with data in memory

Depth-First Search (DFS) is a widely-used algorithm for traversing data structures like trees or graphs. It starts from the root node, explores each branch’s edges before backtracking. To prevent duplicate values in the result, an array is used to store already visited values in memory. While this algorithm may take various forms, a basic structure can be visualized in the following example:

def generate_combinations(characters, length):
    def dfs(length, current_combination, seen):
        # Base case: If the desired length is achieved, add the current combination to the result
        if length == 0:
            all_combinations.append(''.join(current_combination))
            return

        # Explore all possible characters
        for char in characters:
            # Check if the character is not already used in the current combination
            if char not in seen:
                current_combination.append(char)
                # Mark the character as visited
                seen.add(char)
                # Recursively explore combinations with the reduced length
                dfs(length - 1, current_combination, seen)
                # Backtrack: Remove the last character to explore other possibilities
                current_combination.pop()
                # Release the character from the visited set for future exploration
                seen.remove(char)

    # Initialize the result list and start the depth-first search
    all_combinations = []
    dfs(length, [], set())
    return all_combinations

Dynamic Programming.

Dynamic programming is a powerful algorithm that enhances code performance by reusing previously calculated solutions, often stored in an array. A classic example is a coin change problem, where it efficiently counts the ways to make change.

def count_ways_to_make_change(coins, amount):
    # Initialize an array to store the results of subproblems
    dp = [0] * (amount + 1)
    
    # There is one way to make change for amount=0, i.e., using no coins
    dp[0] = 1

    # Iterate over each coin and update the table
    for coin in coins:
        # Iterate from the coin value to the target amount
        for i in range(coin, amount + 1):
            # Reuse the already calculated problem to update 
            # the number of ways to make change 
            dp[i] += dp[i - coin]

    return dp[amount]

There are a bunch of cool algorithms out there, like bit manipulations, HashMaps (super common), Trie, min heap, max heap, math tricks, hashing, sorting, and more. However, the algorithms I described are the ones I’ve encountered frequently and found them interesting. I see solving coding challenges as a creative process that requires a solid foundation in algorithms. While I won’t be focusing as much on this topic in the coming months, I’ve enjoyed the process of solving code challenges.

This year, I made a commitment to delve into more than 10 books centered around Software Engineering. “Head First Design Patterns” is the second book I’ve chosen to explore, as it addresses fundamental aspects of software development. Despite encountering these patterns in various projects throughout my career, I haven’t delved into the details of pattern design. Additionally, I haven’t had the chance to read a “Head First” book before. This seemed like the perfect opportunity to dive into both areas.

Similar to other Head First books, the content is presented in an easily digestible manner, incorporating jokes, images, and puzzles. Key phrases are reiterated in various ways, enhancing your brain’s ability to grasp the underlying concepts effortlessly. The book encourages the readers to solve puzzles and participate in activities. Inspired by this interactive approach, I’ve decided to transcribe the Java code from the book into TypeScript code.

Here are some notes I took and the typescript code.

Identify the aspects of your application that vary and separate them from stays the same

Program to an interface not an implementation. Favor composition over inheritance.

The Strategy Patter: Defines a family of algorithms, encapsulate them and makes them interchangeable. Strategy let’s the algorithm vary independently from clients that use it.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%201

// Strategy and Composition Pattern example
const d = new RuberDuck();
// Use Composition Pattern implemented in the Duck class to perform behavior
d.performFly(); // Output: "I'm flying with a rocket!"
d.performQuack(); // Output: "Quack"

// Use Strategy Pattern to change behavior
d.flyBehavior = new FlyNoWay();
d.performFly(); // Output: "I can't fly :("


// Strategy Pattern example
const k = new King();
k.fight(); // Output: "I'm using a knife"

k.weapon = new SwordBehavior();
k.fight(); // Output: "I'm using a sword"

Patterns allows you to say more with less. When you use a pattern in a description other developers quickly know precisely the design you have in mind.

There are some object-oriented principles that underline the patterns and knowing these will help you to cope when you can’t find a pattern that matches your problem.

One of the secrets to create maintainable OO System is thinking about how they might change in the future, the pattern design address those issues. Change is constant in software development.

The Observer Pattern defines a one-to-many dependency between objects so that when one object changes state, all of its dependents are notified and updated automatically.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%202

// Client code for Observer pattern

const weatherData = new WeatherData();
const cd = new CurrentConditionsDisplay(weatherData);

// Simulate measurements
// The WeatherData object will notify all observers when measurements change
weatherData.setMeasurements(80, 65, 30.4); // Output: 80F degrees and 65% humidity
weatherData.setMeasurements(82, 70, 29.2); // Output: 82F degrees and 70% humidity

Loosely coupled: Objects can interact, but they typically have very little knowledge of each other. Strive for loosely coupled designs between objects that interact.

Classes should be open for extensions, but closed for modifications.

The decorator pattern attaches additional responsibilities to an object dynamically. Decorator provides a flexible alternative to subclassing for extending functionality.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%203

// Client code for the decorator pattern

let beverage1: Beverage = new HouseBlend(); // Make a HouseBlend object
beverage1.size = Size.TALL;

beverage1 = new Soy(beverage1); // Decorate it Wraping it with Soy
beverage1 = new Soy(beverage1); // Decorate it Wraping it in a second Soy
beverage1 = new Mocha(beverage1); // Decorate it Wraping it with Mocha
beverage1 = new Whip(beverage1); // Decorate it Wraping it with whip

console.log(beverage1.description + " $" + beverage1.cost.toFixed(2));

The factory method pattern defines an interface for creating an object but let’s subclasses decide which class to instantiate.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%204

// Client code for factory method pattern

const nyPizza = new NYPizzaStore();
const chicagoPizza = new ChicagoPizzaStore();

let pizza = nyPizza.order("cheese");
console.log("Ethan ordered a " + pizza.name + "\n");

pizza = chicagoPizza.order("veggie");
console.log("Ethan ordered a " + pizza.name + "\n");

Depend upon abstractions. Do not depend upon concrete classes.

A “High-level” (abstract operations)component is a class with behavior in terms of other “Low-level” components. High-level components should not depend on our low-level component, rather, they should both depend on abstractions.

Dependency inversion variations:

• No variables should hold a reference for a concrete class.
• No class should derive from a concrete class. (It should derive from abstractions).
• No method should override an implemented method of any of its base class.

The abstract Factory pattern provides an interface for creating families of related or dependent on objects without specifying their concrete classes.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%204

// Client code for Abstract Factory patterns

import { NYPizzaStoreV2 } from "./AbstractFactory";

// Abstract Factory pattern example
const nyPizzaStore = new NYPizzaStoreV2();
nyPizzaStore.order("pepperoni");

Singleton — Ensure a class only has one instance and provide a global point of access to it.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%205

// Client code for Singleton pattern

const boiler = ChocolateBoiler.getInstance();
boiler.fill();
boiler.boil();
boiler.drain();

if (boiler === ChocolateBoiler.getInstance()) {
    console.log("Singleton works, both variables contain the same instance.");
}

The command pattern encapsulates a request as an object, thereby letting you parameterize other objects with different request, queue or log requests and support undoable operations.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%206

// Client code for Command Pattern

const remote = new RemoteControl();
const light = new Light();
const garageDoor = new GarageDoor();
const stereo = new Stereo();

remote.setCommand(0, new LightOnCommand(light), new LightOffCommand(light));
remote.buttonWasPressed(0);
remote.undoButtonWasPressed();
remote.setCommand(1, new GarageDoorOpenCommand(garageDoor), new GarageDoorCloseCommand(garageDoor));
remote.buttonWasPressed(1);
remote.setCommand(2, new StereoOnWithCDCommand(stereo), new StereoOffCommand(stereo));
remote.buttonWasPressed(2);
remote.buttonWasPressed(5);

Adapter lets classes work together that couldn’t otherwise because of incompatible interfaces.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%207

// Client code for adapter example

const duck = new MallardDuck();
const turkey = new WildTurkey();
const turkeyAdapter = new TurkeyAdapter(turkey);

duck.fly();
duck.quack();

turkeyAdapter.fly();
turkeyAdapter.quack();

Facade defines a higher-level interface that makes the subsystem easier to use.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%207

// Client for Template Pattern

const tea = new Tea();
const coffee = new Coffee();

tea.prepareRecipe();
coffee.prepareRecipe();

The Hollywood principle: Don’t call us, we call you. A technique for creating a design that allow low-level structures to interoperate while preventing other classes from becoming too dependent on them.

Template method lets subclasses redefine certain steps of an algorithm without changing the algorithm structure.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%208

// Client code for a Template Pattern 

const tea = new Tea();
const coffee = new Coffee();

tea.prepareRecipe();
coffee.prepareRecipe();

The iterator pattern provides a way to access the elements of an aggregate object sequentially without exposing its underlying representation.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%209

// Correct implementation of the iterator pattern
const menu1 = new DinnerMenuIterator([
    new MenuItem2("Vegetarian BLT", "(Fakin') Bacon with lettuce & tomato", true, 2.99),
    new MenuItem2("BLT", "Bacon with lettuce & tomato", false, 2.99),
]);

const menu2 = new CafeMenuIterator({
    breakfast: new MenuItem2("Pancakes", "Pancakes with scrambled eggs, and toast", true, 2.99),
    lunch: new MenuItem2("Soup of the day", "Soup of the day, with a side of potato salad", false, 3.29),
});

const menu = new WaitreesMenu(menu1, menu2);
menu.printMenu();

A class should have only one reason to change.

Composite compose object into tree structures to represent part-whole hierarchies. Composite let’s clients treat individual objects and compositions of objects uniformly.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%209

// Client code, using the composite design pattern with submenus

const pancakeHouseMenu = new Menu("PANCAKE HOUSE MENU", "Breakfast");
const dinerMenu = new Menu("DINER MENU", "Lunch");
const cafeMenu = new Menu("CAFE MENU", "Dinner");
const dessertMenu = new Menu("DESSERT MENU", "Dessert of course!");

const allMenus = new Menu("ALL MENUS", "All menus combined");
allMenus.add(pancakeHouseMenu);
allMenus.add(dinerMenu);
allMenus.add(cafeMenu);


dinerMenu.add(new MenuItem3("Pasta", "Spaghetti with Marinara Sauce, and a slice of sourdough bread", true, 3.89));
dessertMenu.add(new MenuItem3("Apple Pie", "Apple pie with a flakey crust, topped with vanilla ice cream", true, 1.59));
dinerMenu.add(dessertMenu);

const waitress = new Waitress(allMenus);
waitress.printMenu();

State allows an object alter its behavior when its internal state changes. The object will appear to change its class.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%2010

// Client code using the state pattern

const gumballMachine = new GumballMachine(1);
gumballMachine.insertQuarter();
gumballMachine.ejectQuarter();
gumballMachine.turnCrank();

gumballMachine.insertQuarter();
gumballMachine.turnCrank();

gumballMachine.insertQuarter();
gumballMachine.turnCrank();

gumballMachine.refill(2);

Proxy provide a surrogate or placeholder for another object to control access to it.

• https://github.com/isidroamv/design-patterns-typescript/tree/main/Chapter%2011

// Client code using the proxy pattern

const youTubeService = new YouTubeLib();
const youTubeProxy = new CachedYouTubeLib(youTubeService);
const manager = new YouTubeManager(youTubeProxy);

// The first attempt gets the data from the youTubeService
manager.reactOnUserInput();

// The second attempt gets the data from the cache
manager.reactOnUserInput();

In general, the book has delve into various patter designs in a easy manner. However, some examples in the book appear kind somewhat outdated, as the first publication took place around 20 years ago. For instance, consider the Proxy pattern, initially proposed for Remote Method Invocation (RMI), a protocol that is not widely used today. Nevertheless, the same Proxy pattern can be effectively applied to interact with modern REST applications.

Book: https://www.goodreads.com/book/show/58128.Head_First_Design_Patterns

Repository: https://github.com/isidroamv/design-patterns-typescript

This year I finished reading this book as part of my plan to read more books about Software Architecture. The book was written by Lee Atchison, it was first publish on 2016 and it covers in a simple manner multiple topics for scaling software.

I recommend this book for people who are starting learning about Software Architecture or you if your are looking for some recommendations when you are scaling your organization. This book you covers topics like strategies to mitigate risk, measure availability, SLA, the use of Tiers and strategies to prevent risk.

Within this summary, I have encapsulated insights and key takeaways that hold particular significance for my journey and understanding of software architecture

Mitigate Risk

Risk Management: How much risk is accepted in a given project.

Risk Mitigation: A plan defined when an error happens.

Risks

• Server will crash.
• Database will became corrupted.
• Response will be incorrect.
• Network connection will fail.
• Deployed piece will fail.

Monitoring

• Server monitoring.
• Configuration changes monitoring.
• Application performance monitoring.
• Synthetic testing ( Simulate a normal user flow).
• Alerting (Identify trend and outliers).

Define way to respond to issues.

• Establish a process to help to diagnose issues.
• The owner should be alerted first, then the other teams that depend on the service.

Measure Availability

+--------+-------------+-----------------+
| Nines  | Percentage  | Monthly Outage  |
+--------+-------------+-----------------+
|   2    | 99%         | 432 Minutes     |
|   3    | 99.9%       | 43 Minutes      |
|   4    | 99.99%      | 4 Minutes       |
|   5    | 99.999%     | 26 Seconds      |
|   6    | 99.9999%    | 2.6 Seconds     |
+--------+-------------+-----------------+

• 3 Nines are commonly accepted for a basic web application, (43 minutes down per month).
• You should monitor the availability percentage and report the results.
• Use tiers from 1 to 4 to assess the importance level of a service.
• You should never perform manual operations on production.
• Test your changes before implement them.
• If a task is repeatable it is a high candidate to be automated.
• Automate deploys and never accept bypass the configuration management system
• Have a record of changes in your system and implement it automated change sanity testing.

Improve your system

This matrix is document that you can use as reference to mitigate the risks identified in your system. This matrix can be use one per team for big companies or just one matrix document for the entire company for small companies. You should maintain this document updated and remove the worst offenders (It is recommended to review monthly and updated every time you note a new risk).

This matrix should be populated this table with the information from: Dev team, Support, feature backlog, technical debt, business owners, performance, system and process.

• The significance of a risk is the combination of the severity of the risk happening with the likelihood of it happening.
• A mitigation plan is a plan for how you are going to put in changes that are designed to either reduce the severity of the risk or reduce the likelihood.
• Low likelihood/ Low severity don’t need to be mitigated.

Recovery Plan

• You should have a plan when a external disaster affect your system (Disaster recovery plan).
• It should be part of the culture to regularly test the recovery plan and other risk.
• Game day is a test strategy that invoke failures and see how the team respond to it (Usually in dev environment). You can use control actions to test on production.

Your recover plan should contain:

• Details of what must be happening that would trigger the recovery plan to be implemented.
• The list of actors that need to be involved in implementing the recovery plan.
• Step-by-step instructions for implementing the recovery plan, and which actor should execute those steps.
• Management, escalation, and notifications that need to be informed.
• Required follow-up that must happen after the problem is resolved.

Redundancy

• Design your app to run in multiple servers.
• Design your app to run in independently tasks.
• Design your app to run in parallel tasks.
• Localize the state into specific areas. (develop stateless preferable).
• Utilize idempotent interface.

Self Repair Strategies

• A load balancer that reroutes traffic to a new server when a previous server fails.
• A “hot standby” database that is kept up to date with the main production database.
• A service that retries a request if it gets an error, anticipating that perhaps the original request suffered a transient problem.
• A queuing system that keeps track of pending work so that if a request fails, it can be rescheduled to a new worker later.

Microservices.

• The teams can focus on the specific scaling and availability requirements of their system.
• Complexity localization: You can think about services as black boxes.
• Service-based architectures are easier to test.
• Microservice should have a contract (API) and Service Level Agreement (SLA).
• Your system can be splited into microservices when the business requirements are different, you can separe the ownership, the date is separable, it contains shared capabilities.
• No more than 8 developer per microservices is recommended.
• A single team can operate more than one service.

Determining Failures

• The response was not understandable.
• The response indicate a fatal error.
• The result is out of the expected bounds.
• Response did not arrive.
• The response was slow in arriving.
• Circuit breaker pattern can be implemented to notify the issue.

Appropriated actions.

• Graceful degradation: Reduce the features of your service.
• Graceful backoff: Show a different alternative for your users.
• Fail early as possible: Don’t call other services if you already detect the error.
• Provide service limits (such as pagination).

Scaling applications.

• You should always have a backup plan for recovering from a mistake.
• Thread your backup and redundant system just preciusly as you treat your primary system.
• 1 extra node will handle traffic but will not handle a not failure.
• 2 extra nodes will handle failure but will not handle upgrade or maintainance.
• 3 extra nodes will handle multiple failures while other nodes are down for maintainance.

Service Tiers.

Tier 1: A service is considered Tier 1 if a failure of that service will result in a significant impact to customers or to the company’s bottom line.

Tier 2: A service that affect your backend business processes in significant ways, but might not be directly noticeable to your customers.

Tier 3: A service that can have minor, unnoticeable, or difficult-to-notice customer impact, or have limited effect on your business and systems.

Tier 4: A service that when it fails, causes no significant effect on the customer experience and does not significantly affect the customer’s business or finances.

Service Level Agreements (SLA).

• SLA are about building trust in a highly distributed in a scalable way.
• You should have SLA in critical areas of your business.
• You should have a dashboard to monitor your SLA.
• SLA should be part of your language when talking with other teams.
• SLA can be measure by: call latency, traffic volume, uptime, error rates, latency groups.

Continue Improvement

• The sooner we consider scalability in the lifecycle of an application the easier it will be to scale.
• Move your system to a distributed ownership model.
• Use stateless servers so the service can manage no data and state for their own.
• Use functional partitioning to split your dataset base on functional lines.
• Choosing your partition key is critical, in general, account name or account id is always a bad partition key. A better partition key would be one that result in consistently sized as much partition as possible.

Distributing the cloud.

• In AWS, the goal is to make access between any server within a region without concerning for the AZ.
• If your application wants to be in multiple regions multiple copies of the application are typically run independently, one copy within each region is desired.
• Two EC2 instances created in different account may or may not be in the same data center, even if the AZ is different.
• Make sure you maintain a redundant components in distinct AZ within a single account. If you have redundant components that are in multiple accounts, make sure you maintain redundancy in multiple AZ within each account individually.
• Dynamic containers are great for easy deployment of complex app in a microservice base application.
• Microcompute is optimized for high volume data streaming and event processing.
• Lambda removes the concerns around scalability. It gives you virtually unlimited scalability within the ability to pay at a subsecond-metered level.
• A common use for lambda is image upload (event processing), API gateway integration.
• Lambda is very good ay handling massive scale loads without the need to increase the amount of infrastructure allocated in your application.

You can find the book here: https://www.goodreads.com/book/show/27560189-architecting-for-scale

Recently I was involved in a typescript project that was configured as mono repo. The objective was to relocate the “example-package” from the existing workspace, as illustrated in the following example:

Initially, it’s crucial to note that when relocating your package outside the workspace, you have the advantage of not needing to include dependencies directly in your package.json. Instead, consider importing them directly into your files as needed.

{
  "dependencies": {
    // Don't import using the workspace protocol
    "@my-org/utils": "workspace:^"
    // Don't import using local path
    "@my-org/utils": "./.."
  }
}

If you attempt to import the a workspace package out of the workspace using and explicitly path like ./../packages/module-b where module-b belongs to the workspace you will get an error. This error indicates that Yarn cannot recognize the workspace structure. To resolve this issue, you should use the path relative to the root workspace package.

➜  examples yarn
➤ YN0000: ┌ Resolution step
➤ YN0013: │ @ts-workspace/module-a@file:./../packages/module-b#./../packages/module-b::hash=e6
➤ YN0001: │ Error: @ts-workspace/module-a@workspace:^: Workspace not found (@ts-workspace/module-a@workspace:^)
    at ze.getWorksp

When you import a package using a local path (e.g. ./../packages/module-b) yarn makes a copy of the entire folder including the node_modulesfolder and files that are listed in the .gitignore. This implies that if you have large files, hidden files, or data generated during the build process, Yarn will also move those files into your new package outside the workspace.

// If your files are too big to be process by yarn you will see an error like this:
➤ YN0000: ⠸ libqp@npm:2.0.1

// And then the following error
.: Couldn't allocate enough memory
 at li.allocateBuffer (/mypath/.yarn/releases/yarn-3.2.3.cjs:314:22707)

Solution 1: A possible solution for this error is to increase the memory space for node. E.g. export NODE_OPTIONS="--max-old-space-size=8192" .

Solution 2: Another option is to use the remote repository path so can avoid dealing local packages. The disadvantage of this approach is that you need to release packages to be available remotely.

*Solution 3: The recommended and optimal solution is to leverage the workspace and directly import packages into your files, like this: import { multiply } from "@ts-workspace/module-b". It's important to ensure that an index.ts file exists at the root of your module; otherwise, you may encounter issues. Additionally, note that there's no need to add dependencies in your package.json file under the dependencies section. Simply importing the modules within your files suffices.

Usually, when working with typescript you need to compile your files into the dist folder this make the package more compatible with third party packages. The following configuration is needed.

// File structure
package-b/
|-- dist // auto generated folder
|-- index.ts // Make sure your index.ts exists
|-- tsconfig.json
|-- package.json


// package.json
{
    "main": "dist"
}


// tsconfig.json
{
    "compilerOptions": {
        "outDir": "dist",
    }
}

So you can import a function from thepackage-b in your file out of the workspace like this:

import { multiply } from "@ts-workspace/module-b";

console.log(multiply(2, 9));

Check this repository as an example.

I recently finished reading the book “Letters from Thailand” from Botan, it is an old novel written in 1969 about a Chinese guy who moved to Bangkok Thailand looking for better opportunities. This is not a happy story nor a sad story I felt it more like a raw reality. This book was recommended by a Thai person with Chinese ascendance who confirmed some facts about the book.

I have decided to write a quick analysis because few books grab my attention like this one and it touches on interesting topics such of values, raising a family, racism, immigration, temptations, modernization. The way the the book is written is even more interesting since these are only letters that Suang U wrote to his mother during 20 years, so reading the letters feels like entering to the author’s mind and feel the same feeling he has. It makes me remember the “The Diary of a Young Girl” by Anne Frank which also made me feel like reading the mind of a young girl.

Spoiler Alert ⚠️ ⚠️ ⚠️. Don’t continue reading if you don’t want to know details about the book.

The story starts with a disclaimer saying the book you will read has sensitive details, since the book was written in the form of letters by a normal human you must read the book from an open mind perspective. Also, it mentioned that these letters were never delivered to Suang’s mother, it is supposed that the letters were written in Chinese and translated to Thai by the Author, Botan. However, when reading the book you can notice these are not simple letters written by a normal person because it has many details that make you imagine the scenario where the characters interact, and when Suang U writes about another person’s behavior, he is so detailed most of the time that you can notice that his writing is not misled by his mental bias.

In the firsts letters, Suang mentioned that he left his home in Po Leng Village because he didn’t want a life on a farm for the rest of his life, he was bored with a monotonous life and didn’t earn much money there. The difference between him and the rest of the guys was that his mother taught him to read and write Chinese it and his good behavior is adopted by a prosperous Chinese merchant (Yong Chua).

In this first part I felt the feelings of a rebel boy thinking to do something meaning for his life, taking with him family values and the teachings from his mother (writing) but and the same time really regretted about living his family, maybe that is the reason he writes the letters for so long. His “father”, Yong Chua, lost their family in a big flood years ago so he wanted to meaningful for someone and have descendants, not the ones that have that same blood but the ones that remembers you when your are death. In this section I saw the importance of family links and the importance about the things even when your are dead, so that people venerate your death which is the opposite to some school of thought that says live your life now because there is nothing after the death.

When Suang arrived to Thailand the author describes really detailed the environment, the weather, the sun, the people, the food, the clothes. Suang U started worked on as bookkeeper with Nguan Thong (Yong Chua’s friend and colleague). Nguan Thong had 2 daughters (Mui Eng and Ang Buai), Mui Eng was more beautiful and elder than Ang Bui which was not as much beautiful but she was really energetic. I believe the girls were around 12–14 years old and Suang U was around 16 or 17 years old. The girls were not thinking in getting married they wanted to continue studying and work in their father’s business. After some conflicts they ended up married and went to live together. Mui Eng’s father died but at least he was able to see his grandson (Suang’s son).

These first letters are really exciting to read because a lot of things happen in a short period, you see how they fall in love, got married, and had their first son.

Suang U.

In the letters, you can see how Suang’s “fathers” and Chinese society living in Bangkok influenced the mind of Suang U. They call their laborers coolies too and say that Thai people only like gambling, getting drunk, kids are half naked on the streets and don’t care about business and many other things that indirectly make you see how Chinese look down to Thai.

Suang U grew up in a place where Chinese looked down to Thais, he wanted to keep their values, believes and culture in a place that was not his country but a community there. He didn’t care about patrioty or war he was only thinking in business and his family. The most important thing for him was his sun that he tried to rise him in the best manner and Chinese way possible.

All the abundance he had in his life once vanished, his children got married and he can not live him them under different circumstances. I think the most disappointing thing in his life was that his son didn’t become the boy he wanted and the daughter that he hatted the most became the most important for him. At the end Suang U, starts accepting that Thais are not different than Chinese.

Mui Eng

Mui Eng was as not as energetic as her sister Ang Buai, and before meeting Suang he was thinking to continue with his father’s business. She didn’t want to have many children and she didn’t care about having a girl or a boy. At the begging and before of his marriage she didn’t get along with her sister her character became more dramatic (maybe from Suangs perspective). The love they had each other vanished the first years of marriage and she became more dependent on Suang’s decisions. I believe he became the woman she didn’t want to be and for that reason, she felt jealous about her sister that was running the business.

In the letters Suang doesn’t write too many things about her, he said that Mui believed in ghosts and spirits which to the point doubt of himself, he mentioned that she only wanted to expend money on glamorous things so society can see how her wealth. She died in a car accident.

Ang Bui

Mui’s sister, Ang Bui had the responsibility to take care of their parents at a younger age which made her an independent and intelligent woman. Besides her father didn’t believe a woman can run a business, Suang trusted in her and helped her to run his father’s business. Suang admired Ang Bui which makes me think that Suang fell in love with her those times or maybe they had sex a couple of times (people rumored about it). I think if it had happened he wouldn’t write this his mother since Mui Eng read the letters he had written. The jealousy Mui felt was for this reason.

Ang Bui grew up as an independent woman influenced by Western culture, she changed her hairstyle, bought an automobile, put on makeup, and wore heels like a “modern” girl. I think the influence of American television changed the young generation at those times and they loose of their traditions. Every body wanted her to be married but she didn’t find someone to marry. Maybe Suang will marry her.

Weng Kim

Weng Kim, Suang’s son, grew up with many expectations about his future, Suang pressured him to be the person he wanted to be, he took him out of school to continue with the business and sent him to a Chinese school. Same as his 3 sisters didn’t feel fit in Thai society, their family was teaching him Chinese traditions but in school, his mates make fun of them. Some of their sisters changed their name to be more Thai. Weng Kim didn’t have the character that Suang expected, this guy ran away from his home because didn’t want to marry Rose (Gim’s daughter) and fell in love with a prostitute who manipulated her so she can get some money from his family. The love of their parents was so big that they offered the prostitute (his girlfriend) to move to his house. Suang said that this was normal in old Chinese families whoever his real plan was to make Kim realize that she was not good for him. He ended up marrying Rose (Suang friend’s daughter).

Meng Ju

She is the youngest Suan’s child, Suang didn’t care about her because he wanted a second boy instead of another girl. So it seems Meng Ju grew up in an environment repressed by her father’s apathy maybe this same apathy motivated her to continue with his studies to be accepted by his father. She fell in love with a poor Thai boy in her school, Suang U didn’t like that because he was Thai but after meeting him he saw that his thoughts are different from the rest of the people. This Thai boy told to Suang many of his thoughts amount of them he mentioned that he didn’t like that Chinese people come to his country to make business a look down on the citizens. Suang U ended up accepting him because he was smart and hard-working.

I find it very interesting almost poetic that only at the very end of the last few pages after mentioning a lot of bad things about Thais (Suang’s mind) the last few letters mention good things about Thais. Meng Ju the girl the girl who he didn’t want and his husband a Thai man were the only that care about him when the rest of the children had gone away to make their own life. At those very few moments at the age of around 30, he saw things from a different perspective in a way he hasn’t though about.

During almost the entire book you can notice how Suang’s mind shows racist thoughts against Thais. You see that the same values that make him a good person also make him a racist person.

Suang’s children like the rest of the Chinese children born in Thailand faced an identity crisis since they grew up with Chinese and Thai culture and were influenced by western media.

When reading the letters regarding how hard working he was I thought about my culture too and made me to remember that I belong a family of hard working generations, my grands parents use to worked more than 16 hrs in farm and the thought the same to my parents that at their age of 60 they don’t stop working and I think they never will, I think in my sisters and all of them work really hard and makes fell I have the same values.

During the story it feels Suang’s happiness, sadness, emptiness, worries, and other feelings. You might think that life is like a balance, he was very lucky at the beginning but things turned out bad in the last pages. In the same way he ran away from his mother in Po Leng his children were different from what he expected. It only makes me think how life is like a cycle as if the situations that happen before will happen later and so on and so on…

“Confucius taught that the world progresses only toward calamity when children do not follow the ways of parents and ancestors. Weng Kim weeps like a child and asks me how he is to survive between two worlds... what about me? Does he realize that I studied all the years of my childhood for a kind of manhood I was never permitted to have?”

In this section, we will cover the following topics:

1. Develop the UI for the the application in React
2. Deploy the contract to ganache (local blockchain for Ethereum development.)
3. Integrate web3 to our application

Develop the UI for the the application in React

The application is designed to be simple and uncomplicated. The intention of this tutorial is not to cover the react development so I won’t include too much details of it. I have decided to utilize React as our frontend framework because it is currently the most widely used framework among developers. You can check the details on of the UI in this commit https://github.com/isidroamv/voting-app/commit/e9e92120628855734fce8d26747879bd24a3b31f

At the end, the application should look like the image above. The hash array is a list of accounts we can use to test our application.

Deploy the contract to ganache

To deploy our contract we need a Ethereum network. Sepolia is the most popular test network for development. Here are some sites you can use to deploy your contract.

• https://www.infura.io
• https://sepoliafaucet.com

However for this tutorial we will be using Ganache, a local test network, since it is a quickest way to work with the Ethereum blockchain and it is not needed to register to a third party website.

To install Ganache globally, run:

npm install ganache --global

Then, run the following command on the console to start the ganache local test network.

ganache

Finally, run the script to deploy the contract:

node Ethereum/deploy-local.js 

Contract deployed at address: 0x277D272ef0b6B0bF5d13B51DCe2c0DaF8f78485E

Integrate web3 to our application

Now you can run the following command to generate the ABI (Application Binary Interface)

 npx solc contracts/VotingSystem.sol -o build --abi

Copy the ABI file to react to the react application. For example: voting-app/src/VotingSystem.json. This file will be use to interact with our contract.

Use the web3.js file to connect with the local Ethereum network.

const Web3 = require("web3");
const web3 = new Web3('ws://localhost:8545');
export default web3;

Use the the contract.js to connect with the contract.

import web3 from './web3';
const address = '0x277D272ef0b6B0bF5d13B51DCe2c0DaF8f78485E';
const abi = require('./VotingSystem.json')
export default new web3.eth.Contract(abi, address);

In this example you can see how the 2 files generated can be used to get test accounts from the test network and call the method organizationCount() from the

import { useEffect } from 'react';
import web3 from "./web3";
import Contract from "./Contract.js";

function App() {
  useEffect(() => {
    async function getProposalCount() {
      const accounts = await web3.eth.getAccounts();
      const organizationCount = await Contract.methods.organizationCount().call();

      console.log("accounts", accounts)
      console.log("organizationCount", organizationCount)
    }
    getProposalCount();
  }, []);
  return (<>
    ....
  </>);
}
export default App;

Check all files in the following repository: https://github.com/isidroamv/voting-app/tree/part-2

The complete code is in this repository: https://github.com/isidroamv/voting-app/