Name: C3 Dev Festival 2024
Start: 2024-06-14T07:00:00.000Z
End: 2024-06-15T19:00:00.000Z

Sientes las limitaciones de los LLMs? Pueden ser creativos, pero a veces carecen de precisión o se basan en información desactualizada. En esta masterclass, desglosaremos el proceso de construir y desplegar fácilmente un sistema de Generación con Recuperación Mejorada. Este enfoque te permite aprovechar el poder de los LLMs con el beneficio adicional de precisión factual e información actualizada.

¿Pueden los LLM aprender? Personalicemos un LLM para chatear con tus propios datos

Today's workshop introduced the concept of LLMs and their potential to free up time for software engineers. It discussed setting up LLMs to chat with proprietary data, utilizing retrieval augmented generation for small chats, and building a speaker recommendation application using this approach. The workshop also addressed concerns about running data on OpenAI and explored the process of splitting and storing data in a vector database. It concluded with the deployment of an end-to-end application using Genesio and invited attendees to provide feedback and stay in touch.

Feeling the limitations of LLMs? They can be creative, but sometimes lack accuracy or rely on outdated information. In this workshop, we’ll break down the process of building and easily deploying a Retrieval-Augmented Generation system. This approach enables you to leverage the power of LLMs with the added benefit of factual accuracy and up-to-date information.

Can LLMs Learn? Let’s Customize an LLM to Chat With Your Own Data

Andreia Ocanoaia

Has hecho tu trabajo. Has entregado funciones a tiempo. Incluso has optimizado algunos procesos en el camino. Sin embargo, aún te rechazan para una promoción o un aumento. En esta charla práctica, la Directora de Ingeniería y especialista en carreras tecnológicas, Anna McDougall, ofrece pasos directos y prácticos que puedes seguir en las próximas semanas, meses y años para asegurar promociones y aumentos. Desde las tareas que eliges hasta cómo las documentas y las 'vendes', ella te dará las herramientas que necesitas para tus objetivos profesionales.

Cómo convertir el trabajo de ingeniería en una promoción

This Talk discusses the process of building a toolkit and applying neurolinguistic programming techniques to succeed in software development. It emphasizes the importance of self-promotion and setting effective goals for career advancement. The concept of a brag bank is introduced as a tool to collect and remember achievements. The NNQ method is presented as a way to build a compelling case for promotion using names, numbers, and quotes. It also explores the idea of having a backup plan and considering alternative options when promotion is not feasible. Finally, the Talk touches on the importance of positive thinking, knowing when to move on, and avoiding excessive specialization.

You've done your job. You've delivered timely features. You even optimised some processes along the way. Yet you still get turned down for a promotion or a raise. In this practical talk, Engineering Director and tech career specialist Anna McDougall delivers direct, immediately actionable steps for what you can do in the next few weeks, months, and years to secure promotions and raises. From the tasks you choose to how you document and 'sell' them, she will give you the toolkit you need for your career goals.

How to Turn Engineering Work into a Promotion

Anna J McDougall

Realización de entrevistas e entrevistando en la era de las herramientas de IA

This talk explores the use of AI in the interviewing process for software engineering. It discusses the history of interviewing and the skills needed for future interviews. The speaker questions the relevance of traditional coding challenges and highlights the shift towards evaluating specific programming languages and debugging skills. The talk also emphasizes the importance of understanding the uses and limitations of AI and the value of communication skills in technical interviews.

Conducting Interviews and Interviewing in the Age of AI Tools

 Lindsey Simon

Prepárate para una competencia de velocidad, es ChatGPT versus servidor, compitiendo para construir una plataforma de visualización de datos desde cero a toda velocidad. ¿Quién ganará? Aceptaremos el desafío de reconstruir una plataforma de visualización de generación de energía, tomando inspiración de GridWatch y el Energy Dashboard.

¿Quién es más rápido construyendo una plataforma de visualización de datos de generación de energía: ChatGPT o un desarrollador?

Today's Talk discusses the competition between a developer and ChatGPT in building a data visualization platform. Generative AI is widely used, but ChatGPT is not a direct replacement for developers. Prompt engineering enhances ChatGPT's performance. The future of AI is promising, with open source models and proactive AI agents on the rise. Leveraging prompt engineering and dedicated LLM tools can improve code generation and automation.

Gear up for a speed competition, it's ChatGPT versus yours truly, racing to build a data visualisation platform from scratch at top speed. Who will win? We’ll be taking on the challenge of reconstructing an energy generation visualisation platform, drawing inspiration from the likes of GridWatch and the Energy Dashboard.

Who’s Faster at Building an Energy Generation Data Visualisation Platform: ChatGPT or a Developer?

Chloe Caron

Qué puede hacer, no puede hacer y no debería hacer la IA en los juegos

AI in game development has evolved rapidly, with generative AI being a focus. However, game developers like Romero Games have concerns about ethics and prefer using AI to automate processes and make creative work easier. AI has been used in games for decades, from path-finding AI to decision trees. Procedural world building and advanced AI technology are pushing the boundaries of FPS games. Different teams within a company have different approaches to the use of AI, depending on their specific needs and requirements.

What AI Can, Can’t, and Shouldn’t Do for Games

John Romero

Aprovecha el poder de la IA en tu aplicación

This Talk covers various aspects of artificial intelligence and user experience in software development. It explores the evolution and capabilities of large language models, the importance of prompt engineering, and the need to design AI applications with human users in mind. The Talk also emphasizes the need to defensively design for AI failure, consider user happiness, and address the responsibility and risks of AI implementation. It concludes with recommendations for further reading and highlights the importance of trustworthiness in AI code tools.

Bring the Power of AI to Your Application

Krzysztof Cieślak

Menos desorden, más poder: Aprovecha el poder de la plataforma web

This talk focuses on the powerful features of CSS and HTML that can level up developer skills and enhance web UI. Scroll-driven animations, popover API, and anchor positioning are explored as ways to create dynamic effects, improve performance, and increase accessibility. The talk also emphasizes the benefits of building presentations with CSS and HTML, separating logic from styling, and leveraging core platform features. Wishlist features for the web platform and the challenges of pushing updates across browsers are discussed.

Less Cruft, More Power: Leverage the Power of the Web Platform

Una Kravets

