October 2024
Intermediate to advanced
270 pages
8h 13m
Spanish
Content preview from 97 cosas que todo programador Java debe saber
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Capítulo 38. Está hecho, pero...
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Jeanne Boyarsky
¿Cuántas veces has asistido a un stand-up, a un Scrum diario o a una reunión de estado y has oído la frase "Está hecho, pero..."? Cuando oigo eso, lo primero que pienso es "Entonces, no está hecho". Hay tres problemas con el uso de la palabra hecho cuando no está hecho.
1. Comunicación y claridad
Lo ideal es que tu equipo tenga una definición de "hecho". Pero incluso si no la tienen, probablemente exista alguna expectativa de lo que significa " hecho". Y, aún mejor, la persona que informa sobre el estado lo sabe. De lo contrario, no tendríamos un descargo de responsabilidad sobre la realización de la tarea.
Entre las cosas más comunes que no se hacen están escribir pruebas, documentación y casos de perímetro. Tómate un momento y mira a ver si se te ocurre alguna más. Del mismo modo, no me gusta el término hecho hecho. Bendice implícitamente la idea de que hecho no significa realmente hecho. Sé un comunicador claro. Si algo no está hecho, no digas que está hecho.
Esta es una oportunidad para que transmitas más información. Por ejemplo, "He codificado el camino feliz y ahora añadiré la validación" o "He terminado todo el código, lo único que me queda es actualizar el manual de usuario" o incluso "Creía que había terminado ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.