Name: TechLead Conference 2024
Start: 2024-06-15T07:00:00.000Z
End: 2024-06-19T18:00:00.000Z

As it is with many developers, his path to coding was not straightforward. And looking at Shawn's bio, it's apparent he applied that experience to his whole career: he's the head of developer experience at Temporal.io, author of a bestselling book on progressing career in IT, and a sought-after mentor and speaker. His number one advice? “Marketing is not beneath you.” What led you to software engineering?My first career was in finance, and I did a lot of trading of currency derivatives and stock portfolios. We had to do a lot of number crunching in Excel, Python, and then Haskell. I was the guy putting together all that data. I didn't call myself an engineer, but I was writing software. I saw that there are many good ideas in software engineering that I should learn and that once I do that, my life will be significantly better. So I left finance and went through a boot camp to learn all the software engineering practices. My first job was at two Sigma as a front-end engineer. Then I joined Netlify as a developer engineer and then AWS. What is the most impactful thing you ever did to boost your career?This will sound very similar to Ken's thing, and it's called learning in public. I did it when I was at Sigma because I wasn't learning much at work. I was in New York City, there were many meetups, and I decided to give myself my own mentors speaking there, writing blog posts, sharing them, and just finding more ways to grow apart from inside of my company. And I realized that it was way more effective than just waiting for the right boss or co-worker to teach me.Also, the dev community has been so welcoming and supportive. You learn, share what you've learned, and people will correct you if you're wrong. And once you're wrong, you will never forget what you have been learning. So if you have a pretty thick skin and a low ego, you can learn a lot. In fact, with my most recent job, I wrote a blog post about what I thought was missing in the serverless ecosystem based on what I had seen at AWS and Netlify. Someone commented on my blog, a VC read the comments and hired that guy to head the products at Temporal. And then that guy turned around and hired me based on that blog post. For me, learning in public has opened up jobs and speaking opportunities on multiple continents. And I've made a lot of friends who are genuinely interested in technology.What would be your three tips for engineers to level up their career? Understand that some marketing is unavoidable and that knowing how to market yourself authentically is not scammy. It's not beneath you. It's what you need to do to get people to know you, your skills, and the quality of your work. A lot of developers have a build-it-and-they-will-come mentality, and it does not serve them very well. Invest some time into developing your marketing and understanding how to market yourself. I have a blog called How to market yourself without being a celebrity. When people look at marketing, they see the celebrity path, the influencer path. But many people don't want to be an influencer, so they'll say: "No marketing for me!" Let's disconnect those two things. Also, there's a difference between marketing yourself internally within your company — which you should always do — and marketing yourself externally with other developers.My second tip is to clone open-source apps. Clone something that already exists so that you stop making all these little product decisions. Maybe your implementation will be better, which is great; that's how the industry improves. And if it's worse, you start to understand the underlying trade-offs of your project. And a third one?Many people have the cold start problem when it comes to networking and content creation. Yes, you will not get much response when you start. So the way to guarantee response is what I call a "pick up what they put down" approach. If you want feedback, start giving feedback, mainly whenever people put out something new.When somebody you respect publishes a new demo, a new library, a new blog post, or a new workshop, summarize it, respond to it, react to it. Not with a YouTube reaction video, but actually respond to the meat of the content. Ask questions: Do you agree? Do you disagree? What else can you do with this implementation? Pick up on the things. Find bugs in the demos and the libraries, and you're guaranteed to get a response from that.I think that's an excellent starting point because these people are already influential. Almost definition, they have more ideas, and they know what they do. You work with them, become a collaborator. Eventually, you start to disagree with them, and you feel forced off into your own path. That's, I think, a great way to get started. You are now working on developer experience at <a href="https://temporal.io">Temporal.io</a>. What does it entail?Temporal is an open-source microservices orchestration system, which you could compare to Apache Airflow or AWS Step Functions. But we're better. There's a core server that is open source, and then there's all this stuff around it that needs to reach developers: documentation, developer relations, web UI, and SDKs. And I'm the head of developer experience helping each team in those areas. They are not essential to the server itself but important to how developers experience the product. I have overarching excitement in my career about helping technologies cross the chasm. I'm not sure who came up with the term, but the idea is that when you switch over from early adopters to a broad audience, there is a big gap in the middle where you have to fill in a lot of gaps with developer experience. That's what I focus on. Do you have some rituals or tools that keep you focused and goal-oriented?I try to do time blocking. For example, interview calls are on Fridays, which gives me focus on work from Mondays to Thursdays. Within the day, you have different time blocks as well. And if you can block off time for yourself too, I think you can get a lot more done.Apart from your daily job, you are a writer and speaker, and you recently published The Coding Career Handbook. What inspired you to write it?Mostly the feedback from my essay on learning in public. It was the most impactful piece of writing I've ever done; it reached over a million people. I can write about technical stuff, and I think it would be easier to sell, but React will be over someday. The thing that will not be over is career stuff, the evergreen things. When I decided to write the book, I had some time between my Netlify job and my Amazon job. So I wrote a poll, and the one with the more enthusiastic response was the career stuff. For whatever reason, this is the most valuable topic to my readers. Also, I think there's a gap in the market for leveling juniors and seniors. You can find many materials on how to learn to code and crack the coding interview. And then there's a big gap. But many people are coming into tech as juniors, and there's a lot of companies wanting to hire seniors — and nobody focuses on developing juniors into seniors.So I'm trying to contribute my thoughts as well as the thoughts of others. I collected 1,500 references to other people's ideas on becoming a senior engineer in the book. And I think if I keep at this — this is version one — I will build it up into the ultimate resource on how to become a senior engineer. And if you were to highlight one idea from your book, which one would it be?I'd say the most underappreciated part of my book is the strategy section — the importance of picking the right thing to work on rather than just being a clean coder or choosing the right tech stack. Understanding how money is made from your software is key to selecting the right company and positioning yourself correctly within the company. You are also very active in the community: you've contributed to several other books, have a <a href="https://twitter.com/swyx">34k+ following on Twitter</a>, helped to run the React subreddit... How has it impacted your career?It helps you to know everybody. It allows you to understand what's going on. I'm typically the source of news to my team, and they appreciate that. Also, if you're friends with everybody, you don't have to know everything — it's all coming from that community. What open-source projects would you recommend keeping an eye on or contributing to?I left the React community because I was getting more and more interested in Svelte. I do think it is an underrated framework for front-end developers. It's not for everybody, but I think it solves a good set of problems, including state management, styling, and animation. At React, we still don't have good answers for these things after all these years.What pieces of your work are you most proud of?Mostly the community behind the coding career handbook. I set up a semi-private Discord channel for people who opt into the community, and seeing people get jobs, double their pay when they go from junior to senior — that's really exciting. It's a great place for discussion where you can be totally honest. Realizing that that's something that I can do for ten years and not get bored of it, that's something I'm proud of. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Shawn Swyx Wang's career tips: Knowing how to market yourself is not scammy

