Miguel Angel Fajardo

Technologist, Manager, Runner, Writer, Photographer. VP of Engineering at Clidrive

[Miguel Angel Fajardo @ma_bits]

Hemos creado este meetup sobre una de las áreas de Tech que encuentro más interesantes y relevantes #dataeng https://t.co/0UPDltd5Hr

[Eckler ✦ @daniel_eckler]

21 Amazing AI.llusions 🌀
and how to make them 🔨

[Miguel Angel Fajardo @ma_bits]

Great description of tech leadership

[Thiago Ghisi @thiagoghisi]

How Technical should Engineering Managers be?

Technical enough to understand and be able to contribute with relevant ideas to: Costs, Performance, Reliability, Operations and Productivity.

If we use @simonbrown’s C4 model as a guideline: EMs should not necessarilly be or have a deep understand at the Code level, but more at the System Context, Containers and Components level. They should be experts at the Context & Containers' levels of their team's systems.

EMs should be technical enough to:

* Understand main infra/cloud cost drivers, monitor them, and pivot execution as needed.
* Actively monitor and improve their team on-call, reduce incidents, and increase post-mortem effectiveness to boost team productivity.
* Identify major causes of latency and single points of failure (SPOF) in their system's architecture.
* Provide detailed technical explanations & descriptions of their domain's main flows, highlighting opportunities, risks, and technical debt.
* Recognize productivity bottlenecks in the codebase and identify high-leverage investment opportunities for technical debt or migrations.
* Inspect the quality, size & cadence of ongoing pull requests, new features & architecture evolution.
* Independently consume and engage with RFCs and technical documentation related to their domains ans make suggestions for improvements.
* Assess technical solutions for unintended risks, common failure modes, scope reduction or more incremental deliveries.

In short, EMs should be technical enough to make contributions into three key areas:

1- Cost & Operational Efficiency: Understanding the cost drivers in infra/cloud, managing on-calls, operational burden and incidents/postmortems. The focus here is on proactively monitoring and pivoting day-to-day to keep things smooth and cost-effective. Think of this role as being the 'supply chain manager' for your tech stack. Just like in manufacturing, where every component, from raw materials to labor, impacts the cost and efficiency of the final product, every architectural decision and operational process in tech has financial implications.

2- System Reliability & Performance: This includes grasping the root causes of latency and identifying Single Points of Failure (SPOF) in the system. Think of it as being the 'health inspector' for their tech architecture, ensuring everything is up to code for maximum reliability.

3- Technical Strategy & Risk Management: Whether it's understanding productivity bottlenecks, technical debt, or evaluating new technical solutions, this is about making high-impact, long-term decisions. Think of it as being an 'investment banker' of their codebases & systems, directing resources toward high-leverage opportunities and away from risks.

More on that on the part II of my interview with @DanLinesLB for the @DevInterrupted podcast.

Link below 👇:

[David Bonilla @david_bonilla]

Hackathon de #IA el 29-30 de mayo, organizado por @IEbusiness y @ClibrainAI, con UN MONTÓN de premios.
https://t.co/Obr94F18mK

[Cory House @housecor]

Common software dev mistakes are at the extremes:

1. Under-engineering
2. Over-engineering

Under-engineering:
No CI
No reviews
Weak types
Hard coding
Tight coupling
Manual deploys
Frequent copy/paste
Insufficient flexibility
No automated checks
No validation/error checks

1/2👇

[Dave Anderson @scarletinked]

Moving from software engineer to senior software engineer is a big step.

Most engineers get hung up on assuming that their technical depth is the key to growing their position. But is that really what's holding them back?

🧵

[Miguel Angel Fajardo @ma_bits]

Notion + AI = magic 🪄 Join me in the alpha waitlist! https://t.co/2RW0KLlOat

[Miguel Angel Fajardo @ma_bits]

"Narratives are (...) often wrong, a diversion, or based on theory without any tether to reality. Narratives that are right, follow from products, which means that if you want to control the narrative in the long run, you have to build the product first" https://t.co/ucq640DEvd

[George from 🕹prodmgmt.world @nurijanian]

12 Signs You’re Working in a Feature Factory

(source: @johncutlefish)

[Sid Palas @sidpalas]

DevOps is dead 💀, long live Platform Engineering!

1) Developers don't like dealing with infra
2) Companies need control of their infra as they grow

Platform Engineering (and Internal Developer Platforms) enable these two facts to coexist. Here's how:

(1/n)

[Jorge el Flechas 🏹 @HeavydePeloCort]

Ayer, 25 de julio a las 22:40 se cumplieron 30 años del lanzamiento de la flecha que encendió el pebetero olímpico en Barcelona 92.

Se ha hablado mucho de esto, pero aquí va un hilo con mi toque, centrándome en todos los detalles frikis arqueros que he conseguido encontrar

[Rob Lennon 🗯 | AI Whisperer @thatroblennon]

Google Docs is used by 1.8+ billion people worldwide.

The recent updates are perfection.

11 g-docs features so good, you'll kick yourself if you didn't know:

[10-K Diver @10kdiver]

1/

Get a cup of coffee.

Many of us are grappling with high inflation. We are worried about how inflation is going to impact our portfolios, and our costs of living.

In this thread, I'll walk you through why inflation is so dangerous for businesses and investors.

[Miguel Angel Fajardo @ma_bits]

Haciendo los impuestos. Tiempo en rellenar venta de acciones USA en impuestos estadounidenses -> 10 minutos. Tiempo en impuestos españoles -> llevo 2h. Consiguen que se te quiten las ganas de invertir en nada...

[Miguel Angel Fajardo @ma_bits]

True story 😅

[Sergio Pereira @SergioRocks]

Some of the most hated messages a CTO can receive from a Software Engineer:

- "Hey, got a minute?"

- "Can we have a chat?"

- "I need to tell you something, when is the best time?"

This isn't obvious, but CTOs instinctively think the Engineer will leave the company.

1/4

[Miguel Angel Fajardo @ma_bits]

@OrtaSastre @CDLeganes @U_D_Almeria Y también por qué canal se podrán a la venta gracias

[Miguel Angel Fajardo @ma_bits]

San Francisco 2011, one of the best concerts I remember attending - ever. Will miss the Foos, rest in peace @taylorhawkins @foofighters

[Miguel Angel Fajardo @ma_bits]

😥

[Ninety Nine @somosninetynine]

¡Siguen las novedades en Ninety Nine! 🔥

Tras añadir las órdenes Stop Loss hace unas semanas, ahora tocan las gráficas avanzadas que muchos de vosotros nos habíais pedido, ¡ya disponibles en la última versión de la app! 📈

[Jennifer Griffin @JenGriffinFNC]

If you read one thing today: Please read every word of this excellent interview with Stephen Kotkin, a leading historian on Stalin, to understand what is happening right now in Ukraine, Putin’s miscalculation and the words of Sun Tzu. https://t.co/rh1lYkJsBG