En Star Wars, los Pit Droids son droides de reparación diseñados para mantener los vehículos de carreras "podracers". Estos droides tienen una altura de 1.2 metros y pueden plegarse cuando no están en uso. Su comportamiento divertido se explica de tal manera que fueron programados con un sentido de urgencia pero sin suficiente capacidad de procesamiento para realizar tareas complejas.Te mostraré cómo construí un Pit Droid realista y lo potencié con NVIDIA Jetson Orin Nano. El droide puede realizar detección de objetos de IA, mover su cabeza hacia los objetos y más. También verás otros proyectos de droides en los que he trabajado.Publicación de NVIDIA Developer: https://blogs.nvidia.com/blog/2023/08/03/goran-vuksic-pit-droid/Proyecto en Hackster: https://www.hackster.io/gvuksic/nvidia-jetson-orin-nano-powered-pit-droid-7da0e8A través de esta sesión, aprenderás:- cómo se ensambló este robot,- sobre Azure AI Studio y Azure Custom Vision,- cómo preparar y etiquetar fácilmente imágenes para el entrenamiento del modelo,- cómo entrenar un modelo para la detección de objetos,- analizar imágenes de la cámara del robot,- controlar motores y otros dispositivos IoT conectados al robot,- y mucho más.¡Espero que esta sesión te brinde una gran introducción a la IA y IoT, e inspire a construir proyectos similares por tu cuenta!

El Poder de la Ingeniería: Dar Vida a tu Propio Compañero de Star Wars

May 25th, 1977, the first Star Wars movie inspired generations with its space travel and lightsaber fights. Goran Vukicic built replicas of the P-Droid and found a community of designers who sell 3D designs for printing. Bringing the droid to a conference is challenging but rewarding. The NVIDIA Jetson Ori Nano is a powerful device for running AI models. Building Star Wars droids at home is possible with open-source development.

In Star Wars, Pit Droids are repair droids designed to maintain racing vehicles "podracers". These droids are 1.2 meters in height and can fold when not in use. Their funny behavior is explained in a way that they were programmed with a sense of urgency but without enough processing power to perform some complex tasks.I will show you how I built a realistic Pit Droid and empowered it with NVIDIA Jetson Orin Nano. The droid can perform AI object detection, move its head toward the objects, and more. You will also see some other droid projects I worked on.NVIDIA Developer post: https://blogs.nvidia.com/blog/2023/08/03/goran-vuksic-pit-droid/Hackster project: https://www.hackster.io/gvuksic/nvidia-jetson-orin-nano-powered-pit-droid-7da0e8Through this session, you will:- hear how this robot was assembled,- learn about Azure AI Studio &amp; Azure Custom Vision- learn how to easily prepare and tag images for model training,- see how to train a model for object detection,- analyse images from the camera of the robot,- control motor and other IoT devices connected to the robot,- and much more.I hope this session will give you a great introduction to AI and IoT, and inspire you to build similar projects on your own!"

The Force of Engineering: Bringing Your Own Star Wars Sidekick to Life

Goran Vuksic

La revolución en curso de la IA nos presenta oportunidades, desafíos y responsabilidades únicas para diseñar nuestro futuro. Aprende cómo ejercitar tus habilidades de pensamiento crítico cuando se trata de integrar la IA en tu oficio de diseño, y cómo construir una sólida mentalidad ética en torno a la toma de decisiones de diseño en la Era de la IA. Guiados por Ioana Teleanu, la Diseñadora de Producto Principal de IA en Miro, exploraremos los principales temas en los que debemos reflexionar como diseñadores que participan en la formación del futuro de la humanidad.

AI + UX: Diseño de Producto para Experiencias Inteligentes

AI design challenges include bias, safety, and security. Trust and transparency are important in AI. Design principles for AI include user control, fighting bias, and promoting good decision-making. AI can enable the design process and investors expect to see it included in products. AI empowers individuals to create and share ideas, but managing expectations is crucial.

The unfolding AI revolution presents us with unique opportunities, challenges and responsibilities for designing our future. Learn how to exercise your critical thinking skills when it comes to integrating AI in your design craft, and how to build a solid ethical mindset around making design decisions in the Age of AI. Guided by Ioana Teleanu, the Lead Product Designer for AI at Miro, we'll explore the main themes that we need to reflect on as designers participating in shaping the future of humanity.

AI + UX: Product Design for Intelligent Experiences

Ioana Teleanu

A finales de los años 90, trabajé como locutor de noticias de radio y usaba las computadoras como hobby. Primero escribía programas bastante inútiles, luego jugaba videojuegos, era malo en ellos y analizaba los juegos para darme vidas infinitas. Luego tuve acceso a la web y todo cambió. Sabía que este era el medio en el que debía enfocar el resto de mi carrera. Aquí se relatan 25 años de desarrollo web profesional. Las tecnologías que vinieron y se fueron, las luchas por obtener los recursos que necesitaba y las cosas y personas maravillosas, locas y extravagantes que encontré. También obtendrás una visión de por qué algunos productos y tecnologías tuvieron éxito y por qué otros fracasaron.

35 Años de WWW: Trabajando como Creador de Contenido, Diseñador y Desarrollador con el Medio más Genial de Todos

The speaker, Christian Heilmann, is a VP of DevRel and has worked at Yahoo, Mozilla, and Microsoft. He emphasizes the importance of exploring and modifying games as a way to learn new skills and innovate. He also highlights the value of working in a limited environment and the opportunities it presents for creativity. He encourages developers to contribute to the web and be in control of their own creations. Lastly, he discusses the challenges of navigating the job market and the state of the web in relation to frameworks and npm packages.

Back in the late 90s, I worked as a radio newscaster and used computers as a hobby. First writing pretty pointless programs, then playing games, being bad at them and analysing the games how to give myself endless lives. Then I got access to the web and everything changed. I knew, this was the medium to support for the rest of my career. Here is a recount of 25 years of professional web development. The technologies that came and went, the struggles to get the resources I need and the wonderful, wild and bonkers things and people I encountered. And you also get an outlook why some products and technologies succeeded and why others failed.

35 Years of WWW: Working as a Content Creator, Designer and Developer With the Coolest Medium Ever

Christian Heilmann

Ser pragmático y comprender las tareas es crucial para lograr de manera efectiva tu actividad como desarrollador de software. Desafortunadamente, se necesita más para adquirir un software exitoso. En este punto, debes ir más allá y comprender la estrategia y las tácticas del ingeniero de software.Un buen software está más cerca del negocio y debe estar listo para cambiar con frecuencia. Volver a escribir todo el sistema desde cero se convierte en una tentación real. Las nuevas soluciones brillantes como microservicios pretenden resolver este problema utilizando nuevas tecnologías. Pero, ¿hay alguna garantía de que este sentimiento no volverá a surgir después de algún tiempo?No importa si es un servicio micro, nano o incluso atómico; ninguna nueva palabra de moda o tendencia puede ayudarnos con este problema.Entonces, aquí está la respuesta que has estado buscando: debes explorar múltiples tácticas y estrategias en las prácticas de ingeniería de software, como documentación, pruebas, diseño impulsado por dominio, persistencia, adopción de la nube y los diferentes estilos de diseño y arquitectura.Esta interacción cubrirá la guía definitiva para aprovechar al máximo la arquitectura y el diseño para garantizar una solución mejor, mantenible y evolutiva. También aprenderás cómo evitar sistemas complejos y luchar contra la herencia para lograr la innovación deseada con estabilidad.

Tácticas y Estrategias en el Desarrollo de Software: Cómo Alcanzar un Software Exitoso