Shawn Swyx Wang

Jan Tomes

Speakers are not made — they are born out of circumstances. And Tomasz is a perfect example of a self-starter who rose to the occasion. “I started at local meetups and climbed my way up to bigger and bigger events,” he says, nodding at the fact that he's now also a seasoned instructor revolutionizing modern commerce. How did he get there? What led you to software engineering?It's been quite a journey. Ever since I was a kid, I was interested in technology, but I was definitely not one of those five-year-old prodigies that installed Arch Linux on their fridge. I wrote my first program on a Commodore 64 copying an entire page of arcane characters from a book to a computer and hitting Enter. And then I watched the screen flash in different colors.I built — okay, copied and pasted random code till it worked, which I kind of do till this day — my first website when I was around 12, but I never thought that web development would turn out to be my career. In fact, I explicitly did not decide to pursue a Computer Science degree for various reasons. I felt I wasn't good enough and thought that programming was not for me.Instead, I decided to pursue a master's degree in Electronics and Telecommunications, which, to my surprise, was most likely harder than the CS curriculum. Along the way, I got an opportunity to learn C++, which wasn't exactly a cakewalk, but it led me to my first internship, which led to another one where I was a part of an eight-week-long paid bootcamp. There I learned web development from scratch, an opportunity I'm forever grateful for. And I've been programming for a living ever since.What is the most impactful thing you ever did to boost your career? It was back in 2017 when I decided to give public speaking a shot. Like all tech speakers, I started at local meetups and slowly but surely climbed my way up to bigger and bigger events.Contrary to a popular notion, speaking at tech conferences is not exactly something you do for money. The connections, networking, and genuine friendships that happened because of all those events are priceless, though. The doors you get to open, the places you get to see, the people you get to meet — if you're able to, I cannot recommend speaking at tech events enough. What would be your three tips for engineers to level up their career? I wrote everything I wished I knew earlier in this blog post. In short: talk to humans rather than machines, have a deep understanding of what you are building and why, and don't be afraid to say, "I don't know." Also, learn in public, as some of my colleagues mentioned in their interviews.What are you working on right now? I'm currently a front-end engineer at <a href="https://www.stedi.com">Stedi</a>, where we're building a fully serverless platform for companies to integrate and exchange business transactions with each other. Stedi is a fully remote startup with employees from all around the globe, and I'm a part of a ridiculously talented team of engineers who happen to be from the same city I'm from!The business domain we're in hasn't seen much innovation in decades, and it's such an exciting space to contribute to. We're working on challenging and complex problems. After all, revolutionizing modern commerce can't be easy. Do you have some rituals that keep you focused and goal-oriented? I'm not sure if this is a ritual, but I strive to challenge myself as often as I can and pursue new personal and professional growth areas. My favorite answer to the famous "Where do you see yourself in five years?" question is, "I don't know." I feel like if you do know where you'll end up in five years, you may not be thinking broadly enough about your potential and possibilities. In this line of work, it's crucial to be focused on growth and becoming a lifelong learner.You're an egghead.io instructor, where you've contributed with two courses and more than 170 lessons. What do you find rewarding about the experience?Joining egghead was life-changing for me. Apart from the financial incentive, having the ability to record a lesson or a course in my bedroom and teach something useful to hundreds, if not thousands of developers, is remarkable. I'm forever grateful to Joel and the entire egghead crew for having me. If you're interested, you can read a bit more about my journey with them in the post.What would you say are essential qualities and skills for teaching — and learning?Keep your eyes open as there's always more to learn. Try to learn something new every week, if not every day. When teaching, optimize for boredom. It's better to explain something again to an expert rather than to a beginner who may feel excluded.Also, when one teaches, two learn, so use teaching as a tool of solidifying your own knowledge.And don't forget to be kind. Whenever you teach someone a concept that may seem totally obvious to you because you mastered it years ago, make sure to remember that you were a beginner not so long ago too.What open-source projects would you recommend keeping an eye on or contributing to?I'm a huge fan of everything Tanner Linsley is working on, especially React Query. In my humble opinion, it's the best library since jQuery, so make sure to check it out. It's just excellent.What pieces of your work are you most proud of? Whenever someone reaches out to me saying that a video, article, podcast, or talk I created helped them, it always means the world to me. It's an incredible feeling to have something you wrote a couple of months ago reach out to someone else from across the globe and help them grow as a developer.<a href="https://www.froala.com/wysiwyg-editor?pb=1"></a>

