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 8. Divide los problemas y las tareas en pequeños trozos
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Jeanne Boyarsky
Estás aprendiendo a programar. Recibes un pequeño encargo. Escribes menos de mil líneas de código. Lo tecleas y pruebas. Luego añades declaraciones de impresión o utilizas un depurador. A lo mejor te tomas un café. Luego reflexionas sobre lo que estabas pensando.
¿Te suena? Y eso es sólo un problema de juguetes. Las tareas y los sistemas de trabajo son mucho más grandes. Los grandes problemas requieren tiempo para resolverse. Y lo que es peor, hay demasiado que retener en la RAM de tu cerebro.
Una buena forma de afrontarlo es dividir el problema en pequeños trozos. Cuanto más pequeños, mejor. Si consigues que ese pequeño trozo funcione, ya no tendrás que pensar más en él y podrás pasar al siguiente. Si lo haces bien, debes escribir pruebas automatizadas para cada pequeño problema. También deberías hacer commits con frecuencia. Así tendrás un punto de retroceso cuando las cosas no funcionen como esperabas.
Recuerdo que ayudé a un compañero de equipo que estaba atascado. Le pregunté cuándo se había comprometido por última vez, porque la solución más fácil sería hacer retroceder y volver a aplicar el cambio. La respuesta fue "hace una semana". Entonces tuvo dos problemas: el original ...
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.