As a software engineer, achieving success in software development requires having a strategy and tactics. However, obstacles such as unnecessary meetings and miscommunication with clients can hinder progress. The methodology used in software development is more important than the programming language. Soft engineering is about understanding strategy and tactics and finding efficient solutions to problems. Software architecture should be aligned with business goals and objectives. Documentation is important for scalability and avoiding miscommunication, but finding the right balance is key. Task efficiency and simplicity in code design are crucial. Embracing simplicity and improving documentation can lead to better software architecture. Communication and collaboration between management and engineering teams is essential for making informed decisions.

Being pragmatic and understanding the tasks are crucial for effectively achieving your activity as a software developer. Unfortunately more is needed to acquire successful software. At this point, you need to go beyond and understand the strategy and tactics of the software engineer.Good software is closer to business and needs to be ready to change often. Rewriting the whole system from scratch becomes a real temptation. New shiny solutions like microservices pretend to solve this problem using new technology. But is there any guarantee that this feeling won't come up again after some time?It does not matter if it is a micro, nano, or even atomic service; no new buzzword or trend can help us with this problem.So here's the answer you've been looking for: you must explore multiple tactics and strategies in software engineering practices, such as documentation, testing, domain-driven design, persistence, cloud adoption, and the different design and architecture styles.This interaction will cover the ultimate guide to making the best use of architecture and design to guarantee a better, maintainable, and evolutionary solution. You'll also learn how to avoid complex systems and fight against legacy to achieve the desired innovation with stability.

Tactics and Strategies on Software Development: How to Reach a Successful Software

Otavio Santana

En el campo del desarrollo de software, la colaboración es clave. Sin embargo, muchos desarrolladores se encuentran trabajando en equipos sin haber aprendido cómo expresar efectivamente sus opiniones e influir éticamente en sus colegas para alinearse con su visión y metas.En esta sesión práctica e iluminadora, profundizamos en la ciencia de la influencia. Al comprender la psicología detrás de por qué las personas dicen que sí y cómo aplicar estos conocimientos éticamente en los negocios, exploramos los disparadores psicológicos que impulsan el comportamiento humano. Los participantes aprenderán cómo comunicarse consideradamente pero persuasivamente, inspirar la cooperación y fomentar una cultura de colaboración dentro de su equipo.Ya sea que estés liderando un proyecto, buscando el apoyo de los interesados o simplemente buscando mejorar la dinámica del equipo, dominar el arte de la influencia puede llevar a flujos de trabajo más fluidos, una mejor toma de decisiones y, en última instancia, un mayor éxito. Esta sesión compartirá estrategias y técnicas prácticas comprobadas para aprovechar el poder de la influencia y crear un entorno de trabajo más productivo y armonioso.

El Arte de la Influencia: Potenciando la Colaboración en los Equipos de Desarrolladores

The Talk explores the art of influence and collaboration in software development. It emphasizes the importance of effective communication, building relationships, and using social proof to increase influence. The speaker highlights the challenges that arise in cross-functional teams and the need for better collaboration skills. Building connections, fostering trust, and addressing team issues openly are crucial for successful collaboration.

In the field of software development, collaboration is key. Yet, many developers find themselves working in teams without ever being taught how to effectively express their opinions and ethically influence their colleagues to align with their vision and goals.In this practical and enlightening session, we delve into the science of influence. By understanding the psychology of why people say yes and how to apply these insights ethically in business, we explore the psychological triggers that drive human behavior. Participants will learn how to communicate considerately yet persuasively, inspire cooperation, and foster a culture of collaboration within their team.Whether you're leading a project, seeking buy-in from stakeholders, or simply aiming to improve team dynamics, mastering the art of influence can lead to smoother workflows, better decision-making, and ultimately, greater success. This session will share proven practical strategies and techniques for harnessing the power of influence to create a more productive and harmonious work environment.

The Art of Influence: Empowering Developers' Team Collaboration

Lirone Glikman

Recientemente me preguntaron: "Pero Rita, ¿no eres una Desarrolladora de Software? ¿No es tu trabajo escribir código? ¿Por qué sigues reflexionando sobre las personas?" Mi respuesta fue simple: "porque no es responsabilidad de una sola persona construir software de calidad. Se necesita un equipo".El Desarrollo de Software y las Personas no pueden ser vistos como dos preocupaciones separadas por las empresas. Existe una entrelazamiento natural entre ambos que me gustaría explorar un poco en esta sesión.

La Entrelazamiento de Preocupaciones entre las Personas y el Desarrollo de Software

As a software developer, the entanglement between people and the software they develop is important. Legacy software poses challenges due to lack of time, understandability, and optimization. Legacy systems in health care face similar challenges. Microsoft's evolution and innovation highlight the value of change. Developing adaptable and user-friendly software requires considering the interconnectedness of all actors.

Recently I was asked: “but Rita, aren’t you a Software Developer? Isn’t you job to write code? Why do you keep pondering about people?” My answer was simple - “because it is not up to a person to build quality software. It takes a village”. Software Development and People can not be seen as two separate concerns by companies. There is a natural entanglement between the two of them that I would like to explore a bit in this session.

The Entanglement of Concerns between People and Software Development

Rita Castro

En un mundo impulsado por la IA donde la sobrecarga de información es la norma, es demasiado fácil depender de ChatGPT o la búsqueda en Google para obtener respuestas rápidas, solo para olvidarlas rápidamente. Pero ¿qué pasa si hay un enfoque más inteligente que no solo nos ayuda a retener lo que aprendemos, sino que también mejora nuestro flujo de trabajo y productividad? Exploraremos por qué y cómo construir un Segundo Cerebro puede revolucionar la forma en que los desarrolladores trabajan. Al cambiar nuestra perspectiva y confiar en nuestra base de conocimientos interna, podemos forjar conexiones que mejoren la retención de memoria y mejoren nuestro flujo de trabajo en general. Esta presentación tiene como objetivo adentrarse en el núcleo del flujo de trabajo del desarrollador, abordando preguntas comúnmente compartidas que normalmente se buscan en Google o se responden utilizando ChatGPT. En cambio, nos centraremos en cómo adoptar el hábito de recurrir a nuestro Segundo Cerebro puede brindar mejores resultados al proporcionar respuestas en el contexto de nuestro aprendizaje previo.

El Poder de un Segundo Cerebro en el Flujo de Trabajo de un Desarrollador

The Talk emphasizes the importance of maintaining a second brain, a curated collection of digital notes, to enhance memory retention in software engineering. Building a second brain helps in recalling information, problem-solving, and retention. It is easy to create your own second brain using various tool options like Notion, Obsidian, Reflect, Rome Research, and Tana. Starting with small, self-contained notes and gradually expanding to form a mesh of related information is recommended for effective learning and retention.