Career tips by Tomasz Łakomy: I strive to challenge myself as often as I can

Tomasz Łakomy

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 elijas 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

The Talk discusses the challenges of work recognition in the software development field and provides practical tools to get your work noticed. It emphasizes the importance of setting specific goals and communicating them with your manager. The concept of a 'brag bank' is introduced as a way to store positive feedback and achievements. The Talk also explores the idea of job hopping and when it may be beneficial or detrimental to your career. It concludes by encouraging positive thinking, creating a career plan, and being kind to oneself.

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

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: escucha, empatía y 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, centrá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, with a focus on understanding and working with people. Developing soft skills is essential for tech leaders, as most tech problems are people problems. Continuous growth requires celebration, reflection, and learning from mistakes. Listening is a key soft skill that impacts other skills, and resolving conflicts requires reflection and open communication. Building trust and openness in offshore teams involves creating a feedback culture and understanding the remote environment. Taking initiative, understanding strengths, and finding support are important for career growth. Overcoming challenges, sustaining momentum, and taking time off for improvement are crucial. Books and resources on leadership are available on LinkedIn.

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

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 growth is a Red Queen's race. Scale the business, team, and tech. Beware of the S-curve. Business growth fuels promotions and engineering challenges. Engineering teams get involved early in the process to develop the best solution.

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

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, promoviendo una mentalidad de crecimiento y optimizando el bienestar.

