Books

A hands-on guide for engineers and architects to build, optimize, and deploy scalable production-grade AI systems and LLM infrastructure.

A calm, practical guide for real people who want to stay active without pain, strain, or intense workouts. Designed for beginners, busy adults, and anyone needing a gentle, sustainable movement routine.

Take control of your storage with FreeCORE: The Complete Guide. From your first installation to advanced ZFS management, network shares, security, backups and performance tuning, this practical guide shows you how to build, manage and troubleshoot a reliable NAS with confidence, whether you are running a home lab or a production environment.

What if your software did not need the cloud to work? Local First Software Development shows you how to build fast, reliable apps that work offline and sync when needed. Learn practical patterns for data, security and synchronization while exploring how local-first systems can grow from simple personal tools into large collaborative applications.

How do complex phase-separation processes become solvable mathematical models?The Cahn–Hilliard equations lie at the heart of modern phase-field modeling—but their nonlinear, higher-order nature makes them notoriously challenging to solve.Solutions of the Cahn–Hilliard Equations explores analytical, approximate, and numerical approaches for tackling these equations, bringing together mathematical insight and practical solution techniques.A concise reference for researchers, engineers, and postgraduate students working in applied mathematics, computational science, materials modeling, and phase-field methods.Understand the equations. Explore the methods. Solve the problem.Rahul Basu

He conquered the heavens and enslaved the gods, but the quiet pressure of a single toe brought the universe's proudest king to his knees. Pinned beneath a mountain for a thousand years, he must tear the music from his own flesh to find redemption. Witness the epic collision of absolute pride and divine surrender in The Veena of Bone.

A gentle companion for anxious, frightened and difficult moments. Choose the path that feels closest, read one message and take only the small choice you need. Written by Lucy from personal experience, these words sit beside you without judgement or pressure.

What happens when scale, dependencies, compliance, governance and AI all press on your delivery system at once. Written from 25+ teams building FedRAMP-authorised government software.

¿Qué siente un olivo que recuerda unos ojos que nunca volverá a ver? ¿Qué sueños guarda una muralla cuando el mundo ha olvidado aquello que juró proteger? ¿Puede un humilde romero encontrar la felicidad contemplando el vuelo de una colibrí dorada?En Versos de alma y polvo, la naturaleza, los objetos cotidianos y los paisajes se convierten en espejos del alma humana. A través de relatos poéticos cargados de simbolismo, esta obra explora la memoria, el amor, la pérdida, la soledad, la esperanza y la búsqueda de significado en un mundo marcado por el paso del tiempo.Cada poema es una pequeña historia donde lo sencillo adquiere voz propia y donde aquello que parece insignificante revela verdades universales. Entre bosques, campos, pueblos olvidados y fuegos ancestrales, el lector encontrará un viaje íntimo que habla de todos nosotros.Porque, al final, todos somos un poco alma y un poco polvo. 

You don't buy what's best. You buy what makes sense to you. A computer that won on every spec — rejected. A jar of sauce nobody noticed — suddenly irresistible the moment it vanished. A salesman who talked you out of the sale — and made it. Why We Buy? follows five real, first-person moments where logic lost to something quieter: trust, timing, and the story we tell ourselves about our own choices. No diagrams. No slogans. Just the exact instant a "no" became a "yes" — and why.

The second half of a from-scratch AI/ML course that refuses to skip the hard parts: LSTMs, real attention, a working transformer, LoRA fine-tuning derived and measured, and a genuine multi-tool, multi-agent system — every mechanism built by hand, then checked against PyTorch and real numbers.

Excerpt 1 — Chapter 1, "Introduction": why cybersecurity management is not about technologyThe simplest way to manage an organization's cybersecurity is to draw up a list of technical measures ("install antivirus software," "enable multi-factor authentication," "encrypt disks") and carry them out one by one. This approach has an obvious advantage — simplicity — but also a systemic flaw: it does not answer the question of which measures this particular organization actually needs, to what extent, and what to do when there are not enough resources for "the whole list." It also creates a false sense of completeness: "we implemented everything on the list — so we are secure," even though the real level of risk depends not on the length of the list but on how well the measures match the specific threats and the value of the organization's assets. Excerpt 2 — Chapter 1: cyber risk within enterprise risk managementIf cybersecurity is about managing risk rather than a checklist of technical measures, the logical continuation of this idea is as follows: cyber risk is not a separate, isolated category discussed only by the IT department in its own language. It is one of the types of risk that any enterprise faces — alongside financial, reputational, operational, and supply chain risk. It should be managed within the same frame of reference as other enterprise risks. Excerpt 3 — Chapter 14, applying the Chapter 10 mapping methodology: where a mapping gap becomes a technical projectThe last row is the central conclusion of this step, and of the whole case study: the mapping table shows honestly that no Annex A control exists for PR.AA-04 that can simply be marked "done" and the gap considered closed. An organization relying only on the SoA, or only on the mapping table, could mistakenly conclude that because A.5.17 partially covers the topic, no further action is needed — which is exactly why the gap analysis, the SoA, and the risk register above all consistently define SSO as a separate, explicit technical project, rather than a derivative action from existing controls. Excerpt 4 — Chapter 14, closing paragraph of the bookThe running case study in this chapter has shown that the fifth step of the Chapter 7 methodology — "the organization can repeat these steps as often as needed" — is not a rhetorical flourish but a real operating cycle: MFA for contractors, backup encryption, and automatic deactivation in the ERP, each opened by a separate cycle in Chapters 6–7 and 13, were already closed and verified by the time this chapter began, and the very fact of their closure — through broadening the profiling scope to identity management across the ERP and CRM together — opened up a new, precisely formulated gap, PR.AA-04, reflected consistently and at once in the updated profile, the action plan, the SoA, the risk register, and the mapping table. It is precisely this consistency among five tools converging on a single decision, not the mere existence of each tool on its own, that is the practical upshot of building an integrated cybersecurity management system.

A calm, cinematic outdoor guide covering the four core survival fundamentals: fire, shelter, water, and navigation. Designed for beginners who want real outdoor confidence.

A model that crashes is a good day. The dangerous failures return answers — plausible, fluent, and wrong. 100 failures. 63 diagnostic instruments. One rule: inspect what actually happened.