In an AI-driven world where information overload is the norm, it's all too easy to rely on ChatGPT or Google Search for quick answers, only to forget them just as quickly. But what if there's a smarter approach that not only helps us retain what we learn but also enhances our workflow and productivity? We will explore why and how constructing a Second Brain can revolutionize the way developers work. By shifting our perspective and relying on our internal knowledge base, we can forge connections that enhance memory retention and improve our overall workflow. This presentation aims to delve into the core of the developer workflow, addressing commonly shared questions that are typically googled or answered using ChatGPT. Instead, we will focus on how adopting the habit of turning to our Second Brain can yield better results by providing answers in the context of our previous learning.

The Power of a Second Brain in a Developer's Workflow

Braydon Coyer

WebXR: Realidad Virtual y Realidad Aumentada de forma nativa en navegadores

This Talk introduces WebXR and VR experiments, showcasing examples and encouraging audience engagement. It explores the possibilities of WebXR and AR games, emphasizing the versatility of A-frame for creating AR and VR projects. The Talk also covers asset customization, animations, and augmented reality using LiDAR scanners. It highlights different types of virtual reality experiences and the potential of Apple Vision with WebXR. The speaker emphasizes the importance of community, developer experience, and starting early in WebXR development.

WebXR? Virtual Reality and Augmented Reality Natively on Browsers

Erick Wendel

"El infierno son los demás." Hay muchas charlas sobre cómo comenzar como ingeniero y cómo pasar a la gestión, pero hay pocas charlas sobre cómo ser un adulto en relaciones (profesionales). He pasado mi carrera en pequeñas empresas y startups, organizaciones FAANG y comunidades de código abierto. Cada uno de estos espacios demanda cosas diferentes de las personas en ellos, sin embargo, en todos estos espacios tienen éxito y fracasan a lo largo de las líneas de falla de un conjunto central de habilidades blandas: regular las emociones, establecer límites, enmarcar experiencias de manera productiva y dejar ir. En esta charla, comparto todo lo que he aprendido en mi carrera que ha ayudado a mis colegas, mentorados y amigos para que puedan navegar la parte más difícil de la tecnología, las personas, con gracia, empatía y seguridad.

Gestionándonos, Gestionándonos Mutuamente

The Talk focuses on providing debugging tools for human interactions in software development. It emphasizes the importance of soft skills in programming and suggests strategies such as depersonalization, giving a good apology, understanding power dynamics, emotional regulation, setting boundaries, and rupture and repair. It highlights the need to avoid a self-centered mindset and take responsibility for one's own actions and reactions. The Talk also discusses power dynamics in relationships and the importance of recognizing and navigating them. It emphasizes the significance of setting boundaries, prioritizing, and managing time effectively. Additionally, it addresses the importance of regulating emotions, showing compassion, and repairing ruptured relationships. The Talk concludes by encouraging the embrace of repair and revolutionizing human interactions in the software development field.

“Hell is other people.” There are many talks on how to get started as an engineer and how to step into management, but there are few talks about how to be an adult in (professional) relationships. I’ve spent my career in small companies and startups, FAANG organizations, and opensource communities. Each of these spaces demands different things of the people in them, yet across these spaces all succeed and fail along the fault lines of a core set of soft skills: regulating emotions, setting boundaries, framing experiences productively, and letting go. In this talk, I share everything I’ve learned in my career that has helped my colleagues, mentees, and friends so that you may navigate the most difficult part of tech—people—with grace, empathy, and safety.

Managing Ourselves Managing Each Other

Rachel Nabors

Cualquier persona que haya trabajado en tecnología, por cualquier cantidad de tiempo, sabe que el panorama está en constante movimiento. Las tecnologías de hoy son obsoletas mañana. Las herramientas del oficio están en constante movimiento, y el aprendizaje continuo es el pan y la mantequilla de todos los ingenieros de software que sobreviven a las olas que pasan. Los ingenieros de software del futuro son aquellos que dominaron una habilidad: la adaptación. En esta charla, abordaré la evolución de nuestra artesanía y mis predicciones para las competencias centrales del futuro.

Adaptándose al Futuro del Trabajo en Tecnología

The Talk explores the AI-assisted programming paradigm shift and the evolution of software engineering. It discusses the limitations of large language models (LLMs) and highlights the importance of balancing forces in software engineering. The future of programming is seen as models solving problems based on datasets. The Talk emphasizes the responsibility of creating a better future and the need to strike a balance between utilizing tools and building problem-solving skills. It also touches on the human dependence on AI and recommends resources for further learning.

Anyone who worked in tech, for any amount of time, knows that the landscape is in constant motion. The technologies of today are obsolete tomorrow. The tools of the trade are in constant motion, and continuous upskilling is the bread and butter of all software engineers who survive the passing waves. The software engineers of the future are those who mastered 1 skill: adaptation. In this talk, I will address the evolution of our craft, and my predictions for the core competencies of the future.

Adapting to the Future of Work in Tech

Bassem Dghaidi

La experiencia de ser un Tech Lead puede variar de una organización a otra, desde ser un arquitecto en una torre de marfil hasta quedarse atrapado en los detalles con desafíos técnicos complejos. Una empresa de software Lean es aquella cuyo enfoque está profundamente arraigado en optimizar el valor para el cliente a través del estudio de las técnicas utilizadas en el Sistema de Producción de Toyota.El Agile de la vieja escuela también tiene muchas raíces en los principios Lean: Kanban, por ejemplo, es una herramienta utilizada en la línea de producción de Toyota. Pero, ¿qué nos puede enseñar la fabricación de automóviles sobre el desarrollo de software?Únete a mí en esta exploración a través del mundo de un TL tal como se experimenta en una empresa de software Lean, mientras revelo algunos de los secretos que permiten a estas empresas entregar software de mayor calidad a mayor velocidad.

No es un Tech Lead cualquiera: ¿Qué significa ser TL en una empresa de software Lean?

The Talk discusses the role of a tech lead in a lean software company and the challenges they face. It emphasizes the importance of problem-solving and continuous improvement in software development. The speaker shares their personal struggles as a tech lead and the need to prioritize between being a maker and a manager. The Talk also highlights the significance of identifying root causes and solving problems to prevent future issues. Overall, it provides insights into the role of a tech lead and the role problem solving plays in creating optimal conditions for developers.

The experience of being a Tech Lead can change from organisation to organisation, from being an ivory tower architect to getting stuck in the weeds with complex technical challenges. A Lean Software Company is one whose approach is deeply rooted in optimising customer value through studying the techniques used in Toyota’s Production System.Old-school Agile also has many roots in Lean principles - Kanban, for example, is a tool used on the Toyota production line. But what can the manufacturing of cars teach us about software development?Join me for this exploration through the world of a TL as experienced within a Lean Software Company as I reveal some of the secrets that allow these companies to deliver higher-quality software at speed.

Not Your Everyday Tech Lead: What Does It Mean To Be TL in a Lean Software Company?

James Haworth Wheatman