Mentalidad: Tú vs. Tu IA

The Talk discusses the mindset and operation of AI assistants, the influence of thoughts on our experience, the impact of subconscious thoughts on well-being, and strategies for improving mental health both individually and in a team setting. It emphasizes the importance of mindful consumption, self-care, and fitness for maintaining good 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

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

This talk explores interviewing in the age of AI, discussing the history of interviewing for software engineering and the skills needed for future interviews. It examines the challenges and frustrations of the current interview process, the role of AI in interviews, and the integration of AI in the development process. The shift in interview focus towards collaboration skills and intuition is highlighted, as well as the importance of adapting to the changing landscape and navigating junior interviews with AI. Effective interview strategies with AI are also discussed.

Conducting Interviews and Interviewing in the Age of AI Tools

 Lindsey Simon

En un mundo impulsado por la IA donde la sobrecarga de información es la norma, es muy fácil depender de ChatGPT o Google Search para obtener respuestas rápidas, solo para olvidarlas igual de rápido. Pero ¿qué pasaría si hubiera un enfoque más inteligente que no solo nos ayude a retener lo que aprendemos, sino que también mejore 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 la 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 dar 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 concept of a second brain, a curated list of digital notes, helps enhance memory retention. Building and maintaining a second brain as a developer is beneficial for contextual discovery and quick information recall. Any tool can be used to create a second brain, starting with self-contained information and gradually forming a web of related content. Active learning through a second brain is enduring and helps retain information that cannot be physically recalled.

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

Cualquiera 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 1 habilidad: la adaptación. En esta charla, abordaré la evolución de nuestra disciplina y mis predicciones para las competencias clave del futuro.

Adaptándose al Futuro del Trabajo en Tecnología

The Talk explores the history and evolution of software engineering, highlighting key figures and concepts that have shaped the field. It emphasizes the importance of understanding AI-assisted programming and how it can be used effectively. The future of programming is envisioned as models writing code based on defined behaviors, with a gradual shift towards solving human problems. The impact of AI on coding raises concerns about dependence and the need for responsible consumption. Guardrails, awareness, and customization are crucial in technology consumption.

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

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

The Talk explores the entanglement of concerns between people and the software they develop, emphasizing the importance of considering people and teams instead of just coding. It highlights the time constraints faced by developers and the potential for code optimization to improve understandability and usefulness. The Talk also discusses the significance of revamping outdated software and embracing continuous improvement in software development. It concludes by emphasizing the interconnectedness of software builders, thinkers, users, maintainers, and payers, and encourages the development of user-friendly software systems that adapt to change and consider the needs of all stakeholders.

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

"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 las 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 exige 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 puedas navegar la parte más difícil de la tecnología, las personas, con gracia, empatía y seguridad.

Gestionándonos, Gestionando a los Demás

The Talk discusses the challenges of dealing with people in software development and engineering. It offers debugging tools for human interactions, emphasizes taking ownership of one's actions and reactions, and recognizing power dynamics. The importance of setting boundaries for work-life balance and privacy at work is highlighted. Strategies for managing emotions and dysregulation are provided, along with techniques for repairing relationship ruptures. The Talk concludes by emphasizing the importance of relationship debugging tools and continuous personal growth.

“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

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 común: ¿Qué significa ser TL en una empresa de software Lean?

The Talk discusses the role of a tech lead in a lean software company. It highlights the importance of understanding the distinction between a senior developer and a tech lead. The speaker shares their experience of focusing on immediate issues rather than addressing root causes, leading to burnout. The Talk emphasizes the mentor model of management and the shift in perspective it brings. It also explores the principles of lean and problem-solving techniques in a lean company. The role of a tech lead is to implement solutions, standardize processes, and create 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 de 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 lanzan al caos: La forma en que los líderes de ingeniería salen del caos diario

