Java for Fucking Idiots: Learn the Basics of Java Programming Without any experience!

new
House();
System.
out
.println(coloredHouse.
color
);

---

The answer? It’s…. the … color…. White! Yep, the constructor’s code runs
after the properties’ values are assigned.
You can verify this by adding some Sysouts.
class
House {
String
color
=
"Gray"
;
House() {
System.
out
.println(
color
);
color
=
"White"
;
System.
out
.println(
color
);
}
}
The result?
>
Gray
> White
Bob had Gray on his blueprint, but when he went to start building, he
decided on White instead.
Brain teaser over. Your brain is no longer being teased.
Brain teaser #2!
Haha, gotcha! We’re back with another one.
What if we create a constructor that looks like this?
class
House {
String
color
;
House(String color) {
color = color;
}
}
What the hell even happens on a line of code where we say that “color”
should be assigned the value of “color”??? color = color???

---

The answer is nothing happens. The house’s color property is left alone.
The custom color value that we’re providing Bob is re-assigned the same
value. That’s fucking stupid.
We can fix this by specifying that we want to assign the custom 
color
to our
property color .
class
House {
String
color
;
House(String color) {
this
.
color
= color;
}
}
Just like you can access an object’s properties and methods with “dot
notation”, a.k.a. a period, an object can refer to its own properties and
methods using this followed by the dot.
Which is great in this case where we need to differentiate between our
property and the parameter, both with the same name.
¿Porque no los dos?
It’s time to introduce you to a concept called engineer overkill.
Wait, that’s not it….
Constructor strain?
No, no…. constructor…overload? Yep, that’s it! Constructor overloading !
Fortunately for me, the Java developer, I don’t have to have just one
constructor. I can have as many, or as few, as I want!
Unfortunately for you, it’s another thing you should learn.
Treat your eyes to this: two constructors!!