Probablemente el cambio más notable que experimentan los ingenieros cuando se convierten en líderes es el aumento del caos diario. En el momento en que te haces responsable del trabajo de un equipo o de un área grande, las tareas comienzan a llegar. ¡Docenas de ellas! A veces, por día. Y también, preguntas. ¡De todos y su perro! Y finalmente, reuniones. Muchas de ellas, largas y cortas, emocionantes y aburridas... ¿Te suena familiar? Para mí, sí. Y me llevó bastante tiempo descubrir qué hacer al respecto. Voy a compartir contigo mi receta para domar el caos. Hablaré sobre los componentes de ese caos, las razones por las que ocurren y las soluciones para evitarlo.

Pequeñas cosas que te sumergen en el caos: La forma de salir del caos diario de un líder de ingeniería

The Talk discusses the challenges faced by engineering leaders in their daily work and offers strategies to manage chaos and improve productivity. It emphasizes the importance of organizing, prioritizing, and delegating tasks, as well as maintaining focus and managing overload. Delegation is presented as a way to scale as a leader and promote growth within the team. The Talk also suggests using techniques like the Eisenhower matrix and protecting focus time to enhance productivity.

Probably the most noticeable change engineers experience when they become leaders is the increase of day-to-day chaos. The moment you become responsible for the work of a team or a large area, tasks start coming at you. Dozens of them! Sometimes, per day. And also, questions. From everyone and their dog! And finally, meetings. Lots of them, long and short, exciting and boring... Does it sound familiar? To me, very. And it took me quite some time to figure out what to do with that. I'm going to share my recipe for taming the chaos with you. I'll talk about the components of that chaos, of reasons that they occur, and about solutions for avoiding it.

Tiny Things That Throw You Into Chaos: Engineering Leader’s Way Out of Daily Havoc

Anton Kazakov

¡Los sistemas de diseño son inevitables! Juegan un papel fundamental en el desarrollo web, permitiendo a los equipos lograr consistencia, escalabilidad y eficiencia.Únete a nosotros para una charla perspicaz y entretenida que explora el mundo de los sistemas de diseño y su evolución dentro de las organizaciones tecnológicas. En esta sesión, exploraremos y trataremos de validar un modelo de madurez de sistemas de diseño, ofreciendo orientación práctica en diferentes etapas de crecimiento. Compartiremos lecciones aprendidas y consejos de expertos sobre cómo adaptar tu enfoque para satisfacer tus necesidades. ¿Por qué es importante esto? Implementar y madurar un sistema de diseño puede ser complejo a medida que las organizaciones evolucionan. Al comprender los diferentes niveles de madurez, estarás capacitado para tomar decisiones informadas.

De Nebula a Supernova: Modelos de Madurez del Sistema de Diseño

Design systems are accelerators for development and every web or app developer will come in close contact with them. The design system maturity model simplifies the stages of maturity from Nebula to Supernova. Building a full-fledged design system requires close collaboration between designers and developers, a clear vision and strategy, and strong governance. Continuous improvement and evolution are essential for a mature design system, as well as aligning the design system with business goals and accommodating changes in organizational structure. Documentation and culture compatibility play a crucial role in the success of a design system.

Design systems are inevitable! They play a pivotal role in web development, enabling teams to achieve consistency, scalability, and efficiency.Join us for an insightful and entertaining talk that dives into the world of design systems and their evolution within tech organizations. In this session, we'll explore and try to validate a design systems maturity model, offering practical guidance at different stages of growth. We'll share lessons learned and expert advice on how to adapt your approach to fit your needs. Why does this matter? Implementing and maturing a design system can be complex as organizations evolve. By understanding the different maturity levels, you'll be empowered to make informed decisions.

From Nebula to Supernova: Design System Maturity Models

Joran Quinten

La presentación de Vanessa, Refactorización de mentalidades: Priorizando la salud mental en el desarrollo de software, profundizará en los signos y síntomas comúnmente experimentados dentro de este grupo profesional. La sesión identificará y definirá una variedad de trastornos mentales, ofreciendo una comprensión más clara de estas condiciones. Además, exploraremos diversas estrategias de afrontamiento, equipando a los desarrolladores e ingenieros con las herramientas para gestionar su salud mental de manera más efectiva. Esta presentación tiene como objetivo fomentar una mayor conciencia y proporcionar soluciones prácticas para apoyar el bienestar mental en la industria tecnológica.

Refactorización de mentalidades: Priorizando la salud mental en el desarrollo de software

The Talk discusses the importance of prioritizing mental health in software development, highlighting the increase of mental health issues in the tech industry. It emphasizes the need to address mental health conditions and their impact on productivity. The challenges faced in the tech industry, such as imposter syndrome and burnout, are highlighted, along with strategies to promote well-being and support in the industry. The importance of self-care, seeking support, and managing mental health is emphasized.

Vanessa’s presentation, Refactoring Mindsets: Prioritizing Mental Health in Software Development, will delve into the signs and symptoms commonly experienced within this professional group. The session will identify and define a range of mental disorders, offering a clearer understanding of these conditions. Furthermore, we will explore various coping strategies, equipping Developers &amp; Engineers with the tools to manage their mental health more effectively. This presentation aims to foster a deeper awareness and provide practical solutions to support mental well-being in the Tech Industry.

Refactoring Mindsets:  Prioritizing Mental Health in Software Development

 Vanessa Raath

El rol de un Líder Tecnológico es más sobre liderar que sobre la tecnología. La tecnología es parte de ello, pero las personas son el resto.En mi charla, "El liderazgo tecnológico es más sobre las personas que sobre la tecnología", explicaré por qué las habilidades interpersonales son cruciales en el liderazgo tecnológico. Nos sumergiremos en las habilidades esenciales que todo líder tecnológico necesita: escuchar, empatizar y dar retroalimentación efectiva.Pero más que solo conocer estas habilidades, aprenderás cómo desarrollarlas. Compartiré algunas estrategias prácticas y cotidianas que pueden ayudarte a mejorar tus habilidades interpersonales con el tiempo.Esta sesión es ideal para cualquier persona que aspire no solo a gestionar, sino a liderar verdaderamente enfocándose en el elemento humano en la tecnología.

El liderazgo tecnológico es más sobre las personas que sobre la tecnología

Tech leadership is more about people than tech, as tech problems are usually people problems. Developing soft skills, such as active listening and giving feedback, is crucial for tech leaders to build high-performing teams. To solve people problems, step away from the issue, reflect, and communicate with others. Transitioning to a tech leadership role requires specific education and resources, while choosing between management and specializing involves understanding personal strengths and goals. Maintaining momentum and support requires tracking progress, building a CV, and seeking assistance when needed.

The role of a Tech Lead is more about leading than tech. Tech is a part of it, but people are the rest. In my talk, "Tech Leadership is more about people than tech" I'll explain why people skills are crucial in tech leadership. We'll dive into the essential skills every tech leader needs: listening, empathy, and effective feedback.But more than just knowing these skills, you'll learn how to develop them. I’ll share some practical, day-to-day strategies that can help you improve your people skills over time. This session is ideal for anyone aiming to not only manage but truly lead by focusing on the human element in tech.

Tech Leadership Is More About People Than Tech

Anemari Fiser

Esta sesión explora el arte de la entrevista más allá de las evaluaciones tradicionales, centrándose en el desarrollo de habilidades blandas, la mentoría y el reconocimiento del talento senior. Cubriendo estrategias para construir rapport, evaluar habilidades blandas de manera efectiva y cambiar la dinámica de la entrevista hacia la mentoría, la charla enfatiza la importancia de cultivar un entorno de apoyo para los candidatos. Además, se adentra en la identificación de rasgos de senioridad más allá de la experiencia técnica, promoviendo la diversidad y la mejora continua a través de la retroalimentación. Los participantes obtendrán ideas para transformar las entrevistas en compromisos significativos que encuentren talento y posibles futuros líderes.

El Arte de Entrevistar Personas o Cómo Identificar el Talento Senior

In interviewing senior talent, it's important to find the intersection between the candidate's knowledge and the company's requirements. Traditional assessments have shifted focus from technical skills to soft skills. Problem-solving approach, ownership, independence, and emotional intelligence are key traits to assess in senior candidates. Evaluating mindset, career stage, and judgment based on feelings can provide insights into a candidate's characteristics and progression.

This session explores the art of interviewing beyond traditional assessments, focusing on cultivating soft skills, mentorship, and recognizing senior talent. Covering strategies to build rapport, assess soft skills effectively, and shift the interview dynamic towards mentorship, the talk emphasizes the importance of cultivating a supportive environment for candidates. Additionally, it delves into identifying seniority traits beyond technical expertise, promoting diversity, and continuous improvement through feedback. Participants will gain insights to transform interviews into meaningful engagements that find talent and potential future leaders.

The Art of Interviewing People or How to Identify Senior Talent

Krasimir Tsonev

Todos tenemos nuestro propio procesador de bienestar.Influye en cómo te sientes y actúas. Conduce a todos los resultados que has tenido o tendrás...Para la mayoría de nosotros, nuestro procesador de bienestar se alimenta principalmente de nuestra propia IA.Desafortunadamente, nuestra IA a menudo parece trabajar en contra nuestra.En esta charla, aprenderás cómo recuperar el control y entrenar a tu IA para que trabaje contigo y promueva una mentalidad de crecimiento y optimice el bienestar.

Mentalidad: Tú vs. Tu IA

This Talk explores the role of mindset in software development and the use of AI assistants. It emphasizes the importance of training the AI assistant and the potential impact of outdated beliefs. The conscious mind is discussed as the gatekeeper to thoughts and feelings, influencing our actions and results. Mindful media consumption and prioritizing mental health are also highlighted, along with the need to support team well-being. The Talk concludes with the significance of fitness in supporting mental health.

We all have our very own wellbeing processor.It influences how you feel and act. It leads to every outcome you’ve ever had or will have…For most of us, our wellbeing processor is primarily fed by our very own AI.Unfortunately, our AI often seems to work against us.In this talk, you’ll learn how to take back control and train your AI to work with you to promotes a growth mindset and optimise wellbeing.

Mindset: You vs Your AI

Richard Donovan

Potenciando el Asistente de Código Cody utilizando LLMs

This Talk explores the world of coding assistants powered by language models (LLMs) and their use cases in software development. It delves into challenges such as understanding big code and developing models for context in LLMs. The importance of ranking and code context is discussed, along with the use of weak supervision signals and fine-tuning models for code completion. The Talk also touches on the evaluation of models and the future trends in code AI, including automation and the role of tasks, programming languages, and code context.

Powering Cody Coding Assistant Using LLMs

Rishabh Mehrotra

La economía es terrible, los despidos están en todas partes y las entrevistas son difíciles. La búsqueda de empleo es agotadora y estresante, ¿entonces cómo superarlo? ¡Todo lo que necesitas es un plan! Ya sea superando los nervios o aprendiendo a comunicar tu experiencia técnica de manera más efectiva, todos tenemos nuestras dificultades. ¡Lo que no puedes hacer es dejar que te detengan! En esta charla, aprende cómo aprovechar las tres C (Conexiones, Comunicación y Confianza) para obtener una ventaja competitiva durante tus entrevistas. Al adoptar esta estrategia, estarás preparado para arrasar en tu próxima entrevista y obtener esa oferta.

Maximizando tu Potencial en Entrevistas de Tecnología: Las Tres Cs para el Éxito

Tech interviews are becoming more competitive due to increasing layoffs in the tech industry. Building connections and having referrals are crucial in securing job opportunities. Building your brand and online presence can lead to job opportunities without traditional interviews. Sharing your expertise through content creation and networking can help build connections and raise awareness. Confidence, effective communication, and showcasing soft skills are key to succeeding in technical interviews.

The economy is terrible, layoffs are everywhere, and interviewing is hard. Job searching is exhausting and stressful, so how do you overcome all of that? All you need is a plan! Whether it’s overcoming nerves or learning to communicate your technical experience more effectively, we all have our struggles. What you can’t do is let them hold you back! In this talk, learn how to leverage the three C’s (Connections, Communication, and Confidence) to gain a competitive advantage during your interviews. By embracing this strategy, you’ll be prepared to crush your next interview and get that offer!

Maximizing Your Potential in Tech Interviews: The Three Cs to Success

James Q Quick

Únete a mí en "Pixels, Promesas y Pánico" mientras nos adentramos en el mundo de los contratiempos en el frontend. Compartiremos 4-5 historias de terror reales desde las trincheras del desarrollo web. Desde desconcertantes errores del navegador hasta catastróficos desastres de código, estas historias son una mezcla de humor y precaución. Ya seas un desarrollador experimentado o recién estés comenzando, estas historias te entretendrán, iluminarán y nos recordarán a todos los giros inesperados en el mundo de la codificación.

Pixels, Promesas y Pánico: Historias de Pesadillas en Producción

The Talk covers the importance of preventing and dealing with bugs in software development, with the speaker sharing their experiences and solutions. They discuss the impact of bugs on user experience and revenue, the importance of stress testing and implementing alerts, and the surprising impact of CSS. The speaker also emphasizes the importance of simplicity, monitoring, and refactoring, as well as the need to address security threats and learn from failure. They provide tips for writing postmortems and highlight common mistakes to avoid, especially for junior developers.

Join me for "Pixels, Promises, and Panic" as we delve into the world of frontend mishaps. We'll share 4-5 real-life horror stories from the trenches of web development. From baffling browser bugs to cringe-worthy code catastrophes, these tales are a mix of humor and caution. Whether you're a seasoned developer or just starting out, these stories will entertain, enlighten, and remind us all of the unexpected twists and turns in the world of coding.

Pixels, Promises, and Panic: Horror Stories of Production Nightmares

Neciu Dan

Después de años de crecimiento rápido, los vientos han cambiado en muchas empresas tecnológicas, con cambios de estrategia, recortes de presupuesto, reestructuraciones y despidos. La productividad y la eficiencia se han convertido en las palabras de moda de la temporada, y aunque la presión hacia "más productividad en ingeniería" está aumentando en muchas organizaciones, puede ser difícil aplicar estos conceptos abstractos a los equipos de ingeniería y convertirlos en acciones concretas que no alienen a tu equipo y que tengan un impacto duradero que se alinee con las necesidades de tus partes interesadas.Estoy aquí para ayudarte. En esta charla, iremos:- Más allá de las palabras de moda: ¿Qué significan productividad, eficiencia y efectividad?- Más allá de "implementar métricas DORA": ¿Cómo puedes entender y mejorar la productividad de tu equipo como líder técnico o de personas?- Más allá de tu equipo: ¿Cómo puedes gestionar eficazmente hacia arriba para mantener informados a tus jefes y garantizar la alineación con los objetivos organizativos?Habiendo liderado docenas de equipos en momentos de gran cambio, sé que liderar durante una recesión tecnológica presenta desafíos únicos. Obtendrás pasos concretos para ayudarte a mejorar en tu equipo y liderar con éxito en tiempos inciertos.

De Palabras de Moda en los Negocios a un Cambio Significativo: Medir y Mejorar la Productividad en Ingeniería

This Talk focuses on the importance of productivity, efficiency, and effectiveness in software development. It highlights the evolving role of leadership, the need for clarity in understanding these terms, and the significance of metrics in driving behaviors and outcomes. The Talk emphasizes the value of aligning with business goals, involving teams in defining productivity measures, and continuously improving productivity to achieve goals.

After years of rapid growth, the winds have changed in many tech companies, with strategy changes, budget cuts, restructurings, and layoffs. Productivity and efficiency have become the business buzzwords of the season, and while pressure towards “more engineering productivity” is mounting in many organizations, it can be difficult to apply these abstract concepts to engineering teams and turn them into concrete actions that don’t alienate your team and lead to lasting impact that aligns with your stakeholders’ needs. I’m here to help. In this talk, we’ll go: - Beyond buzzwords: What do productivity, efficiency, and effectiveness mean? - Beyond “implementing DORA metrics”: How can you understand and improve your team's productivity as a technical or people leader?- Beyond your team: How can you manage up effectively to keep your bosses informed and ensure alignment with organizational goals?Having led dozens of teams through times of high change, I know that leading during a tech downturn presents unique challenges. You will take away actionable steps to help you improve on your team, and lead successfully through uncertain times.

From Business Buzzwords to Meaningful Change: Measuring and Improving Engineering Productivity

Lena Reinhard

Estás trabajando como desarrollador, y un día - BAM, te ofrecen la oportunidad de liderar un equipo, de ocupar un puesto gerencial o de liderazgo.¿Y ahora qué? ¿Si acepto la oferta, olvidaré cómo programar? ¿Mis habilidades se depreciarán? ¿Hay un camino de regreso hacia una trayectoria especializada? ¿Realmente puedo ser un 'gerente de día, desarrollador de noche'? ¿Seguiré siendo una persona técnica?¡He estado en este punto! En Atlassian, realicé un experimento y pasé de un puesto de desarrollador senior a un rol de gerente durante 15 meses... y luego volví a la codificación.¿Ayudará mi experiencia a tomar una decisión si te encuentras en una situación similar? No lo sé. Pero será algo para reflexionar.

De Desarrollador Senior a Gerente y Viceversa: El Viaje de Regresar a la Codificación

Transitioning from being a software developer to a manager can be challenging, but offers the opportunity to have a greater impact on the organization. However, some people may miss the hands-on aspect of coding and choose to return to development. The transition may involve changes in company size, hierarchy, and product focus. Soft starts and gaining new skills and perspectives are helpful in navigating the challenges of being a manager. Feedback and further discussions are encouraged, along with sharing presentation materials.

You're working as a developer, and one day - BAM, you're offered the chance to lead a team, to step into a managerial or leadership position.What now? If I accept the offer, will I forget how to code? Will my skills depreciate? Is there a way back to a specialist path? Can I really be a “manager by day, developer by night”? Will I still be a technical person?I've been at this point! At Atlassian, I undertook an experiment and moved from a senior developer position to a manager role for 15 months... and then I went back to coding.Will my experience help you make a decision if you're facing one - I don’t know. But it will be food for thought

From Senior Developer to Manager and Back: The Journey of Returning to Coding

Michał Michalczuk

Construir un negocio es una pelea para ver quién consigue más clientes primero. Tienes que adoptar esa mentalidad al escribir código. Como me dijo una vez un antiguo jefe: El código limpio no importará si estamos muertos. Tienes que cambiar tu mentalidad de las mejores prácticas a hacer las cosas. Pero no puedes volverte demasiado loco o la deuda técnica te matará.

Escalando Rápido: Lecciones de Ingeniería de ~15 Años de Startups Tecnológicas

Tech startups require scaling the business, the team, and the tech. The goal of an engineering team at a startup is to not be the reason for the business to slow down. Engineers prioritize business outcomes over code debates. Simplify your code and prioritize solving the specific problem. Organize your code vertically to limit complexity and improve clarity. To avoid code problems in the future, focus on getting the data and architecture right rather than striving for perfection today. Balancing dry and duplicating code can be achieved by allowing patterns to develop and observing for common solutions.

Building a business is a slugfest to see who gets more customers first. You have to adopt that mindset when writing code. As an old boss told me once: Clean code won't matter if we're dead. You have to shift your mindset from best practices to getting shit done. But you can't go too wild or the tech debt will kill ya.

Scaling Fast – Engineering Lessons From ~15 Years of Tech Startups

Swizec Teller

Ningún desarrollador es una isla y ningún desarrollador es perfecto. Esto significa que no puedes crear nada sin usar componentes escritos por otra persona y estos componentes tendrán defectos o características faltantes. En algún momento de nuestra vida, todos hemos pedido apoyo a alguien más.Pero ser un mantenedor no es una tarea fácil en absoluto. Piensa en recibir toneladas de informes con información parcial o faltante, o ser gritado por extraños por no ser lo suficientemente receptivo o rápido.Para la salud de nuestra industria, debemos amar más a nuestros mantenedores: en esta charla mostraré cómo pedir ayuda de manera educada y cómo asegurarte de proporcionar toda la información necesaria.

Ama a tus Mantenedores

Open source is a decentralized software development model driven by passion, improving software quality. Kindness is crucial in the open source community to prevent burnout and maintain healthy dynamics. When asking for help, do thorough research and communicate effectively. Reporting issues should be detailed and provide relevant information. Follow-up and engagement are important in finding solutions and expressing gratitude to maintainers.