This Talk discusses the challenges faced by engineering leaders and provides strategies to overcome them. It emphasizes the importance of organizing, prioritizing, delegating, and maintaining focus. Techniques such as email organization, task prioritization using the Eisenhower matrix, and delegation to scale work are highlighted. The Talk also emphasizes the need to protect and schedule focus time to avoid overload and fragmentation. Overall, the Talk provides practical advice for engineering leaders to navigate the chaos and 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

La presentación de Vanessa, Refactorizando 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 serie 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 necesarias 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.

Refactorizando Mentalidades: Priorizando la Salud Mental en el Desarrollo de Software

Today's Talk focuses on the importance of mental health in software development and engineering. The pandemic has highlighted the need to raise awareness and address mental health issues in the tech industry, which has seen a significant impact on productivity and well-being. Common mental health issues in the industry include anxiety, depression, burnout, and imposter syndrome. Solutions include promoting work-life balance, empathy, upskilling, mindfulness, and regular breaks. Maintaining mental well-being involves being involved in tech communities, setting realistic goals, embracing criticism, finding support, and prioritizing sleep.

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

Esta sesión explora el arte de la entrevista más allá de las evaluaciones tradicionales, centrándose en el cultivo de habilidades blandas, mentoría y reconocimiento de 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, profundiza 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 interacciones significativas que encuentren talento y posibles futuros líderes.

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

The Talk discusses the process of interviewing and identifying senior talent. It emphasizes the importance of assessing soft skills and qualities like communication, leadership, mentoring, and teaching abilities. Evaluating problem-solving skills involves observing the candidate's reaction and their focus on the actual problem, rather than the specific answer. The Talk also highlights the significance of ownership, autonomy, emotional intelligence, and the ability to handle failure. Finally, it mentions the importance of concluding the interview by asking questions to assess the candidate's fit and career stage.

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

La economía es terrible, los despidos están por todas partes y las entrevistas son difíciles. La búsqueda de empleo es agotadora y estresante, ¿entonces cómo superar todo eso? ¡Todo lo que necesitas es un plan! Ya sea superar los nervios o aprender 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 C para el Éxito

To maximize your potential for success in tech interviews, it is crucial to have a well-planned approach. The three C's to interview success are connections, confidence, and communication. Connections play a significant role in job search and personal branding is important. Building a personal brand and making connections can have a significant impact on your career. Content creation, confidence building, effective communication, and preparation are key for success 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

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 ayudar. En esta charla, iremos más allá:- 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 para mantener informados a tus jefes y asegurar la alineación con los objetivos organizativos?Habiendo liderado docenas de equipos en tiempos de grandes cambios, sé que liderar durante una desaceleració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

Efficiency and productivity are buzzwords in the tech industry, but they have been misused and misunderstood. Leadership roles in tech are evolving, and understanding engineering productivity is crucial. Effectiveness is about achieving goals and customer adoption, while efficiency is about doing things right with fewer resources. Prioritizing effectiveness, productivity, and efficiency can help businesses achieve their goals. Understanding company goals, aligning strategies, and involving the team in defining success metrics are key to driving productivity and improving team performance.

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

The Talk explores the transition from software developer to team leader, highlighting the different responsibilities and challenges involved. It discusses the role of an engineering manager in organizing team work, making top-level technical decisions, and representing the team externally. The challenges and satisfaction of being a manager are also explored, with an emphasis on the importance of the team's success and growth. The Talk concludes with tips for new managers and the possibility of returning to an engineering role.

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

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 pedimos ayuda 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. Maintainers give their time for free, out of passion. Even a small act of rudeness can burn people out. Start with a detailed search when asking for help in open source projects. Providing detailed information in issue reports is crucial. Creating reproducible repositories with minimum details is the best way to get a fix. Follow up on filed issues and show kindness and gratitude towards 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. Profundizaremos en las 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 las RFCs facilitan la toma de decisiones técnicas a nivel superior, 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 las RFC en Entornos de Alto Rendimiento

