Soledad @soledad_dev

Product Management is, at its heart, about managing risk. But the risks at play are not obvious. The extended classification beyond the famous "Value, Usability, Viability, and Feasibility:" (1/9)

Hard - Learning a 2nd language Harder - Giving a talk in a 2nd language Hardcore - Live coding while speaking a 2nd language This is for all of you who have to focus on English just to speak at conferences.

It's crazy what results PMs can get with ChatGPT-4o. But just a few write good prompts. (1/7)🧵

Great #Kubernetes Mind Map

The future that is happening. Automation powered by GPT-4o generates Figma designs based on PRD. @figma

Seven types of income.

Top 5 Kafka use cases Kafka was originally built for massive log processing. It retains messages until expiration and lets consumers pull messages at their own pace. Let’s review the popular Kafka use cases. - Log processing and analysis - Data streaming in recommendations - System monitoring and alerting - CDC (Change data capture) - System migration

Razones por las que no volveria a vscode: - Las macros de VIM

In case you were wondering just how cracked the team @cognition_labs is... This was the CEO (@ScottWu46) 14 years ago.

Cognition @cognition

2 years ago

Today we're excited to introduce Devin, the first AI software engineer. Devin is the new state-of-the-art on the SWE-Bench coding benchmark, has successfully passed practical engineering interviews from leading AI companies, and has even completed real jobs on Upwork. Devin is

4K 10K 42K 31.5M 25K

Today we're excited to introduce Devin, the first AI software engineer. Devin is the new state-of-the-art on the SWE-Bench coding benchmark, has successfully passed practical engineering interviews from leading AI companies, and has even completed real jobs on Upwork. Devin is an autonomous agent that solves engineering tasks through the use of its own shell, code editor, and web browser. When evaluated on the SWE-Bench benchmark, which asks an AI to resolve GitHub issues found in real-world open-source projects, Devin correctly resolves 13.86% of the issues unassisted, far exceeding the previous state-of-the-art model performance of 1.96% unassisted and 4.80% assisted. Check out what Devin can do in the thread below.

I'm making a video on Partial Prerendering. What would you like to know?

My React Server Components (RSC) mental model is basically: They’re getServerSideProps / getStaticProps but more powerful. Things RSC / gSSP / gSP share in common: 🔸 You can’t pass things like normal functions from RSC / gSSP / gSP to the client, because they just can’t be serialized; 🔸 They must be executed before Client Components; 🔸 They don’t run in the browser; 🔸 They don’t have states, so no hooks; 🔸 They can both be executed and stored as static at build time (RSC / gSP), so they don’t require a server. Things that are more advanced in RSC compared to gSSP / gSP: 🔹 Server Components can pass elements and more to the client, instead of being limited to JSON values; 🔹 Server Components are able to define extra wrappers around Client Components, whereas gSSP / gSP can only affect components’ inner content; 🔹 You can have many Server Components and they will be more parallelized when executing, instead of only one giant gSSP / gSP blocking on the top; 🔹 Individual Server Component boundaries can be optimized as static if possible, instead of picking between fully dynamic (gSSP) and fully static (gSP) for all data; 🔹 Individual Server Component boundaries can be streamed to the browser and rendered earlier, unlike gSSP that must block the initial client rendering.

React tip: "use client" misconceptions (1/5) 🚫 You need to mark EVERY individual file with "use client" to ensure it is a Client Component. ✅ You only need to mark each client entry point ONCE. Modules imported into a "use client" file are already part of the client bundle. (0:05) Adding "use client" to `3.js` marks the file as a client entry point, including it in the client bundle. (0:11) Importing `d()` into `3.js` (a client entry point) also includes it in the client bundle. (0:14) Adding "use client" to `4.js` has no additional bundling effect on `d()` because it is already part of the client bundle. (0:23) All modules (and their dependencies) imported to `3.js` are included in the client bundle. (0:26) Removing "use client" from `3.js` moves it and its dependencies into the server bundle.

¡El nuevo hook use() de React tiene pintaza! No más useEffect para hacer llamadas a APIs

We can add computed refs and methods directly to a reactive object in @vuejs:

Introducing Sora, our text-to-video model. Sora can create videos of up to 60 seconds featuring highly detailed scenes, complex camera motion, and multiple characters with vibrant emotions. openai.com/sora Prompt: “Beautiful, snowy Tokyo city is bustling. The camera moves through the bustling city street, following several people enjoying the beautiful snowy weather and shopping at nearby stalls. Gorgeous sakura petals are flying through the wind along with snowflakes.”

10 lessons I've learned about handling React state over the last 7 years... (thread) #react #reactjs

Arquitecturas para APIs más usadas. ¡Te las explico todas y cuándo usarlas! ↓ gRPC Desarrollado por Google. Utiliza HTTP/2 para la transmisión, Protocol Buffers como lenguaje de interfaz y ofrece funciones como autenticación, balanceo de carga y verificación. Uso: Ideal para microservicios y sistemas distribuidos donde se necesita un rendimiento eficiente y una comunicación rápida entre servicios. SOAP Simple Object Access Protocol es un protocolo de intercambio de mensajes basado en XML utilizado para la comunicación entre aplicaciones. Es independiente del lenguaje y la plataforma, y se apoya en protocolos como HTTP y SMTP. Uso: Adecuado para entornos empresariales con requerimientos de seguridad y transacciones complejas, aunque tiende a ser más pesado que alternativas como REST. GraphQL Lenguaje de consulta y manipulación de datos para APIs. Permite a los clientes especificar exactamente qué datos necesitan, lo que puede reducir la cantidad de datos transferidos. Uso: Útil cuando los clientes necesitan solicitar datos específicos y variados, optimizando las cargas de las solicitudes y respuestas. Webhook Técnica utilizada para que una aplicación proporcione a otras aplicaciones información en tiempo real. Funciona mediante "callbacks" HTTP: una aplicación enviará datos a otra aplicación tan pronto como ocurra un evento. Uso: Ideal para reacciones en tiempo real a eventos, como notificaciones o integraciones automáticas entre diferentes servicios. REST Representational State Transfer es una arquitectura para sistemas distribuidos, y es el más común para APIs en la web. Utiliza métodos HTTP estándar y se basa en recursos identificados por URLs. Uso: REST es versátil y fácil de entender, adecuado para la mayoría de las aplicaciones web que no requieren una comunicación en tiempo real o un formato de mensaje más complejo. WebSocket Proporciona un canal de comunicación bidireccional y persistente sobre una sola conexión TCP. Esto permite una comunicación en tiempo real entre el cliente y el servidor. Uso: Es ideal para aplicaciones que requieren interacciones en tiempo real como juegos en línea, chat en vivo y aplicaciones de colaboración en tiempo real. ¡Existen más pero estos serían las más populares! Espero que te sirva el contenido.

Here are my most popular @vuejs tips from the last month. Enjoy!

One kind of prop in @vuejs can be directly converted into slots without very much work. It's called a "template prop". This makes your component more reusable. The `text` prop here is a template prop, because it is only ever used in the template: