Alvaro Moya

Fundador de hub del mejor talento tech senior, y Tech Sherpas, comunidad de liderazgo. CTO experimentado. Fundador, inversor y advisor

[Alvaro Moya @AlvaroRMoya]

@javilop Muy alineado además con ese nuevo concepto de founders que usan su marca personal como altavoz de la marca, vease @bchesky que genera más tráfico a @Airbnb que la propia marca

[Alvaro Moya @AlvaroRMoya]

Ya estamos en la siguiente etapa de IA: LLMs descentralizados 🚀

[Fetch.ai @Fetch_ai]

https://t.co/hMqVKk3bqc

[Alvaro Moya @AlvaroRMoya]

#techsherpas 🔥🔥🔥

[Alvaro Moya @AlvaroRMoya]

Aprende a construir el equipo #deeptech de tus sueños

Hoy a las 17:00 en Playground Stage con panel de lujo.

Te vienes?

[Alvaro Moya @AlvaroRMoya]

Sin palabras...ESPECTACULAR el recibimiento de la charla "El developer aumentado por #IA" en la #codemotionmadrid24. +300 GRACIAS!!

Si no estuviste, repito el miércoles online, con demo inédita. Te apuntas en https://t.co/4hzEwoW7U9

[Alvaro Moya @AlvaroRMoya]

En respuesta a los que piensan que la IA va a borrar millones de trabajos para siempre

[Aaron Levie @levie]

One of the most common concerns about AI is the risk that it takes a meaningful portion of jobs that humans currently do, leading to major economic dislocation. Often these headlines come out of economic studies that look at various job functions and estimate the impact that AI could have on these roles, and then extrapolates the resulting labor impact. What these reports generally get wrong is the analysis is done in a vacuum, explicitly ignoring the decisions that companies actually make when presented with productivity gains introduced by a new technology -- especially given the competitive nature of most industries.

The thinking generally goes that if a company could, say, be 50% more productive in a particular function, it would mean a commensurate reduction of jobs in that area. For instance, if a certain function (like engineering or sales) required 10 units of labor before, then with a 50% gain in productivity, in the future that same function would now only need ~7 units of labor. The challenge with this type of thinking is that it assumes that companies have maximized the amount of labor they wish they had for a particular function, when in reality many functions are only staffed at the level the company can afford. Further, it assumes that a company is not in a competitive field, and that the company would be complacent and happy about generating the same output as before, just with less costs. Finally, it ignores the fact that productivity gains in a market will lead to increased response from competition, which companies equally have to respond to with more productivity not necessarily more profit. Time and time again this is the type of flawed thinking that we tend to get out of broad economic studies on the labor needs in the economy.

To break this down and make it practical, I thought I'd illustrate the point with the example of an engineering function -- one that already is seeing the benefits of AI starting to roll out. The numbers will all be kept simple, but you can change almost any variable and the point will remain the same. The key to thinking through job impacts is to think through what happens a step or two *after* the productivity gain of AI is experienced.

So, imagine you're a software company that can afford to employee 10 engineers based on your current revenue. By default, those 10 engineers produce a certain amount of output of product that you then sell to customers. If you're like almost any company on the planet, the list of things your customers want from your product far exceeds your ability to deliver those features any time soon with those 10 engineers. But the challenge, again, is that you can only afford those 10 engineers at today's revenue level. So, you decide to implement AI, and the absolute best case scenario happens: each engineer becomes magically 50% more productive. Overnight, you now have the equivalent of 15 engineers working in your company, for the previous cost of 10.

Finally, you can now build the next set of things on your product roadmap that your customers have been asking for. We can't assume it will be 50% more because there are new points of friction and coordination tax that emerge as you have 15 equivalent engineers, but let's say your output goes up meaningfully. Assuming you're acting in your best interests as a company, the features you build make your product that much more compelling, which means at some point (sooner or later) they should result in an incremental gain in revenue. Let's be somewhat conservative on what impact these new features will have on your product, but let's say they generate an incremental 10% of revenue over time or keep customers retained at a 10% greater rate (roughly the same financial benefit).

Now let's assess the downstream impact. Firstly, any growth of revenue will often lead to some functions in the business growing as well to support these new customers, which will directly create new jobs. But further, the company now has to decide whether it remains satisfied with its 10 engineers that have the output of 15, or with their incremental revenue should they hire even more engineers to build the *next* set of features that will make them even more compelling to customers. Unless this company is in some rare monopoly position, they likely will want to build the next set of features even faster than the last set to grow even more quickly. This then means AI has caused the company --counterintuitively-- to hire more engineers than before, because the productivity of each engineer is much higher, allowing them to generate more return per engineer, and thus more revenue.

What's interesting is this analogy works similarly for most functions in a business. In sales, if you could make sales reps 10% more productive (i.e. they sell 10% more of your products/services for the same cost), almost every company in the world would prefer to hire even more sales reps, instead of merely banking the incremental profit. That incremental sales productivity again would lead to downstream implications, like the need to deliver more features to customers, and thus more R&D hiring! Even back-office functions that don't as directly tie to revenue growth, often are a bottleneck to growth . If you can reduce the bottleneck -- say lawyers reviewing contracts, or people processing invoices-- cycle time in businesses accelerates, which almost always lets you serve more customers faster or grow more quickly, again letting a company reinvest those dollars.

In the end, when you step out of the vacuum of just the specific productivity gain of a particular job function, and look at how the whole system will adapt and improve due to that productivity gain, a very different picture of AI's impact on jobs will emerge. Yes there will absolutely be changes to what jobs become more or less in demand in the future, but the competitive nature of companies inevitably ensures that across the whole system companies will be focused on leveraging AI to become more productive.

[Distrito Talento Comunitat Valenciana @DD_Talento]

💡¡Consejos de emprendedor para emprendedores! Con @alvarormoya, CTO con más de 15 años de experiencia y fundador de @lidr_cto
🔸Redes de apoyo
🔸Solvencia
🔸Actitud
¡Más en la entrevista completa! https://t.co/BsH5YeucyF
#Liderazgo #Tecnología #CrecimientoPersonal

[Alvaro Moya @AlvaroRMoya]

Panelón de mujeres hoy en @techsherpas_ Barcelona hablando del rol del #developer aumentado por #ia

Gracias @AdevintaSpain 🙏

#techsherpas

[Tech Sherpas @techsherpas_]

Conmemoraremos el mes de la mujer con un EVENTAZO liderado y moderado al 100% por mujeres 💃

Si estás en #Barcelona prepárate porque discutiremos sobre el futuro de los roles tech con la irrupción de la #IA: amenazas y oportunidades.

Apúntate gratis ⤵️
https://t.co/zPbGdZSBNd

[Alvaro Moya @AlvaroRMoya]

La (R)evolución de la #IA ya está aquí, queramos los #developers o no. Toca dar la bienvenida en nuestro entorno de trabajo a Devin, @cursor_ai, @GitHubCopilot y demás

[Cognition @cognition]

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.

[Alvaro Moya @AlvaroRMoya]

Ya viene mi nueva masterclass para #techsherpas, como siempre 100% online, 100% gratuita.

Mañana hablaré de cómo va a cambiar el rol del #developer con la adopción masiva de asistentes de código #ia: cómo usar estas herramientas, qué habilidades serán clave...Te apuntas?

[Alvaro Moya @AlvaroRMoya]

@lexrodba @MWCHub @4YFN_MWC I'm in, so is @techsherpas_

[Alvaro Moya @AlvaroRMoya]

Poco a poco se crea el ecosistema con el que soñaba en 2019. GRACIAS 💛

[Tech Sherpas @techsherpas_]

5 eventos #techsherpas en 5 ciudades, 2 de ellas de estreno, y este es el resultado. INCREIBLE, muchísimas gracias a tod@s por organizar, hospedar, subiros al escenario, asistir y crear una comunidad única en el mundo hispanohablante.

Por muchos más y siempre mejores 🍻

[Alvaro Moya @AlvaroRMoya]

@nucliweb @LauraLacarra @nhan_bcn @MoureDev Muy guay pasar la tarde con vosotros, gracias por cambiar mi rumbo en el MWC 😂

[Alvaro Moya @AlvaroRMoya]

Enorme #techsherpas ayer, GRACIAS a todos los asistentes por estar, por las preguntas y por quedaros hasta el final. @moxiol y Patricia Infantes, descomunales. Y @AdevintaSpain siempre el mejor partner para estos saraos. Más en marzo con panelazo de mujeres @techsherpas_

[Otto Navarrette @onavarrette]

Ahora escuchando las diferentes vivencias y experiencias de los cracks @moxiol, Patricia Infantes & @AlvaroRMoya sobre Equipos de Ingeniería Eficientes, como parte de #techsherpas en las oficinas de @AdevintaSpain #Meetup

[Alvaro Moya @AlvaroRMoya]

El futuro del desarrollo de software: por supuesto aumentado por IA

Pásate por el stand de @AWSstartups en @4YFN_MWC y te enseño todo lo que viene y cómo adaptarte a esta (R)evolucion. Y si quieres charlar despues, mandame DM

[Alvaro Moya @AlvaroRMoya]

@pedropaparicio @amuino @CabifyTech @nowports @anabuigues @surfeandocambio Uno más, suma y sigue! Orgullo de moderador 🫶

[Alvaro Moya @AlvaroRMoya]

Estamos entrando en una nueva era en el mundo del software, podemos adaptarnos o no

https://t.co/7iXVqfJ8vT

#aipowereddev #citizendeveloper

[Alvaro Moya @AlvaroRMoya]

Vuelve #techsherpas a Barcelona. Proximo miercoles panelazo con @moxiol y Patricia Infante y tema controvertido. Nos vemos?

[Tech Sherpas @techsherpas_]

Si estás en #Barcelona prepárate para un EVENTAZO con #netwoking del bueno incluido

Traemos un panel de lujo para que descubras cómo aumentar la eficiencia de los equipos #tech y marcar la diferencia en las empresas 🚀

Reserva tu asiento gratis ⤵️
https://t.co/AtUxSVSivR