Mateus Palino from Quintana Roo presents From Chaos to Clarity, Leveraging RFCs in High-Performance Environments. Quintana Roo aims to improve delivery quality and reduce design time through RFCs. They have created a group called RFCs Advisors and focused on empowering focal points, training managers, and creating tools, guides, and processes. By implementing tailored training initiatives and optimizing design review meetings, they have increased the number and quality of RFCs, resulting in better solutions deployed.

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 sola palabra 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 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 buscar 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 a powerful tool that can improve relationships and foster growth. The BREW framework provides guidance for effective communication, emphasizing the importance of being present, reflecting, encouraging, and withholding judgment. Active listening involves understanding what is not being said and creates trust and empathy. By practicing active listening and using the BREW framework, leaders can become more effective in their roles.

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

En esta presentación, exploramos el papel de la diversión y los hobbies en la prevención del agotamiento en la industria tecnológica. Descubre cómo integrar la alegría y la creatividad en nuestras rutinas de trabajo puede mejorar la innovación y el bienestar. Únete a nosotros para obtener ideas y estrategias para adoptar un enfoque más equilibrado y satisfactorio hacia el trabajo tecnológico.

Reiniciando la alegría: aprovechando la diversión y los hobbies para redefinir el trabajo en el mundo tecnológico

Reignite your passion for tech by incorporating playfulness and hobbies into your daily grind. Organize mini hackathons, engage in pair programming, and dedicate time for curiosity hours. Helping others and participating in hack-a-thons are great ways to stay excited. What's one hobby or playful activity that could reignite your passion?

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é hay de los desarrolladores? Esta charla cubrirá 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 amount of available memory and cognitive resources a person has, and cognitive overload occurs when the load exceeds what can be sustained. Various factors, including disabilities and external factors like stress, can affect cognitive load. Attention deficit hyperactivity disorder (ADHD) and autism spectrum disorder (ASD) impact cognitive load differently, and instructional design can help reduce cognitive load for individuals with these conditions. Understanding cognitive complexity in code, optimizing the development environment, and minimizing distractions are important for managing cognitive load. Multitasking increases cognitive load, and using organizational systems, automation, and constant learning can help mitigate cognitive load and improve productivity.

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 destacarte y conectarte con otros.

Creación de Contenido para Desarrolladores

Today's Talk highlights the importance of technical content creation for developers and the benefits it brings. It emphasizes the value of becoming a thought leader and the opportunities it opens up in one's career. The Talk also provides practical tips for getting started with content creation, such as tailoring content to the audience, using storytelling techniques, and providing value to the readers. It further emphasizes the need for quality and consistency in content creation and the importance of sharing personal insights and experiences. Overall, the Talk encourages developers to step out of their comfort zone, share their knowledge, and grow both professionally and personally through content creation.

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.

Content Creation for Developers

Adrian Hajdin

Liderando con Pasión y Equilibrio

In this Talk, the speaker discusses the importance of effective leadership and maintaining well-being. They present a prioritization framework for task management, using the analogy of three types of threads: glass, bead, and rubber. Glass threads represent critical tasks that require personal attention, while bead threads can be managed collaboratively. The speaker emphasizes the need for delegation and empowering team members to take on leadership roles. They also highlight the importance of self-care and mental health in avoiding burnout.

Leading With Passion & Balance

Naz Delam

Transicionar de un rol de contribuidor individual a una posición de liderazgo, especialmente en la industria tecnológica de ritmo acelerado, es enormemente desafiante. La mayoría de los nuevos líderes no reciben ningún tipo de capacitación en los primeros 10 años de sus nuevas responsabilidades.Nuestro completo masterclass está diseñado para ayudar a los nuevos y emergentes líderes tecnológicos a comprender sus nuevos roles y adquirir las habilidades para convertirse en líderes seguros, felices y efectivos.

De Ingeniero a Líder: Un Masterclass para Líderes Tecnológicos Primerizos

This workshop explores leadership and communication skills in the software development industry. It covers the difference between leadership and management, essential traits of effective leadership, and the challenges of leadership. Effective communication is emphasized, with a focus on tailoring messages to different audiences and highlighting benefits over features. The workshop also addresses the importance of trust, time management, and personal growth in leadership roles.

