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 20. No varíes tus variables
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Steve Freeman
Intento que el mayor número posible de variables sean final porque me resulta más fácil razonar sobre código inmutable. Me simplifica la vida a la hora de codificar, lo cual es una gran prioridad para mí: he pasado demasiado tiempo intentando averiguar exactamente cómo cambia el contenido de una variable a lo largo de un bloque de código. Por supuesto, el soporte de Java para la inmutabilidad es más limitado que el de otros lenguajes, pero aún hay cosas que podemos hacer.
Asignar una vez
He aquí un pequeño ejemplo de una estructura que veo por todas partes:
Thing thing;
if (nextToken == MakeIt) {
thing = makeTheThing();
} else {
thing = new SpecialThing(dependencies);
}
thing.doSomethingUseful();
Para mí, esto no expresa de forma irrevocable que vamos a establecer el valor de thing antes de utilizarlo y no volver a cambiarlo. Me lleva tiempo recorrer el código y darme cuenta de que no será null. También es un accidente a punto de ocurrir cuando necesitamos añadir más condiciones y no acabamos de entender la lógica. Los IDE modernos advertirán sobre algo no establecido, pero muchos programadores ignoran las advertencias. Una primera solución sería utilizar una expresión condicional:
final var thing = nextToken ...
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.