No developer is an island and no developer is perfect. This means that you cannot create anything without using components written by someone else and these components will have defects or missing features. At some point in our life we all asked for support to someone else.But being a maintainer is not an easy task at all. Think about receiving tons of reports with partial or missing information, or being yelled by strangers for not being responsive or fast enough.For the health of our industry we must love our maintainers more: in this talk I’ll show how to politely ask for help and how to make sure you provide all the necessary informations.

Love Your Maintainers

Paolo Insogna

En entornos de alto rendimiento, el ritmo es implacable. Si bien es fácil tomar decisiones técnicas rápidas en equipos de desarrollo más pequeños, la dinámica cambia drásticamente al tratar con un equipo de 100 desarrolladores. Tomar decisiones técnicas significativas, especialmente aquellas relacionadas con la arquitectura, sin afectar a otros equipos se vuelve casi imposible.En esta charla, compartiré mi experiencia en la estructuración de un proceso de RFCs en QuintoAndar. Nos adentraremos en los RFCs, descubriendo por qué son una herramienta indispensable para las empresas que buscan mantener la excelencia técnica, incluso con una fuerza laboral considerable. Exploraremos cómo los RFCs facilitan la toma de decisiones técnicas de alto nivel, proporcionando una hoja de ruta clara para los cambios y empoderando a todos para navegar los riesgos con precisión.

De la Confusión a la Claridad: Aprovechando los RFCs en Entornos de Alto Rendimiento

The AmazingRFCs initiative was created to improve deliveries and collaboration at Quintana Roo. Two key actions were forming the RFCs Advisors group and optimizing the design and review process. By including interested and key people in discussions and implementing daily training initiatives, the density of capable decision makers increased, resulting in more high-quality RFCs and improved solutions in production.

In high-performance environments, the pace is relentless. While it's easy to make quick technical decisions in smaller developer teams, the dynamics shift drastically when dealing with a team of 100 developers. Making significant technical decisions, especially those concerning architecture, without impacting other teams becomes nearly impossible.In this talk, I'll share my experience of structuring an RFCs process at QuintoAndar. We'll delve deep into RFCs, uncovering why they're an indispensable tool for companies aiming to maintain technical excellence, even with a sizable workforce. We'll explore how RFCs facilitate high-level technical decision-making, providing a clear roadmap for changes and empowering everyone to navigate risks with precision.

From Chaos to Clarity: Leveraging RFCs in High-Performance Environments

Mateus Paulino

Todos hemos tenido un gerente que parece no escuchar ni una palabra de lo que decimos, y si no lo hemos tenido, probablemente seamos esa persona. He estado en ambos extremos, pero encontré una salida del ciclo vicioso. La respuesta es la escucha activa.Como líderes, tenemos mucha influencia y poder para hacer cambios. Debemos a nuestro equipo la responsabilidad de cuidar a los miembros del equipo, ayudarlos a crecer y apoyarlos en momentos difíciles, y no podemos hacer esto de manera efectiva si no sabemos cómo escuchar activamente.¿Por qué alguien nos escucharía si nosotros no los escuchamos a ellos?La escucha activa es una habilidad de comunicación que va más allá de simplemente escuchar las palabras que otra persona dice, para tratar de comprender el significado y la intención detrás de ellas.Escuchar construye confianza, crea una comprensión compartida y pone a las personas del mismo lado para trabajar hacia una solución.Explora conmigo el significado de la escucha activa, cómo puede ayudarnos a ser líderes más efectivos y empáticos, y cómo practicarla.

Escucha Mejor, Lidera Mejor

Active listening is crucial for effective leadership, as it fosters trust, empathy, and meaningful relationships. The BREW framework, which emphasizes being present, reflecting, encouraging, and withholding judgment, can help develop active listening skills. By actively listening, we can understand unspoken words, create a safe environment for expression, and improve relationships. Practicing active listening leads to more fulfilling relationships and effective leadership.

We all had a manager who doesn’t seem to listen to a single word we say, and if we don’t, it’s probably because we are that person. I’ve been on both ends, but I found a way out of the vicious cycle. The answer is active listening.As leaders, we have a lot of influence and power to make changes. We owe the team the responsibility of taking care of the team members, helping them grow, and supporting them in tough times, and we cannot do this effectively if we don’t know how to actively listen. Why would someone listen to us if we don’t listen to them?Active listening is a communication skill that involves going beyond simply hearing the words that another person speaks, to seek to understand the meaning and intent behind them. Listening builds trust, builds shared understanding, and puts the people on the same side to work toward a solution.Explore with me the meaning of active listening, how it can help us be more effective and empathetic leaders, and how to practice it.

Listen Better, Lead Better

Lean Vilas

In this presentation, we explore the role of playfulness and hobbies in preventing burnout in the tech industry. Discover how integrating joy and creativity into our work routines can enhance innovation and well-being. Join us for insights and strategies to embrace a more balanced and fulfilling approach to technology work.

Rebooting Joy: Harnessing Playfulness and Hobbies to Redefine Work in the Tech World

Johnny Fekete

Hay mucha información disponible sobre cómo reducir la carga cognitiva para los usuarios, pero ¿qué pasa con los desarrolladores? Esta charla abordará la Teoría de la Carga Cognitiva, cómo algunas discapacidades la afectan y cómo diseñar un entorno de desarrollo en torno a ella.

Carga Cognitiva y tu Entorno de Desarrollo

Cognitive load is the thinking load that can lead to cognitive overload. Disabilities can increase cognitive load, and reframing tasks can reduce it. Information presentation affects cognitive load, with intrinsic, extraneous, and germane cognitive load. Focus and context switching should be managed to optimize workflow and reduce cognitive load. Opening a PR can be simplified with task automation, and optimizing workflow involves reducing distractions and utilizing tools. Prioritizing personal coding skills and reducing cognitive load are key to success.

There's lots of information out there about reducing cognitive load for users, but what about developers? This talk will cover Cognitive Load Theory, how some disabilities affect it, and designing a development environment around it.

Cognitive Load and Your Development Environment

Abbey Perini

Aprende cómo crear y compartir contenido profesional de desarrollo web para ampliar tu alcance, avanzar en tu carrera y establecer tu estatus de experto. Esta charla te enseñará cómo compartir tu conocimiento de manera efectiva a través de blogs, videos y publicaciones en redes sociales, ayudándote a destacar y conectarte con otros.

Creación de Contenido para Desarrolladores

Today's Talk discusses the importance of technical content creation for developers, including the benefits of becoming a technical content creator and the personal growth it offers. It emphasizes the value of sharing knowledge and experiences through articles, videos, and open source projects to gain recognition and respect from the community. The Talk also provides tips for creating engaging technical content, sharing it across social platforms, and staying connected with the developer community.

Learn how to create and share professional web development content to expand your reach, advance your careers and establish expert status. This talk will tech you how to share your knowledge effectively through blogs, videos, and social media posts, helping you stand out and connect with others.

C3 Dev Festival 2024

The contemporary software engineering and design festival