Sign in

João Alves

@joaoqalves.net
73 followers 27 following 126 posts

2x Dad. Husband. Head of Engineering @Adevinta. Building abistama.com and rotahog.com Opinions are my own. Writes in PT/ES/EN/CAT

PostsRepliesMedia
João Alves @joaoqalves.net · 18/02/2026
Should engineering managers become hands-on again? If even 20% of what we’re seeing is real, productivity, speed, and cost structures will change. Leadership blind spots at inflection points are expensive. I think eng leaders can’t afford to find it out.
110
João Alves @joaoqalves.net · 28/01/2026
🧵 Yesterday, after a discussion on Discord, and today with @sdepablos, I got inspired. AI is not just changing how software is built. It’s changing how the industry operated for years. The loop is: smaller teams → cheaper feature parity → margin pressure → labor shifts → capital reallocates. 👇
110
João Alves @joaoqalves.net · 27/01/2026
After reading the article on software industrialization, this is my (current) take on Software Engineering + AI. Where am I wrong?
000
João Alves @joaoqalves.net · 20/01/2026
“I already raised my concerns. If they chose to ignore them, that’s on them.” I heard it many times from Tech Leads. But this is not (tech) leadership at all. So... I wrote about it. 👇
110
João Alves @joaoqalves.net · 13/01/2026
As a Tech Lead, “we need more speed” always comes up. Without KPIs, SLIs, and SLOs, that turns into opinions: “I think it’s fine.” // “I think it’s risky.” This is why Operational Excellence matters. 👇
110
João Alves @joaoqalves.net · 09/01/2026
AI won’t break your company (yet?). It will expose slow org design, fragile delivery pipelines, and leadership habits that no longer scale. I wrote down what actually needs to change for CTOs running 100+ engineers. 👇
120
João Alves @joaoqalves.net · 18/12/2025
Si eres Tech Lead y tus métricas no cambian las decisiones, no te están ayudando. KPIs, SLIs y SLOs no van de medir más. Van de dejar de discutir opiniones y empezar a operar el sistema. Nuevo artículo 👇
100
João Alves @joaoqalves.net · 16/12/2025
I joined mytaxi as a Tech Lead in 2018 and quickly realized something uncomfortable: having good ideas and the title did not mean people would listen. What finally changed things was simpler. A small tool and sitting side by side with people, solving problems. Full article 👇
130
João Alves @joaoqalves.net · 15/12/2025
“Why do you blog?” I learned most of what I know by watching great teams up close and trying to apply their habits in the real world. Writing is my way of passing that learning forward. Happy to see a positive impact.
010
João Alves @joaoqalves.net · 11/12/2025
El otro día, un pequeño post de Félix López me inspiró. Los títulos no te dan influencia por arte de magia. Si eres TL y tu equipo no te hace caso, no suele ser porque tu estrategia sea mala. Suele ser porque aún no existe confianza. ¿Qué me gustaría haber sabido en 2018? 👇
100
João Alves @joaoqalves.net · 09/12/2025
The Tech Lead role is among the most misunderstood in engineering teams. It’s not “the best coder”, and it should never be a bottleneck. I wrote a post on what good Tech Leads actually do, the signals to look for, and how EMs can better support them.
110
João Alves @joaoqalves.net · 04/12/2025
¿Qué hace realmente un Tech Lead? Y, sobre todo, ¿cómo saber si lo estás haciendo bien? Hablo de arquitectura, calidad, alcance, principios operativos y del verdadero impacto de un TL: crear un equipo que toma mejores decisiones sin depender de él. 👇
100
João Alves @joaoqalves.net · 02/12/2025
1/2 Considering the success of my article in Spanish, I’ve translated it to English: “When software becomes fast food” AI commoditizes code. So the bottleneck shifts and intensifies elsewhere (CI/CD, architecture, taste, judgment, etc.).
111
João Alves @joaoqalves.net · 27/11/2025
Hoy os traigo un artículo sobre algo que a veces olvidamos: no debemos enamorarnos de la tecnología, sino de nuestros usuarios. Suena fácil y obvio, pero los equipos de ingeniería se olvidan a menudo de ello. open.substack.com/pub/esjoaoqa...
open.substack.com
Bricks of Love: enamórate de tus usuarios, no de tu tecnología
Cómo las actualizaciones semanales pueden reforzar la cultura, el propósito y la empatía en tu equipo
010
João Alves @joaoqalves.net · 25/11/2025
I failed two promotion attempts even when everything “looked right” on paper. In a post-ZIRP world, doing great work isn’t enough. You need level n+1 stories, visibility outside your team, and impact across boundaries. Full article below.
Whiteboard sketch outlining three promotion mistakes: "potential" trap, competition favors proven experience, and visibility gap limiting cross-team trust.
110
João Alves @joaoqalves.net · 24/11/2025
Nueva edición de “El doble clic” - Gestión de contexto en Claude Code, cómo Tinybird reforzó su infraestructura en entornos multi-tenant y mucho más. Aquí 👇 enespanol.joaoqalves.net/p/el-doble-...
010
João Alves @joaoqalves.net · 20/11/2025
Private Equity en tech: todo lo que siempre quisiste saber enespanol.joaoqalves.net/p/private-eq...
enespanol.joaoqalves.net
Private Equity en tech: todo lo que siempre quisiste saber
Qué es, cómo funciona y qué implica para quienes trabajamos en tecnología
010
João Alves @joaoqalves.net · 19/11/2025
Doing active/active K8s setup is hard. In many cases — unless it’s a regional service with its own database, etc — it comes with a lot of hidden complexities. @tjamet writes about our experience at Adevinta doing it. Must read: medium.com/learnings-f...
110
João Alves @joaoqalves.net · 18/11/2025
Cloudflare down creating this huge impact is a nice reminder of why I’m a happy shareholder since a long time ago.
010
João Alves @joaoqalves.net · 18/11/2025
“Meta evaluating AI fluency” is making people mad about micromanagement. Using metrics as prompts, not targets, can solve issues and boost performance. Like DORA metrics at Adevinta, AI fluency needs clarity. Full article: world.hey.com/joaoqalves/...
world.hey.com
AI adoption needs light, not hope
As per last week’s rumors, Meta will judge employee performance based on AI skills. Nothing new. Other companies, like Zapier, have even published what they expect “AI fluency” for all new hires: Every time a company announces “AI usage dashboards,” people get mad. My timeline on X gets full of surveillance, micromanagement, and bullsh...
110
João Alves @joaoqalves.net · 17/11/2025
Managing EN/ES accounts and blogs with diverse content is more challenging than I anticipated, but I’m really enjoying it. Tomorrow, I'll post about how Meta and others are measuring AI adoption and making it a requirement in performance reviews. Stay tuned!
010
João Alves @joaoqalves.net · 17/11/2025
Hoy lanzo “El doble clic” en mi blog. Cada semana compartiré lecturas, charlas y enlaces que me hayan gustado. Perspectivas de @paoramen.com, @eferro.net, @elwatto.bsky.social y más! Si te gustan la tecnología, los productos y las startups, ¡te interesará! 👇
enespanol.joaoqalves.net
El doble clic — Semana del 17 de noviembre
Ideas, artículos y descubrimientos de la semana
231
João Alves @joaoqalves.net · 14/11/2025
Mi tesis sobre la IA: abarata picar código y desplaza el valor hacia el criterio. Habrá mucho “software fast-food”, pero también una mayor necesidad de expertos que sepan diseñar, integrar y tomar decisiones. open.substack.com/pub/esjoaoqa...
open.substack.com
Cuando el software se vuelve “fast food”
La nueva frontera no es programar, sino decidir qué merece construirse
000
João Alves @joaoqalves.net · 09/11/2025
More updated than ever. 2020s engineering leaders must be more into the details. That’s a feature and not a bug. “Servant leadership” (misapplied) created a lot of peace time engineering leaders. Full post on world.hey.com/joaoqalves/...
120
João Alves @joaoqalves.net · 03/11/2025
On the AI Agents vs workflows, my mental model is a sports team. * An agent is like a player knowing specific skills (speed, dribbling, …) * A workflow is like a tactic, using AI agents to achieve a goal (eg, score)
000
João Alves @joaoqalves.net · 02/11/2025
Cloud/FinOps Pro Tip: run Claud Code on AWS Bedrock, as they have the models available. Two benefits: 1. Built-in access control with AWS and temporary credentials. 2. It contributes to your AWS expenditure/commitment, allowing you to leverage this cost for volume discounts.
010
João Alves @joaoqalves.net · 02/11/2025
Un poco a contracorriente: no todo el esfuerzo es tóxico. open.substack.com/pub/esjoaoqa...
open.substack.com
El esfuerzo no es tóxico
Nota: Este artículo es una traducción al español del original en inglés, escrito por mí.
000
João Alves @joaoqalves.net · 31/10/2025
“How do you write so many articles in such a short time frame? You must be using AI” Nope. I use Grammarly to (re-)write as I’m not a native English guy. I use ChatGPT mainly to create an illustration, as otherwise HEY World (my blogging provider) puts my photo on it.
100
João Alves @joaoqalves.net · 29/10/2025
"538 microservices? What a mess." Four years ago, I wrote Disasters I've Seen in a Microservices World. I thought by now we'd have solved most of them. We didn't. We just learned to live with the chaos. Link below 👇
A graph showing how risk changes: too few services? monolith, and potentially problems when deploying. A lot of services? A headache too
111
João Alves @joaoqalves.net · 28/10/2025
I've written a sequel to "Disasters I've Seen in a Microservices World," my most-read blog post. Ten disasters later, it's still chaotic, and with the rise of AI agents, it's bound to get worse. Planning to publish soon. Anyone want to read it before I do?
 Four years later, I'm still seeing the same patterns, just dressed in different frameworks, clouds, and YAML dialects. The tools evolved, but the fundamentals didn't: distributed systems remain distributed, humans remain human, and complexity remains undefeated.  What's coming next will make this even more interesting. We're now trying to build AI agents: autonomous, stateful systems that communicate with each other, make probabilistic decisions, and respond to unpredictable inputs. In other words: distributed systems with opinions. What could go wrong? The same fallacies apply, just at a different layer. Latency, consistency, observability, determinism. None of them magically disappears because the component now "thinks."
