Plain-English explanations of the concepts that actually get tested — written against standard course topics and current published exam objectives, then linked straight into free practice on that exact topic.
s.upper() ran, produced the right answer, and threw it away. Plus negative indexes, slicing, traversal, .format() and f-strings.
Opening a file for writing empties it before you write a byte. Plus key-value lookup, KeyError, .get(), the counting idiom and try/except/else/finally.
number == 5 or 6 or 7 compiles, runs, raises nothing — and is true for every possible value. Plus truthiness, elif chains and why floats break ==.
The stop value is excluded, the accumulator has to accumulate, and a nested loop can be traced reliably — if you write down the right two columns.
A function that prints looks right and fails every test. A local variable vanishes the moment the call ends. Both cost marks, and neither looks like a mistake on screen.
y = x does not copy a list — it gives the same list a second name. The idea intro Python tests hardest, because you can get it wrong without anything crashing.
Retrieve instead of reread, space the sessions, read every explanation, and trace code by hand — with a two-week plan. Works without a class.
What every word of Hello World is doing — and the exact error each one gives when you change it.
javac makes bytecode, java runs it. Two tools, two kinds of error, and the five you hit first.
All eight types, plus integer division, silent overflow, floating-point drift and char arithmetic.
The plus sign is two different operators. That is where the wrong output comes from.
Prefix versus postfix in plain English — why x = x++ does nothing, and the hidden cast inside every compound assignment.
Why you cannot multiply through by the denominator, how to build a sign chart, and bracket or parenthesis.
Every connective, the one row where a conditional is false, and what a tautology actually is — the definitions a first test opens with.
Only one of the three says the same thing as the original — plus the “only if” vocabulary that causes the swap.
Push the negation inward, flip every quantifier it passes, and don’t let the conditional survive.
The skeleton a grader wants to see, two worked examples, and the line where the hypothesis must appear.
What each one assumes, what each must produce, and how to spot a proof wearing the wrong label.
The division algorithm hands you an exhaustive case split — and even/odd is often too coarse.
Name the witness, then verify it. The half that gets skipped is the half worth marks.
Truth table or chain of named laws — the same result two ways, and when each one is what was asked.
One shared key or a public/private pair, when each is used, and why TLS quietly uses both.
Port-based network access control: a device proves who it is before the network lets it in.
The NCLEX-RN practice app and exam guide are live. Every question in the app carries a written rationale in the meantime.
No guides match that yet.
These are not written yet. They are listed so you can see where each subject is going — not as links.
Java · Variables and scope · if / else and boolean logic · Loops and off-by-one errors · Methods and parameter passing · Arrays and ArrayLists · What a NullPointerException is telling you
Calculus · Involutions · Exponential equations · Solving trig equations · Trig identities · Conic tangents
Discrete Math · Rules of inference and common fallacies · Strong induction and when to use it · The well-ordering principle · Sets and set identities · Functions, injections and surjections · Counting and the pigeonhole principle
Security+ · The CIA triad · Phishing vs vishing vs smishing · SIEM explained · IDS vs IPS · SPF, DKIM & DMARC · SLE vs ALE (risk math)
Topic-selectable practice — offline, no ads, no account.
Choose your subject →