Transitioning from an individual contributor role to a leadership position, especially in the fast-paced tech industry, is hugely challenging. Most new leaders don't receive any training at all in the first 10 years of their new responsibilities.Our comprehensive workshop is designed to assist new and emerging tech leaders in understanding their new roles and gaining the skills to make them confident, happy and effective leaders.

From Engineer to Leader: A Workshop for First-Time Tech Leaders

Andrew Murphy

Una Guía para Desarrolladores sobre Cómo Comunicar, Convencer y Colaborar Efectivamente con los Stakeholders Es una historia tan antigua como el tiempo: la colaboración entre desarrolladores y stakeholders de negocios ha sido durante mucho tiempo un desafío, con una falta de comunicación clara que a menudo deja a ambas partes frustradas. Los mejores desarrolladores pueden comprender profundamente las necesidades de sus contrapartes de negocios, comunicar efectivamente la estrategia técnica sin perder a la audiencia no técnica y convencer al negocio de tomar las decisiones correctas. Trabajando en una consultoría, he fallado y tenido éxito en arquitectar y “vender” visiones técnicas, aprendiendo muchas lecciones en el camino.Ya sea que trabajes en una empresa de productos, seas consultor/freelancer, o quieras aventurarte más allá de ser solo un desarrollador, la capacidad de convencer y comunicar claramente con los stakeholders puede diferenciarte en la industria tecnológica. Esto se vuelve aún más importante con el auge de GenAI y el mercado de desarrolladores cada vez más competitivo, ya que la resolución de problemas y la comunicación efectiva son clave para posicionarte.En esta masterclass, compartiré ejemplos del mundo real, tanto buenos como malos, y te guiaré a través de poner la teoría en práctica mediante dojos.

Managers Are From Mars, Devs Are From Venus

The Workshop titled Managers are from Mars, Devs are from Venus focuses on the importance of effective communication and collaboration between developers and stakeholders. It aims to break the cycle of adversarial relationships between business and tech and provides practical strategies for improving communication. The workshop covers topics such as understanding stakeholders, convincing them to adopt new technologies, and addressing challenges in software development. It also emphasizes the need to balance fast delivery with bug fixing and prioritize user retention. Overall, the workshop provides valuable insights and techniques for bridging the gap between managers and developers.

A Developer’s Guide to Communicating, Convincing, and Collaborating Effectively With Stakeholders It’s a tale as old as time - collaboration between developers and business stakeholders has long been a challenge, with a lack of clear communication often leaving both sides frustrated. The best developers can deeply understand their business counterparts’ needs, effectively communicate technical strategy without losing the non-technical crowd, and convince the business to make the right decisions. Working at a consultancy, I’ve both failed and succeeded in architecting and “selling” technical visions, learning many lessons along the way.Whether you work at a product company, are a consultant/freelancer, or want to venture beyond just being a developer, the ability to convince and clearly communicate with stakeholders can set you apart in the tech industry. This becomes even more important with the rise of GenAI and the increasingly competitive developer market, as problem-solving and effective communication are key to positioning yourself.In this workshop, I’ll share real-world examples, both good and bad, and guide you through putting the theory into practice through dojos.

Mo Khazali

Integrarse a un nuevo proyecto puede ser difícil, sin importar tu experiencia y antecedentes. Pero puede ser especialmente desafiante para los nuevos desarrolladores recién salidos de la escuela o de un bootcamp de programación. Basándose en su experiencia personal como graduado de un bootcamp y consultor de JavaScript, esta charla discutirá consejos y estrategias para que los gerentes ayuden a los nuevos desarrolladores de sus equipos a familiarizarse con un código desconocido, para que puedan tener un impacto más rápido y efectivo.

Fuera de la sartén, al fuego: Guía para gerentes sobre cómo ayudar a los nuevos desarrolladores a prosperar