030
João Alves @joaoqalves.net · 27/10/2025
Sigo contando cosillas :) Hoy inauguro "Desde mi terminal". También en español, pero en formato largo. Explico las razones de crear una cuenta específica para contenido en español. Si queréis leerlo, paso el enlace en el post de abajo. enespanol.joaoqalves.net/p/la-desven...
substack.com
La desventaja de ser plurilingüe
Lo complicado no es hablar varios idiomas, sino decidir en cuál contar tu historia
010
João Alves @joaoqalves.net · 24/10/2025
Everyone talks about multi-cloud and reliability. Here’s what it looked like in practice when I joined Adevinta five years ago. The company had just agreed to acquire the eBay Classifieds Group, its secondhand marketplaces division. On the table: private cloud, GCP, and AWS.
Multi-cloud made it to the final spreadsheet, but only so everyone could see how crazy expensive it would be.  In the past, AWS and other hyperscalers had single points of failure. As @GergelyOrosz  mentions in the latest Pragmatic Engineer newsletter, there are still some components that are “global” and run on a single region (us-east-1). That’s not the norm, and the vast majority of services can be run in multiple areas. It’s up to the business to understand (a) what its critical paths are and (b) what its risk appetite is versus the cost of running multi-region or even multi-cloud/hybrid setups for specific scenarios.  For some businesses, 24/7 uptime is more critical than for others. Take Glovo or Uber, for example: there’s a high per-minute cost during peak hours. Why? The cost of switching is low. Users also have Lyft, FREE NOW, Just Eat, and Uber Eats on their phones, so they can easily open another app to get from A to B or order a meal.  If one of Adevinta’s portals (secondhand, real estate, or motors) is down at 2 a.m. on a Friday, that’s mostly OK. Yes, there are peak times, but there’s also a counterbalance thanks to (a) network effects — a lot of the inventory on @leboncoin  isn’t listed anywhere else; everyone in France uses it — and (b) low time sensitivity. If you’re looking for a flat or a car, it can wait a bit.  Multi-cloud (and sometimes even multi-region) sounds smart until you price it, model the risks, and realize: it’s usually not worth it. Reliability is an architecture problem, not a cloud problem.
000
João Alves @joaoqalves.net · 23/10/2025
Meta laying off a chunk of the FAIR (frontier research AI lab) led by @ylecun was not in my bingo card for 2025. Any clues why? aftermath after acquisition of @alexandr_wang and the team?
000
João Alves @joaoqalves.net · 22/10/2025
.@karpathy says the best way to learn is to build things. He’s right, but as engineers, we know that’s only half the story. Writing, teaching, or preparing a talk forces you to understand what you have built. That’s what this post is about. Link below 👇
Visualization from Jason Roberts with x-axis on "Doing" and y-axis on "talking". The best is the intersection between them
100
João Alves @joaoqalves.net · 21/10/2025
Today in the incident review meeting: “We should prepare for AWS disasters. Multi-cloud.” Checks numbers... “Yeah, it’s cheaper to have the same downtime as AWS.” Every. Single. Time.
020
João Alves @joaoqalves.net · 20/10/2025
Do you know these guys who intern 1-2 months at a company to fix "that one thing" that annoys them about a product? I need to do that @37signals. Goal 1: add subdomains to Hey World. Goal 2: Add a simple "Plausible-alike" analytics for the posts. That's it. The End.
000
João Alves @joaoqalves.net · 20/10/2025
Many people don’t know, but AWS has a few services they run “globally” on us-east-1. So it’s not the same to have an outage there or in another big region (eg eu-west-1). Also likely the reason why Vercel and others are down
010
João Alves @joaoqalves.net · 20/10/2025
LLMs changed everything for me. I got my first money on @hirotahog, thanks to it. Before I had lots of ideas but with my limited time, I threw the towel before I went live. Now I go from idea to prod quickly and I try a lot of stuff. FAFO
010
João Alves @joaoqalves.net · 19/10/2025
At abistama.com, we’re cooking something new. 🧑‍🍳
000
João Alves @joaoqalves.net · 17/10/2025
2025 is my "back to blogging" year! After 1.5 years of hiatus, I've written eight blog posts this year. The fun part for me? Talking about SaaS, Private Equity, being a Head of Eng, and more.
320
João Alves @joaoqalves.net · 16/10/2025
I wrote a post, after @factorialapp's latest announcement: back in the office, five days a week 🔥 Remote is a tool, not dogma. Why? Juniors struggle, culture slips. Hybrid needs rules; remote edges, small teams. Tradeoffs. Full post below
100
João Alves @joaoqalves.net · 09/10/2025
I’ve spent three years "vibe coding" with LLMs. Shipping side projects I’d never have had time to build otherwise. In terms of implementation, I agree with @iagolast and I don't feel it's "magic" anymore, but I do feel a lot more productive. Full post below.
112
João Alves @joaoqalves.net · 25/09/2025
Does anyone else notice how the trend of responding to "Oh, layoffs at company X. I'm sad for you" with "At company Y, we're hiring" feels a bit off? Companies often discuss "empathy" and then...
000
João Alves @joaoqalves.net · 26/08/2025
I built a Slack-to-Jira support bot a while ago. It sat on the shelf: useful, but not perfect. Instead of letting it rot, I cleaned it up and open-sourced it. Inspired by @dhh, Omarchy, and the reminder that you can just share your work. Wanna know more about it? 👇
100
João Alves @joaoqalves.net · 25/08/2025
I’m open sourcing Abistama’s support hero! 🦸 ⚡ Emoji → Jira tickets 🤖 AI-powered summaries 📊 CSAT surveys 🔗 Slack & Jira integration The biz model failed, but maybe it helps your team. Repo in the post below 👇
100
João Alves @joaoqalves.net · 30/07/2025
The Zero Interest Rate Period (ZIRP) encouraged Engineering Managers to prioritize their team’s happiness and feelings almost like a union representative. That is not the job. These folks are having a hard-time the post-ZIRP era.
000
João Alves @joaoqalves.net · 01/07/2025
The two main blockers for AI use in sales, marketing, and non-tech departments are: * Data access: Lack of APIs or costly beyond standard reports/dashboards. * Credit card access: Limited by company systems. People need self-sufficiency to test niche tools.
010
João Alves @joaoqalves.net · 23/06/2025
The other day, I had the chance to have a conversation with @agilestateofM about DevOps, Platform Engineering, SLIs, SLOs and more. It’s meant for people that are start looking into all of this. >>>
100
João Alves @joaoqalves.net · 16/06/2025
🚩"Not a 9-5 job" in a job post: is it a red flag? Some roles, such as those at OpenAI or Anthropic, require extra hours but offer career growth, equity, or a mission-driven impact. Effort can be a choice, not a trap, if the upside’s real. Read more: bit.ly/3HIJKlw
000
João Alves @joaoqalves.net · 05/06/2025
"If yogurts have expiration dates, why don't your nodes?". Simple, to-the-point article by @danielillu on keeping an eye on old K8s nodes and leveraging things like "node TTL" from auto-scalers like Karpenter. medium.com/learnings-f...
medium.com
If Yogurts Have Expiration Dates, Why Don’t Your Nodes?
When was the last time you checked the “freshness” of your Kubernetes nodes?
010