Meet the Corydon authors.

Skyler has spent years on red team engagements and writes the attacker’s side of the story with unusual clarity. Her PenTest+ material walks the full kill chain, then spends just as long on the reporting that most curricula skip.

Daniel came up through network operations and still keeps a lab of ageing switches for the exercises he writes. His certification material is known for cutting the theory that never appears on an exam and drilling hard on the parts that do.

Sarah works at the point where security meets audit, translating framework language into controls that engineering teams can actually implement. She is one of the few writers in the field who makes governance material genuinely readable.

Eleanor works on large language model systems in production, where cost, latency and safety matter more than benchmark scores. She writes for engineers who have to make a model useful inside a real product, and she is candid about what does not work yet.

Marcus builds data products and teaches the messy middle of the job — cleaning, framing the question and knowing when a model is not the answer. His writing leans heavily on worked examples, because he is convinced nobody learns analysis by reading about it.

Lynette runs the three-pass technical review that every Corydon title goes through before it reaches a printer. She has spent her career making expert writing readable without flattening the expertise, and authors credit her with the questions that fixed their weakest chapters.

Alicia has led security operations teams through more incidents than she cares to count, and she teaches detection the way an analyst experiences it — ambiguous alerts first, tidy conclusions later. She is unusually good at explaining why a control fails, not just how it works.

Tom writes the practice-question banks that tell candidates whether they are actually ready, and he grades his own questions against real exam feedback. He has coached hundreds of first-time candidates through CompTIA certifications and knows exactly where people talk themselves out of the right answer.

Akanksha has spent a decade building and running platforms on AWS and Kubernetes, most of that time on call for the systems she designed. She writes the way she works — starting from what actually breaks in production, then explaining the architecture that prevents it.

Raymond designs cloud architectures for organisations large enough that mistakes are expensive, and he has the scar tissue to prove it. He writes for practitioners preparing for AWS certification who also have to defend their design choices at work on Monday.

Aleeya ships machine learning systems that stay up long after the demo is over, with a focus on evaluation, monitoring and the unglamorous parts of MLOps. Her chapters are built around real pipelines, so every example runs against current tooling rather than a toy dataset.