Petro tuitea cualquier cosa -una mentira, un insulto, un delirio- y recibe 10.000 likes.
Mi teorรญa es que sus fanรกticos ni siquiera lo leen. Simplemente le dan like porque es รฉl y por la ridiculez aquella de โlas lรกgrimas de fachosโ.
Es la mรกs clara muestra del fanatismo irracional que puede generar un caudillo y una advertencia de los peligros que eso conlleva para la sociedad y la democracia.
ยกLa guerra de la IA continua!
Nuevo modelo Anthropic Opus 4.5
โ Por delante de Gemini 3 Pro en muchos benchmarks
โ El mejor modelo de programaciรณn de lejos
โ 3 veces mรกs barato que Opus 4.1
Ya lo tienes disponible en Cursor y pronto el resto
If youโre still sending raw JSON into your LLMs, youโre burning tokens, latency, and budget!
Try TOON (Token-Oriented Object Notation).
Clear like YAML, compact like CSV:
โข 30โ60% fewer tokens
โข Up to 50% lower costs
โข Shines for tabular data.
Free and Open source ๐งตโ
El framework que usamos en @RappiColombia para aprender y construir CUALQUIER COSA desde cero (actualizado y mejorado a la fecha)
El mismo que uso para que mi equipo desarrolle world-class capabilities
Aquรญ los 6 pasos clave ๐
๐ฆ๐ผ๐ณ๐๐๐ฎ๐ฟ๐ฒ ๐๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ != ๐๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐ฒ๐ฟ
Software Engineer == Problem Solver
Don't attack problems with code. Try first to understand them from a business perspective and then a technical perspective. When you do this, make a plan for how to solve it.
Try to solve without coding. The best code is not code.
If you must code, then do it.
Remember, ๐ฐ๐ผ๐ฑ๐ฒ ๐ถ๐ ๐ฎ ๐น๐ถ๐ฎ๐ฏ๐ถ๐น๐ถ๐๐, ๐ป๐ผ๐ ๐ฎ๐ป ๐ฎ๐๐๐ฒ๐.
#softwareengineering #programming #developers
๐๐ผ๐ ๐๐ผ ๐ด๐ฒ๐ ๐บ๐ผ๐ฟ๐ฒ ๐ฑ๐ผ๐ป๐ฒ ๐๐ต๐ฎ๐ป ๐ต๐ฌ% ๐ผ๐ณ ๐ฝ๐ฒ๐ผ๐ฝ๐น๐ฒ
We all struggle with the things we should do next and what to prioritize. Here comes the ๐๐ฒ๐๐๐ถ๐ป๐ด ๐ง๐ต๐ถ๐ป๐ด๐ ๐๐ผ๐ป๐ฒ (๐๐ง๐) ๐ณ๐ฟ๐ฎ๐บ๐ฒ๐๐ผ๐ฟ๐ธ to help. David Allen developed it in the 1990s, and the main idea behind GTD is that by getting all of your tasks and commitments out of your head and into a trusted system, you can reduce stress, increase productivity, and free up mental space to focus on more important things.
So, how it works is to have the following lists:
๐ญ. ๐๐ป. Here, we put all the ideas we have as they occur. Write down every task, idea, or commitment that comes to mind, whether small or insignificant. When adding items here, you should ask yourself if this is actionable. You should remove or add the answer to the ๐ฆ๐ผ๐บ๐ฒ๐ฑ๐ฎ๐/๐บ๐ฎ๐๐ฏ๐ฒ list if the answer is NO. If it's actionable in the physical and visible sense, move it to the ๐ก๐ฒ๐ ๐ ๐๐ฐ๐๐ถ๐ผ๐ป๐ list.
๐ฎ. ๐ก๐ฒ๐ ๐ ๐๐ฐ๐๐ถ๐ผ๐ป๐. The most crucial section is that we have everything you can choose to do at any moment. Consider whether it takes less than two minutes to determine the next action. If this is the case, do it immediately (2-minute rule). If an action needs less than ๐๐๐ผ ๐บ๐ถ๐ป๐๐๐ฒ๐, it gives us overhead to track, compared to how long it takes. If you need more than 2 minutes, delegate it if possible and put it in the Waiting for a list or to your Next actions list if not.
Here, you can use the ๐๐ถ๐๐ฒ๐ป๐ต๐ผ๐๐ฒ๐ฟ ๐บ๐ฎ๐๐ฟ๐ถ๐ to help you understand what you should do immediately, what to delegate, and what to delete.
๐ฏ. ๐ช๐ฎ๐ถ๐๐ถ๐ป๐ด ๐ณ๐ผ๐ฟ. This is the list where you put stuff you delegated to others, or you're waiting to reply to, or some issue blocks it.
๐ฐ. ๐ฃ๐ฟ๐ผ๐ท๐ฒ๐ฐ๐๐. This is where we put stuff that needs more than one action, which is a grouping for actions. It is a simple list of projects with two or more actions. And be sure that there is at least one action from a project in the Next actions list.
๐ฑ. ๐ฆ๐ผ๐บ๐ฒ๐ฑ๐ฎ๐/๐บ๐ฎ๐๐ฏ๐ฒ.This is where you put your ideas without concrete actions, which you want to pursue in the future but currently don't have time for.
Finally, don't forget to do a weekly review, which is a critical factor for success. You can do it once per week (30 minutes), e.g., on Friday or Sunday afternoon. Here, you make sure each project has at least one of the next actions, that each action in your next actions is something you need to do in the next week, and look through your Someday/maybe list and see if some actions should be moved in the list of current projects or next actions.
#personaldevelopment #productivity #gettingthigsdone
โQue miedo las cuentas de alta rentabilidad en esos bancos tan rarosโ
Ya la he escuchado varias veces ๐
Vamos a hablar de esa frase en este ๐งต
Honrados de que Kantar haya incluido a @mercadopago como una de las 20 marcas de servicios financieros mรกs valiosas del mundo! Y muy agradecidos a los mรกs de 50 millones de usuarios que nos eligen todos los meses! Juntos #Democratizamos_el_dinero
๐ช๐ต๐ ๐๐ผ๐ ๐๐ต๐ผ๐๐น๐ฑ ๐ฏ๐๐ถ๐น๐ฑ ๐ฎ (๐บ๐ผ๐ฑ๐๐น๐ฎ๐ฟ) ๐บ๐ผ๐ป๐ผ๐น๐ถ๐๐ต ๐ณ๐ถ๐ฟ๐๐?
In recent years, we have seen a significant increase in apps built using a microservices architecture. The main reason we selected this approach is to have small teams that can work in isolation without tripping over each other. Yet, this is an organizational problem, not a technical one. We can also build each service using separate technology and scale it independently.
With the ๐บ๐ถ๐ฐ๐ฟ๐ผ๐๐ฒ๐ฟ๐๐ถ๐ฐ๐ฒ๐ ๐ฎ๐ฝ๐ฝ๐ฟ๐ผ๐ฎ๐ฐ๐ต, we also have a few disadvantages; the system is becoming complex to maintain and diagnose issues (logging and tracing). This is very important when dealing with microservices.
So, ๐ฏ๐๐ถ๐น๐ฑ๐ถ๐ป๐ด ๐บ๐ผ๐ป๐ผ๐น๐ถ๐๐ต๐ ๐ฑ๐ผ๐ฒ๐๐ป'๐ ๐บ๐ฒ๐ฎ๐ป ๐๐ผ๐บ๐ฒ๐๐ต๐ถ๐ป๐ด ๐ฏ๐ฒ๐๐๐ฒ๐ฟ ๐ฝ๐ฒ๐ฟ ๐๐ฒ. In the last few years, we have often seen the identification of monoliths with big balls of mud architecture or purely building legacy code, which doesn't mean to be. Yes, monoliths cannot scale-independent pieces of the system or release them separately, but those are mainly the biggest downsides. Still, you can create great and high-quality code inside. What monolith brings to us is much less complexity, reduced network calls, simpler logging and debugging, etc.
What could be one good solution, where we can still have separate modules and work on them but maintain simplicity, is to ๐ฏ๐๐ถ๐น๐ฑ ๐ฎ ๐บ๐ผ๐ฑ๐๐น๐ฎ๐ฟ ๐บ๐ผ๐ป๐ผ๐น๐ถ๐๐ต. A properly built modular monolith can be a good step that can be more or less transformed into a microservice solution tomorrow if needed.
When we want to build a modular monolith, it is crucial to ๐ณ๐ถ๐ฟ๐๐ ๐ฑ๐ถ๐๐ถ๐ฑ๐ฒ ๐๐ต๐ฒ ๐๐๐๐๐ฒ๐บ ๐ถ๐ป๐๐ผ ๐บ๐ฎ๐ป๐ฎ๐ด๐ฒ๐ฎ๐ฏ๐น๐ฒ ๐บ๐ผ๐ฑ๐๐น๐ฒ๐ before assembling those modules into a monolith for deployment. As all communication between the modules might result in a cross-network call, high cohesion and low coupling are crucial if you decide to break it into services in the future. This means that all inter-module communication must be abstracted, asynchronous, or based on messaging for the modules to handle calls that travel across the network in the future.
How can we put such a concept in place? ๐ช๐ฒ ๐ฐ๐ฟ๐ฒ๐ฎ๐๐ฒ ๐๐ฒ๐ฝ๐ฎ๐ฟ๐ฎ๐๐ฒ ๐บ๐ผ๐ฑ๐๐น๐ฒ๐, ๐๐ต๐ฒ๐ฟ๐ฒ ๐ฒ๐ฎ๐ฐ๐ต ๐ผ๐ป๐ฒ ๐ฐ๐ฎ๐ป ๐ต๐ฎ๐๐ฒ ๐ถ๐๐ ๐ผ๐๐ป ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฒ, and those modules are pulled together into a single API gateway. This allows us to deploy the whole system as a monolith, but it allows us to pull out separate modules into services if needed in the future.
In the end, we need to mention that this approach ๐๐ฅ๐ฌ ๐ฐ๐ผ๐ป๐ฐ๐ฒ๐ฝ๐ (don't repeat yourself) in a few places, but this allows us to avoid unnecessary dependencies between modules.
Don't go for trends; always choose simplicity and use common sense to determine what will work for you.
#technology #softwareengineering #programming #techworldwithmilan #softwarearchitecture
@TeroMknen I'd generally recommend the "docs as code" approach ... Markdown/AsciiDoc files (1 per decision) in version control next to the code, published to other locations (e.g. Jira, SharePoint, etc) by your build pipeline if required.