This talk, titled 'Out of the Frying Pan and Into the Fire: A Manager's Guide to Helping New Developers Thrive,' covers real-life stories and concrete tactics for onboarding new developers. The speaker shares their experiences joining large organizations, navigating bureaucracy and building relationships, and overcoming challenges in both complex organizations and small startups. They emphasize the importance of preparation, clear instructions, and documentation for successful onboarding. The speaker also highlights the benefits of the buddy system, simulating onboarding, using checklists, and continuous improvement of the onboarding process. They encourage making a strong first impression and engaging in conversations for a successful onboarding experience.

Onboarding to a new project can be difficult, no matter your background and experience. But it can be especially challenging for new developers straight out of school or a coding bootcamp. Drawing on personal experience as a bootcamp grad and JavaScript consultant, this talk will discuss tips and strategies for managers to help the new developers on their teams get their bearings in an unfamiliar codebase, so they can make more of an impact, faster!

Out of the Frying Pan, Into the Fire: A Manager's Guide to Helping New Developers Thrive

Andrew Coleburn

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 objetivos.En esta sesión práctica e iluminadora, profundizaremos 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 de manera ética en los negocios, exploraremos 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 conducir a flujos de trabajo más fluidos, una mejor toma de decisiones y, en última instancia, un mayor éxito. En esta sesión, compartiremos 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

You are all influencers already in your teams and in your companies. If we learn how to master this skill, you can really achieve what you want. Collaboration is key to successful software development. Shift your thinking from old thinking to growth thinking. Effective collaboration requires more than just technical skills.

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

The time has come: the DevOps revolution is winding down, and we’re entering the post-DevOps era. We’re at the precipice of a massive generational shift in how we build and understand our software, and CTOs need to prepare.In the past, we were only interested in basic metrics on how we operated our software: reliability, uptime, MTTR, MTTD. Observability 1.0. Companies that settle for these basic data points will not survive in this new era.As engineering best practices around separating deploys from releases, testing in production, observability-driven development have become standardized, the approach to telemetry has stalled, and it’s time for a new version: Observability 2.0.Learn what this new version means for your engineers, and how to embrace this breaking change to:- Save them from drowning in symptom-based alerting- Help fewer people work together to build better software- Create fast feedback loops throughout the entire organization through highly granular visibility into all their systems

Observability Is Due for a Version Change; Are You Ready for It?

Charity Majors

TechLead Conference is an online event for middle and senior software developers to get knowledge of how to become a tech lead of a team, how to grow professionally. The conference will be held on June 15 & 19.

TechLead Conference

I'm attending TechLead Conference 2024 – get your free remote ticket and join me there

The conference is about leadership and seniority in teams. 20 engineers, managers and HR from leading companies will give talks on topics as careers and soft skills. We'll discuss how to become more senior and get more influence in the company, get a promotion and achieve what you want in your career.

TechLead Conference 2024

FocusReactive

FocusReactive will help you architect, build, and lead technically advanced websites focusing on performance and scalability. Partners and <a href="https://focusreactive.com/next-js-expert-agency/" target="_blank" rel="noopener noreferrer">experts in Next.js/Vercel</a>, Storyblok, Sanity, Contentful, Shopify Hydrogen, and other Headless eCommerce platforms.Whether you seek <a href="https://focusreactive.com/headless-cms-expert-agency/" target="_blank" rel="noopener noreferrer">expert Headless CMS agency</a> services or an expert agency with deep experience with platforms like Headless <a href="https://focusreactive.com/react-cms/" target="_blank" rel="noopener noreferrer">React CMS</a> &amp; <a href="https://focusreactive.com/nextjs-cms/" target="_blank" rel="noopener noreferrer">NextJS CMS</a>, FocusReactive is the one to help you scale.

As a special perk, we're offering a complimentary <a href="https://focusreactive.com/nextjs-performance-audit/" target="_blank" rel="noopener noreferrer">NextJS audit</a> designed to pinpoint areas for optimization, improve performance, and ensure you're following the best practices for SEO and security.&nbsp; Our expert team will closely examine your implementation, provide actionable insights, and help you leverage the full power of NextJS.

Free NextJS Performance and SEO Best Practices Audit

Next.js, Headless CMS and eCommerce expert agency

TechLead Conference 2024

Event about leadership and seniority