Iniciar sesión para ver el perfil completo de Leo
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Iniciar sesión para ver el perfil completo de Leo
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
San José Metropolitan Area
Iniciar sesión para ver el perfil completo de Leo
Leo puede presentarte a 3 personas en Calliope AI
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
2 mil seguidores
Más de 500 contactos
Iniciar sesión para ver el perfil completo de Leo
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Ver tus contactos en común con Leo
Leo puede presentarte a 3 personas en Calliope AI
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Ver tus contactos en común con Leo
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Iniciar sesión para ver el perfil completo de Leo
o
¿Estás empezando a usar LinkedIn? Únete ahora
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Sitios web
- Sitio web de la empresa
-
https://weareconflict.com
- Sitio web de la empresa
-
https://calliope.ai
Acerca de
¡Hola de nuevo!
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
¿Estás empezando a usar LinkedIn? Únete ahora
Artículos de Leo
-
I Read the Source Code Behind Claude's "Frontend Design" Skill. Spoiler: It's a fancy font Blacklist.
I Read the Source Code Behind Claude's "Frontend Design" Skill. Spoiler: It's a fancy font Blacklist.
Anthropic has shipped a plugin system for Claude Code, and one of the flagship skills is "frontend-design" — a skill…
13
1 comentario
Actividad
2 mil seguidores
-
Leo M. ha compartido estoProvenance doesn’t only apply to wines; make sure you know where your package dependencies are sourced. Carefully scan and review all imports, more importantly, research the community and repos.Leo M. ha compartido estoThe software supply chain has become the most critical and least-defended attack surface in modern software development. This week, someone hijacked one of the most popular packages on the internet and used it to install a backdoor on every machine that ran npm install. a16z's Malika Aubakirova, Zane Lackey, and Joel de la Garza on how Socket detected the Axios attack within 6 minutes, why AI is compressing software supply chain attack timelines, and why defenders have to move at machine speed to save the agents. Full piece in the comments.
-
Leo M. ha compartido estoafter some more testing and feedback we just shipped scuttlebot v1.2.0 with some important fixes which include: - group mentions (@all, @worker, @claude-*) so you can direct all your agents at once - agents now show online/offline/idle status with last seen times - automatic reconnection when the server restarts - responsive mobile web UI that actually works - per-project channel routing - stale agent cleanup - OpenClaw integration seeing as #openclaw has native irc support Thank you to everyone who ran it today and reported issues... every fix on this list came from real use cases #claude #claudecode #gemini #codex https://lnkd.in/e6EqxkReGitHub - ConflictHQ/scuttlebot: Agent coordination backplane built on IRCGitHub - ConflictHQ/scuttlebot: Agent coordination backplane built on IRC
-
Leo M. ha compartido estoLeo M. ha compartido estoScuttleBot is now open source. It is a coordination backplane for AI agent fleets. Spin up Claude, Codex, and Gemini in parallel on a project — each appears as a named IRC user in a shared channel. Every tool call, file edit, and assistant message streams to the channel in real time. Address any agent by name to redirect it mid-task. The hard problem with production agent fleets is not capability, it is visibility and control. Most tooling treats the agent as a black box. You give it a task, it runs, you look at the output. That works for simple things. It breaks down the moment you are running multiple agents in parallel on real work. ScuttleBot puts a coordination layer underneath without changing how the agents work. They run exactly as they always have. You gain a live command center: every agent's activity visible in real time, every agent addressable by name, every session persistent and logged. Human observable by default. No dashboards. Any IRC client works (also has a built in web client). Built-in: unified LLM gateway across Anthropic, OpenAI, Gemini, Ollama, and Bedrock. System bots for logging, history, summarization, and moderation. SQLite and Postgres backends. TLS with Let's Encrypt. scuttlebot.dev — https://lnkd.in/evDC2PYjGitHub - ConflictHQ/scuttlebot: Agent coordination backplane built on IRCGitHub - ConflictHQ/scuttlebot: Agent coordination backplane built on IRC
-
Leo M. ha compartido estoJust open sourced ScuttleBot. The problem with running AI agents in production is not getting them to write good code. It is knowing what they are actually doing, being able to interrupt them when they go wrong, and coordinating multiple agents on the same work without losing control of the process. Most agent tooling treats the agent as a black box. You give it a task, it runs, you look at the output. That works for simple things. It falls apart the moment you are running Claude, Codex, and Gemini in parallel on a real project. ScuttleBot is the coordination layer we built to fix that. Each agent appears as a named IRC user in a shared channel. Every tool call, file edit, bash command, and assistant message streams to the channel in real time. You can watch your fleet work from any IRC client. You can address any agent by name and inject a message directly into its running terminal, with an interrupt if it is mid-task. It is human observable by default. No dashboards to build. No observability pipelines to configure. You open an IRC client and you see exactly what is happening. Under the hood: an embedded Ergo IRC server, relay brokers that wrap Claude Code / Codex / Gemini on a PTY, a unified LLM gateway for routing requests across backends, built-in bots for logging, history replay, channel summarization, and moderation. SQLite and Postgres for state when you need it. TLS and Let's Encrypt built in. scuttlebot.dev — https://lnkd.in/e6EqxkReGitHub - ConflictHQ/scuttlebot: Agent coordination backplane built on IRCGitHub - ConflictHQ/scuttlebot: Agent coordination backplane built on IRC
-
Leo M. ha compartido estoLeo M. ha compartido estoWhile Wikimedia content is free, the infrastructure that serves it is not. Thanks to improvements in bot detection, more than *2 billion* requests per day get currently blocked, which would have otherwise caused further strain on the infrastructure. https://lnkd.in/ei5sNrmbQuo Vadis, Crawlers? Progress and what’s next on safeguarding our infrastructureQuo Vadis, Crawlers? Progress and what’s next on safeguarding our infrastructure
-
Leo M. ha publicado estoStop burning tokens bootstrapping boilerplate. Auth. Connection pooling. Backend wired to frontend. CI. Docker. You've solved these before. Your agents have solved these before. Yet every new project starts from zero. Boilerworks fixes that. 26 production-ready templates across 10 stacks — pick one, run boilerworks init, and start on the work that actually matters. https://boilerworks.ai https://lnkd.in/e_aMQ_N7 --- #devtools #agenticengineering #platformengineering
-
Leo M. ha compartido estoStop burning tokens bootstrapping boilerplate. Auth. Connection pooling. Backend wired to frontend. CI. Docker. You've solved these before. Your agents have solved these before. Yet every new project starts from zero. Boilerworks fixes that. 26 production-ready templates across 10 stacks — pick one, run boilerworks init, and start on the work that actually matters. https://boilerworks.ai --- #devtools #agenticengineering #platformengineering
-
Leo M. ha compartido estoLeo M. ha compartido estoWe just open-sourced Boilerworks. Here's why it exists. Every client engagement starts the same way. Not with the interesting problem — with 40 hours of setup. Auth. CI/CD. Docker. Terraform. Structured logging. Test infrastructure. The same foundation, rebuilt from scratch, on every project. We got tired of paying that tax. Boilerworks is what we built instead: 26 production-ready project templates across 10 languages and frameworks. Pick a stack, run one command, get a real working foundation — not a skeleton with TODO comments. pip install boilerworks boilerworks init Two minutes later you have CI that actually runs, Docker Compose for local and staging, Terraform for your infra layer, structured logging from day one, and auth scaffolding appropriate to your stack. Stacks: Django, FastAPI, Go, Rails, Laravel, NestJS, Spring, Elixir, Rust, Svelte. Full-stack, micro services, and edge variants. No lock-in. The generated code is standard libraries. An engineer who's never heard of Boilerworks can read and maintain it. We built this for ourselves. Now it's yours. Boilerworks.ai GitHub: https://lnkd.in/e6ZavMJx Docs: boilerworks.dev --- #devtools #opensource #softwaredevelopment #platformengineering #boilerworks
-
Leo M. ha compartido estoThis is the right take. Use AI to empower humans, make them more effective, not redundant.Leo M. ha compartido estoI keep seeing companies talk about using AI to reduce their engineering teams. That’s the wrong move. AI isn’t eliminating software development. It’s changing what software is. For most of the last few decades, software behaved like infrastructure. Expensive to build. Risky to change. Something you tried to get right and then leave alone. But as the cost of writing and modifying code drops… that model breaks. Software stops being something you build once. It becomes something you generate, test, and replace continuously. Which means the constraint isn’t writing code anymore. It’s how fast you can change what you’re doing. Companies cutting developers right now aren’t becoming more efficient. They’re reducing their ability to adapt.
-
Leo M. ha recomendado estoWikimedia Foundation is hiring: Senior Software Engineer (Security & Privacy). Please check out our job posting & share with your networks: https://lnkd.in/eFmRxSTD #wikipedia #techjobs #remotejobs #nonprofitjobs #freeknowledge #hiring #globaljobs #techforgood
-
Leo M. ha recomendado estoLeo M. ha recomendado estoThree decades of #curl is my talk from NDC Security back in early march. https://lnkd.in/dF8CrE3yThree decades of curl - Daniel Stenberg - NDC Security 2026Three decades of curl - Daniel Stenberg - NDC Security 2026
-
Leo M. ha recomendado estoLeo M. ha recomendado estoNew from Together Research: LLMs can fix the query plans your database optimizer gets wrong, resulting in up to 4.78x faster execution. Cost-based optimizers fail when they miss semantic correlations. A filter that prunes 15M rows to 2.9M gets applied after a join instead of before — because the optimizer assumed independence where none existed. DBPlanBench exposes DataFusion's physical operator graph to an LLM, which applies targeted JSON patch edits to fix join ordering without regenerating the full plan. On TPC-H and TPC-DS workloads: → Up to 4.78x speedup on complex multi-join queries → 60.8% of queries improved by more than 5% → Build memory: 3.3 GB → 411 MB on a single benchmark query → Plans optimized at small scale transfer directly to larger databases Paper and code are open-source. Link in comments.
-
Leo M. ha recomendado estoLeo M. ha recomendado estoThe Kilo Code team reached out to me and showed me a pretty incredible Gas Town user experience they've built inside Kilo, which they launched yesterday. Amazing! I've been predicting forever that our agentic terminal experience will evolve into a graphical interface, and it didn't take long. They have convoy viewers, molecule viewers, dashboards, and all sorts of other conveniences. Here's their blog post about it: https://lnkd.in/gCzh5TKq If you've been hesitant about leaving the comfort of VS Code to try Gas Town, this could be just right for you. Gas Town is stable -- we are approaching a v1.0.0 release. And Kilo has solid onboarding in the UX. Might be worth a try.
-
Leo M. ha recomendado estoLeo M. ha recomendado estoEnough people asked me about Medvi, thought I'd share some stuff that I think is missing from the main narrative. Not mentioned in the article was there was a 2-3 year period where the FDA declared a shortage of weight loss drugs and compounded GLP1's were a DTC marketers dream -> unprecedented demand for a product where the alternative cost $1000-1500, was unavailable and you could sell the exact same chemical for $250. Most digital health companies were trying to build some lifetime value around the care model/patient experience to capture more margin & build equity value. A pure marketing-focused firm with no board or clinical team could move much faster. IE Medvi optimized for profits vs long term equity value - which basically worked Now, compounding is more highly regulated (new rules coming down this month) and the branded prices coming down to the $200-range, the arbitrage has been eroded. Medvi today has an issue - the company made $400m last year but the "special sauce" of being able to sell a highly discounted product has been diminished. By definition his CAC will be higher and Medvi already has thin margins. The founder probably wants some credit and releasing his numbers at the peak. He's now known as the "first vibe-coded" billionaire which is monetizable - I am sure he will leverage for new deals, financing, etc...
-
Leo M. ha recomendado estoLeo M. ha recomendado estoA fresh new landing page for all your "clinician in the loop" needs: https://lnkd.in/gPygbMAz DM me if you have any specific questions!
Experiencia y educación
-
Calliope AI
******* * ***
-
********
******** ********
-
****** **********
******
-
*********** ****** ** ***** ****
-
-
******* ******
-
Mira la experiencia completa de Leo
Mira su cargo, antigüedad y más
¡Hola de nuevo!
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
¿Estás empezando a usar LinkedIn? Únete ahora
o
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Licencias y certificaciones
Experiencia de voluntariado
-
Technology Advisor
National Childrens Hospital Cost Rica - Developmental Pediatrics Unit
- 14 años
Infancia
I served as a technical consultant for ongoing technical efforts relating to bridging technology to kids with autism and other developmental disorders. This often included advising on matters to assist screening and data recording/processing for the kids that are treated there for developmental problems such as Autism, Down Syndrome, Cerebral Palsy, etc.
-
Certified Official Translator
Costa Rican Ministry of Foreign Relations
- actualidad 25 años
Política
Official translatorship awarded by the Ministry of Foreign Relations in Costa Rica... I volunteer when called to translate official documents regarding technical matters or random court appearances to translate depositions or diplomatic encounters.
Idiomas
-
Spanish
Competencia bilingüe o nativa
-
English
Competencia bilingüe o nativa
-
French
Competencia básica
Recomendaciones recibidas
12 personas han recomendado a Leo
Unirse para verloVer el perfil completo de Leo
-
Descubrir a quién conocéis en común
-
Conseguir una presentación
-
Contactar con Leo directamente
Perfiles similares
-
Víctor Suárez
Víctor Suárez
With over 15 years of experience in project management, I specialize in leading cross-functional and virtual teams to deliver robust business, financial, and multimedia applications. As Manager at Vorealis Software since March 2019, I contribute to the development of innovative solutions, including TaskBlast.com, ERPNext, designed to enhance agile project workflows.<br><br>Leveraging expertise in project management, and team leadership, my focus lies in aligning business strategies with software development to foster team collaboration and client success. Currently exploring entrepreneurial ventures, I aim to expand my skill set and drive impactful solutions while maintaining a strong commitment to excellence and innovation.
1 mil seguidoresSan José, Costa Rica -
Mariano Dilascio
Mariano Dilascio
Passionate about helping teams and businesses unlock their true potential. While I believe in the power of cutting-edge technology to drive success, it's the people behind the tech who make the real difference.<br><br>I focus on operational excellence and inspire positive change, guiding organizations through challenges and toward their strategic goals. My leadership centers on motivating and empowering teams to deliver outstanding results, fostering a culture where innovation thrives, and ensuring lasting growth.<br><br>Let's connect and explore how we can collaborate to transform ideas into impactful solutions.
1 mil seguidoresCosta Rica
Ver más publicaciones
-
Christopher Flores
The Moxie Health Group • 432 seguidores
I want to talk about Team Nightwatch: Rolando Maradiaga, Christhian Flores, André Velásquez and Jean Pierre Santos At MoxieThon Panama 2026, while my team was heads-down on billing automation, these four were quietly building something that stopped everyone in the room during the final presentation. MoxieReport — a module that replaces one of the most painful parts of healthcare operations: manual report generation and auditing. If you've ever worked in a clinical setting, you know what that looks like. Spreadsheets. Back-and-forth reviews. Data gaps nobody catches until it's too late. Their system automates all of it. Identifies gaps in real time. Generates reports automatically. And then — the detail that stood out — a One-Click Notify that alerts practitioners via email and WhatsApp the moment new census data is created. They also shipped an AI assistant that lets you ask natural-language questions about your report data and get charts back instantly. Three days. Four engineers. First place. Well deserved. This is what happens when talented engineers are given a real problem and the space to solve it. Thank you to The Moxie Health Group and Gustavo Ferrer MD, FCCP, MBA for creating this space. Competing alongside this level of talent doesn't happen by accident — it takes a company that actually invests in its people. #MoxieThon #HealthcareAI #MoxieLink #TeamNightwatch #Healthtech #EngineeringLeadership #Panama
20
2 comentarios -
Ray Carneiro
QAT Global | Custom Software… • 10 mil seguidores
This guide gives CIOs, CTOs, and VPs of Engineering the insights to: * Evaluate the strengths and risks of nearshore delivery vs. offshore or onshore. * Justify the nearshore decision internally with CFOs, security, and procurement stakeholders. * Choose the right nearshore partner with confidence. * Understand the most common pitfalls—and how to avoid them. Download today and walk away with a clear, strategic view of how nearshoring works, when it works best, and what it takes to get it right. https://lnkd.in/d7kYcUbs
11
2 comentarios -
Marcel Tan
Tusk • 8 mil seguidores
Your code is only as good as your input. Guillermo Rauch, Vercel's CEO, posted that code should be treated as an output, and we should be turning our attention to production inputs. I agree. No amount of context in a system message will replace giving your coding agents access to production traces. Your agents need to see how real users actually hit your APIs. Which means looking at full request/response bodies, database calls, cache hits, etc. How we do it: - Record live traffic down to individual spans (with PII redacted) - Pipe traces to a coding agent via MCP so it can debug with real payloads - Replay traffic as a test suite in CI to diff API responses against user behavior Your app already knows what to test. You just didn't have something listening back then.
30
1 comentario -
Dmytro Yarmak
Shine • 660 seguidores
🚀 Highly efficient CI/CD is not just a technical detail - it’s one of the most impactful levers an engineering leader can pull. Guillermo Rauch, CEO of Vercel, shared this during his conversation on Uncapped with Jack Altman: “The one thing I did that was revolutionary for my team was spending a lot of time in getting the CI/CD process… as efficient as possible. Imagine that you’re almost editing the internet in real time. That was the feeling that I wanted to give my employees.” 🧑💻 For engineers, this means a workflow where pushing a small feature to Git immediately triggers a deployment - feedback is nearly instantaneous, and iteration becomes natural. 🧑💼 For engineering managers, it’s about deployment velocity. The faster your team can ship safely, the more they can stay in flow, experiment, and innovate. Velocity compounds into business value. ✨ Guillermo compares it to setting up a new Apple laptop: everything “just works” out of the box. That’s the developer experience goal - no wasted cycles on painful environment setup, just pure focus on building. 💡 The real takeaway: Efficient CI/CD is a business strategy. Happy developers build better products, and organizations that can “edit the internet in real time” will outpace those still stuck in quarterly deployments and code freezes. #SoftwareEngineering #DevOps #DeveloperExperience
1
1 comentario -
Michael Skarzynski
Brite • 12 mil seguidores
12 Architectural Concepts Developers Should Know By Alex Xu 12 Architectural Concepts Developers Should Know 1 - Load Balancing: Distributed incoming traffic across multiple servers to ensure no single node is overwhelmed. 2 - Caching: Stores frequently accessed data in memory to reduce latency. 3 - Content Delivery Network (CDN): Stores static assets across geographically distributed edge servers so users download content from the nearest location. 4 - Message Queue: Decouples components by letting producers enqueue messages that consumers process asynchronously. 5 - Publish-Subscribe: Enables multiple consumers to receive messages from a topic. 6 - API Gateway: Acts as a single entry point for client requests, handling routing, authentication, rate limiting, and protocol translation. 7 - Circuit Breaker: Monitors downstream service calls and stops attempts when failures exceed a threshold. 8 - Service Discovery: Automatically tracks available service instances so components can locate and communicate with each other dynamically. 9 - Sharding: Splits large datasets across multiple nodes based on a specific shard key. 10 - Rate Limiting: Controls the number of requests a client can make in a given time window to protect services from overload. 11 - Consistent Hashing: Distributes data across nodes in a way that minimizes reorganization when nodes join or leave. 12 - Auto Scaling: Automatically adds or removes compute resources based on defined metrics.
1
-
Santhosh Kumar Venkatesan
Nasdaq • 808 seguidores
Organizing cross-functional, multi-faceted teams requires a. Structuring them to address mixed priorities originating from their respective streams. b. Establishing an enabling task force to support stream-aligned teams, and c.Managing the complex subsystems within them. Navigating these complexities without a proper framework can be challenging; I recently encountered the works of Team Topologies - https://lnkd.in/g3pT878f. Their approach helps create a mental model and aids in identifying inherent patterns within the teams to: a. Understand the natural flow of work within the teams and maximize the flow. b. Establish a shared vocabulary, both internally (vertically) and externally(horizontally), for discussing the team's structure and roles. Useful videos - https://lnkd.in/gMemdB7C https://lnkd.in/g_mvhkHt
3
-
David Szabo
SnapSoft • 694 seguidores
General info. Technical details. Affected sites. Here we go: A few days ago Amazon Web Services (AWS) experienced a major disruption in its U.S. East (N. Virginia, us-east-1) region, affecting 142 regional and some global services for several hours. The issue lowered AWS’s uptime in this region for October below its usual 99.99% reliability target (which varies by service). Lots of green days, two red ones, and back to green. AWS has since resolved the problem, added stronger safeguards, and committed to improving testing and recovery to prevent similar outages. The full post-mortem is linked in the comments. From a technical standpoint, the outage was triggered by a DNS automation race-condition fault within Amazon DynamoDB’s DNS management system. This created incorrect DNS records that caused endpoint resolution failures, impacting dependent services such as EC2 instance launches, Network Load Balancer (NLB) health checks, and Lambda functions. Such issues usually occur due to a specific chain of events, and honestly, they can happen even in the most well-designed systems. AWS engineers disabled the faulty automation, deployed new recovery and throttling controls, strengthened failure isolation, and enhanced resilience testing across large-scale systems. Many well-known companies were affected. Most likely, most of them didn’t want to reveal their infrastructure dependencies, but that information was exposed unintentionally. Snapchat, Reddit, Canva, Duolingo, The New York Times, Fortnite, Apple TV, McDonald’s, OpenAI, Vimeo, Twitch, Shopify, Google Maps, reCAPTCHA, YouTube, Spotify, Discord, Google, Cloudflare, Mailchimp, WhatsApp, Airbnb, and Disney+. What do you think?
5
1 comentario -
Santiago Merlos
SIGHUP • 1 mil seguidores
KCD Mexico 2025: Advancing Cloud-Native Innovation KCD Mexico 2025 in Guadalajara brought together over 200 cloud computing and Kubernetes professionals to explore the latest advancements in cloud-native technology. The event featured more than 30 international speakers who shared insights on Kubernetes optimization, security, and scalability. Key sessions included intelligent autoscaling with Karpenter and Amazon EKS, security hardening for compliance with PCI DSS and GDPR, enhanced visibility with API Gateway and OpenTelemetry, and the integration of Istio with KubeVirt for hybrid architectures. Additionally, discussions on cloud-native CI/CD migrations and sustainable green infrastructure practices highlighted practical strategies for maximizing cloud efficiency. This collaborative environment fostered innovation and knowledge sharing, reinforcing Guadalajara’s status as a burgeoning tech hub in Latin America. Author: Rodolfo Martinez, KCD Organizer
1
-
Guy Royse
Redis • 4 mil seguidores
It's not every day that I get to quote Dave Thomas—the founder of Wendy's, not the author of The Pragmatic Programmer—but I do in this podcast with Roberto Perez. Dave Thomas said that the most important bites of a burger are the first bite and the last bite. Those are the bites you remember. Those are the bites that influence your reaction to eating that burger—in other words, will you get another in the future. LLMs, it turns out, do something similar. They tend to remember stuff at the beginning of the context and the stuff at the end of the context. And sometimes struggle with the in the middle stuff. So keeping context small matters. The less middle you have, the less chance the middle is missed. And, of course, a smaller context is cheaper and faster too. Fewer tokens. Less time spent processing them. So smaller contexts are, generally speaking, better. Of course, just dropping messages off the back of the conversation to keep a small context doesn't solve the problem. The context needs to be tight, not truncated. To do this, you need Agentic Memory. In the podcast, I demo a simple chatbot that uses Agent Memory Server to provide just that. Watch it for all the details: https://lnkd.in/eBFACpYb
5
1 comentario -
Eryn Muetzel
Tensor9 • 2 mil seguidores
We just published a new post on the Tensor9 blog about a problem that comes up in almost every vendor conversation we have: what happens when your application depends on a managed service like DocumentDB, and your customer can't run on AWS. https://lnkd.in/gzamYh2d
6
-
Surabhi Kothari
DigiCert • 3 mil seguidores
Really excited about this one: Confluent is teaming up with the Visa Cash App RB F1 Team! As someone who gets to see firsthand how powerful real-time data can be, it’ll be amazing to see it fuel faster race-day calls, engineering breakthroughs, and even fan experiences. Read more here: https://cnfl.io/46LDD8Z
14
-
Alessandro Haag
MongoDB • 2 mil seguidores
When was the last time you typed just “Peru travel guide” into a search bar? It's likely that you asked a longer question, such as a complete sentence. That shift, powered by large language models and vector search, is reshaping how we find information. The future of search isn’t purely about AI models or keyword search alone — it’s about hybrid search, so results are smarter and more relevant. This MongoDB blog explains what to look for when choosing a hybrid search solution and why it’s becoming essential. https://lnkd.in/gkr8kuyS
1
-
💻 Daniele Frasca
DanAds • 2 mil seguidores
Lambda Durable Functions were developed to address the need for pausing a Lambda execution while allowing external work, such as an LLM generating a response, to continue without incurring idle VM costs or losing execution state. This challenge is not new. It’s not a “which is better” post it walks through the same real use case implemented both ways and looks at where complexity and cost actually live. https://lnkd.in/dBDdk94z #AWS #Serverless #CloudArchitecture #StepFunctions #AI
28
-
Jeffrey Baker
DevHawk • 22 mil seguidores
I’m intentionally expanding my network with people who run or lead outsourced software teams: development agencies nearshore/offshore delivery partners fractional engineering firms I’m building DevHawk, a product focused on delivery visibility inside engineering organizations — largely because most of the tools we all use today are built for reporting activity, not understanding how work actually moves through a team. They look busy. They don’t show friction. What I care about is how outsourced teams really operate: how work gets handed off, where reviews slow things down, how QA queues form, and what actually determines whether a project ships smoothly or quietly drifts. If you’re in this world, feel free to connect. This isn’t about exposing problems or “fixing” anyone — it’s about learning from operators who already know how hard delivery is at scale. Even if we never work together, I’d value being in the same network.
13
3 comentarios -
Vijender Singh
cloudEQ • 779 seguidores
We at cloudEQ enable faster, safer deliveries by combining standardization and governance to cut manual fixes, elastic agents with self-healing to remove delays, and GitOps with observability to ensure resilient, visible, and secure deployments. #Automation #DevSecOps #GitOps #AIOps #Observability
4
-
Steve Halvorson
2 mil seguidores
Abre has 200% growth since I joined 2 years ago and still proudly running our main application as a giant monolith 💪 🎉 What are we focused on this year? - Shipping key features that solve major problems for our clients - Refactoring legacy code so we can ship and debug faster - Code consolidation to reduce trips to our main database - Optimizing our main database for speed and performance - Adding caching - Optimizing image storage and rendering - Reducing latency What we are avoiding: - Refactoring into microservices - Overengineering - Kubernetes clusters and container orchestration - Expensive infrastructure - Adding complexity just because someone thinks it’s a good idea - Rewriting our application code in GO or Rust When you have a small team and a growing company, speed and optimization is more important than anything. Unnecessarily adding complexity creates barriers when solving problems for customers needs to be the number one focus!
32
2 comentarios -
Luciano Mammino
fourTheorem • 13 mil seguidores
🤩 Stoked to see a new major release of Middy supporting already many of the most recent announcements in #AWS #Lambda. This includes: - Durable Functions 🔥 - Tenant Isolation Mode - Multi Concurrency on Lambda Managed Instances - And even LLRT! ⚡️ #serverless #opensource #oss
7
-
Shakti Pawar
Bhavans College • 320 seguidores
Demystifying Terraform Modules, A Practical Primer. 🚀 Over the past few weeks, I invested focused time and effort into putting together a beginner-to-intermediate guide on Terraform Modules, aimed at helping engineers structure infrastructure as code with clarity and reusability. In this article, you'll find: ✅ Core principles of modules ✅ Scenario based learning to design modules ✅ Remote state and significance of workspaces ✅ GitHub repo with functional code, so you can follow along, clone, or adapt as needed ✅ Folder structures, file naming conventions, and best practices ✅ Tips for writing scalable, readable code Every diagram (except the banner 🙂) has been hand designed to enhance understanding, not just imported. The goal was to make this guide informative, visually intuitive and practically useful for developers who are starting their journey with Terraform. I’d love if you give it a read and share your thoughts in the comments, especially around what resonated and what could be improved. If you find it useful, please consider resharing it to help it reach more tech folks looking to get better with Terraform !! https://lnkd.in/dR9fdqPj #terraform #modules #remotestate #devops #workspace #aws
2
Otras personas con el nombre de Leo M.
-
Leo Jaffer
París -
Leo M.
Valencia y alrededores -
Leo M.
AI Senior Engineer
Tokio -
Leo Marine
Región IV-A (Calabarzón), Filipinas -
Leo Cole
Pattaya
Hay 748 personas más con el nombre de Leo M. en LinkedIn
Ver a otras personas con el nombre de Leo M.