?
am i not understanding something - or - do the code questions in the Self-Tests - especially chaptr3 have no relation at all to any of the material or code examples in any chaptrs in the book - in fact - ((NO - IT DOES Have relation -BUT- the code is written in a more complicated & sometimes purposely misleading way)) i haven’t seen code like that anywhere in any books & by now - i’ve seen alot of weird (& interesting) stuff...
Budi questions seem a bit too easy
OCA/ocp book quest’s seem too hard - overly obfuscating
Enthuware seem to be the right balance between difficulty & relationship to the objectives/material - but - since i haven’t taken the actual exam yet - i’m just guessing that this is true...
Positive Value Usage of OCD:
i’ve utilized/leveraged - my slight ocd to learn the material - but - can’t get caught-up in minor details at the ... (?) (insert: expense) of the overall picture
OCD Trap:
-ie- be mindful not to let ocd ctrl behavior -&- then get distracted by less important details
btw: i need more keyboard chars (download app)
---
i get rattled too easily - bc - omg - i get it...
really interesting stuff & yes - it’s true - the self-test code is different than chaptr explanation code - most recent example:
you can instantiate in different ways:
purposely obfuscating code = using ivar & parameter w/same name - but - not shadowing (?):
class Tester {
float f1 = 3.14f; // instance var (ivar)
double t2 = 5.5; // ivar t2 - vs- parameter t2 (below)
static Tester aMethod(Tester t1, Tester t2){
Tester q1 = t2; // -or- Tester q1 = new Tester();
q1.f1 = 9.5f; //ref var q1 & f1 is the ivar of type float
q1.t2 = 3.14; // not parameter t2 - but - ivar t2 !!
// u could really be a pain-in-the-butt and write:
t2.t2 = 5.5; // 1st t2 is parameter & 2nd t2 is primitive ivar (double)
new Tester().f1= 1.1f; // equivalent to using q1 ref/var
return t1;
}
} // i got upset: how can u assign a numeric value to that object ref... lol
/* the self-tests & practice Xams help u id gaps in understanding &/or knowledge */
// 1 good thing though - i read the code in 2-3 seconds bc of acronym use
// -but- the actual question was about the: equality operator ==
//chaptr 3 / q5
//the idea - i think - is not to memorize ans - but - to understand (even if //memorization is a consequence) the code scenario & associated rules