Software Development

Packaging behaviour under a name, and what a method can and cannot change for its caller.

What a subclass gets from its parent, and the order in which things happen.

Failing loudly, recovering deliberately, and swallowing neither.

A pipeline over a source, what runs lazily, and what comes out of the end.

What a variable actually holds, and how to choose the type that holds it.

What the symbols do when the types are not the ones you assumed.

Deciding once and repeating without copying, and the boundaries that go wrong.

Text that never changes, and what that costs when you build it in a loop.

Turning a description into instances, and what this and static each belong to.

One call, several bodies, and which one the JVM picks.

Where a value lives, what keeps it alive, and what the two memory errors mean.

What a hash map does with a key, and what it costs when two keys collide.

Teaching Java an order, for one natural ordering and for many.

Type parameters, what the compiler checks, and what is gone by runtime.

Passing behaviour as an argument, and the interface it is compiled against.

Two threads, one field, and the two different ways it goes wrong.

What synchronized guarantees, on which object, and what it still does not protect.

Handing work to a pool, getting a result back, and shutting it down without losing it.

A fixed run of values under one name, and the index that throws.

Naming a capability without saying how it is met.

Keeping state where only its owner can reach it.

The three methods every object inherits, and what breaks when two of them disagree.

Three interfaces, many implementations, and which name to declare a variable with.

Two lists with the same methods and opposite costs.

Collections that refuse duplicates, and collections that decide what comes out next.

A return type that makes "there might be nothing" impossible to ignore.

Starting work that runs beside your code, and what each thread takes to exist.

Four conditions, three failure names, and the ordering rule that removes one of them.

How long a bean lives, and the two moments the container promises to call you at.

One shape for every error response, wherever it comes from.

Two different answers to what an object mapped to a row actually is.

The four states an entity moves through, and the operations that move it.

What `@Transactional` actually wraps, and the two ways it surprises people.

Skipping work you've already done, on purpose, and knowing when to throw the answer away.

What javac produces, what java consumes, and why one file runs on every machine.

What the container actually is, and the five things it does to every bean before it's ready to use.

What Boot changes about starting a Spring application, and how it decides what to create for you.

One dependency instead of a dozen, and a server that ships inside the jar.

Where a setting comes from, and what wins when two sources disagree.

Turning a URL and a verb into a method call, and a method's return value into a response.

Refusing a bad request before it reaches your business logic.

Asking for data without writing the SQL yourself.

Finding the real bottleneck before optimizing the wrong thing.

Getting your dependencies handed to you — by constructor, and by name when there's more than one candidate.

Why Spring hands you your dependencies instead of you building them yourself.

How long a bean lives, and the two moments the container promises to call you at.

One shape for every error response, wherever it comes from.

Two different answers to what an object mapped to a row actually is.

The four states an entity moves through, and the operations that move it.

What `@Transactional` actually wraps, and the two ways it surprises people.

Skipping work you've already done, on purpose, and knowing when to throw the answer away.

What the container actually is, and the five things it does to every bean before it's ready to use.

What Boot changes about starting a Spring application, and how it decides what to create for you.

One dependency instead of a dozen, and a server that ships inside the jar.

Where a setting comes from, and what wins when two sources disagree.

Turning a URL and a verb into a method call, and a method's return value into a response.

Refusing a bad request before it reaches your business logic.

Asking for data without writing the SQL yourself.

Finding the real bottleneck before optimizing the wrong thing.

Getting your dependencies handed to you — by constructor, and by name when there's more than one candidate.

Why Spring hands you your dependencies instead of you building them yourself.

What a hash map does with a key, and what it costs when two keys collide.

A fixed run of values under one name, and the index that throws.

Three interfaces, many implementations, and which name to declare a variable with.

Two lists with the same methods and opposite costs.

Collections that refuse duplicates, and collections that decide what comes out next.

The three methods every object inherits, and what breaks when two of them disagree.

Packaging behaviour under a name, and what a method can and cannot change for its caller.

Keeping state where only its owner can reach it.

What a variable actually holds, and how to choose the type that holds it.

Teaching Java an order, for one natural ordering and for many.

Type parameters, what the compiler checks, and what is gone by runtime.

A pipeline over a source, what runs lazily, and what comes out of the end.

Getting your dependencies handed to you — by constructor, and by name when there's more than one candidate.

Skipping work you've already done, on purpose, and knowing when to throw the answer away.

Why Spring hands you your dependencies instead of you building them yourself.

Turning a URL and a verb into a method call, and a method's return value into a response.

Three interfaces, many implementations, and which name to declare a variable with.

A return type that makes "there might be nothing" impossible to ignore.

One call, several bodies, and which one the JVM picks.

Naming a capability without saying how it is met.

Keeping state where only its owner can reach it.

Teaching Java an order, for one natural ordering and for many.

Two different answers to what an object mapped to a row actually is.

What a subclass gets from its parent, and the order in which things happen.

Turning a description into instances, and what this and static each belong to.

One call, several bodies, and which one the JVM picks.

Naming a capability without saying how it is met.

Keeping state where only its owner can reach it.

The three methods every object inherits, and what breaks when two of them disagree.

Two threads, one field, and the two different ways it goes wrong.

What synchronized guarantees, on which object, and what it still does not protect.

Handing work to a pool, getting a result back, and shutting it down without losing it.

Starting work that runs beside your code, and what each thread takes to exist.

Four conditions, three failure names, and the ordering rule that removes one of them.

How long a bean lives, and the two moments the container promises to call you at.

Teaching Java an order, for one natural ordering and for many.

Passing behaviour as an argument, and the interface it is compiled against.

Failing loudly, recovering deliberately, and swallowing neither.

One shape for every error response, wherever it comes from.

Why Spring hands you your dependencies instead of you building them yourself.

Refusing a bad request before it reaches your business logic.