Books

A direct route from the basics to real-world Haskell. Master functions, types, and effects, structure real projects, and ship a working blog engine. Along the way, you learn design principles that make you a stronger engineer in any language.

Pull a model onto a machine you own, shape it with a Modelfile, fine-tune your own adapter, and build a chat app that calls tools and talks to an MCP server, all running on your own hardware. By the end, you'll know exactly where owning your AI beats renting it, and where it doesn't.

Before containers, service meshes, and modern security platforms, qmail showed how much could be achieved with Unix processes, file permissions, queues, and discipline.

Software and infrastructure only create value when they pull in the same direction as the business. This book shows IT leaders how to get there: from shaping IT strategy and the architecture roadmap to the daily discipline of IT and architecture governance, all built on a pattern-based approach that adapts to your organization rather than forcing it into a template.Grounded in established frameworks such as TOGAF, COBIT, and ITIL, it pairs solid fundamentals with numerous real-world examples — and gives growing weight to compliance and IT security, now central concerns of any IT management agenda.This English edition is based on the German standard work on the subject, fully revised in its 4th edition (late 2024). It is current with TOGAF 10 and reflects recent developments in business-oriented enterprise architecture — including the open-source tool EDGY and patterns for digital strategy — alongside the latest trends in IT risk management and cybersecurity architecture.

This book takes you straight into the Compose compiler, runtime, and UI layer, all about Compose performance tuning, reading the source line by line and explaining the why behind every design decision, then connecting each internal mechanism back to the code you write every day. The Course: Jetpack Compose Mechanisms | Hardcover | ISBN-13: 9798185354780

Once the five essential hooks are in place, the incidents that keep happening are the guards themselves failing, silently. Nine chapters collect the hooks (Git, credentials, token spikes, autonomous operation, multi-agent work), a chapter on hooks that do not fire, eight dated incidents from the author's own unattended operation, and a 50-point audit you can run against your own setup.

Lo que no te cuentan sobre construir el software que mueve un e-commerce en LATAM: facturación electrónica ante el SII, concurrencia con plata de por medio, marketplaces con sus gotchas no documentadas y multi-moneda sin descuadres de un peso. No es teoría ni un "hola mundo": son las decisiones, los bugs que costaron dinero y los patrones que vienen de operar un ERP multi-tenant real en producción.

Coder ne suffit plus. N'importe quel LLM peut générer du code. Pour vingt dollars par mois.Ce qui change tout, c'est d'avoir une **méthode**. Sans méthode, l'IA te produit du code.Avec une méthode, elle te produit le logiciel dont tu as besoin. --- Le vibe coding a un problème Les deux premières semaines sont magiques. Chaque session produit duvrai code. Le projet grandit vite. Troisième semaine : tu corriges un module, quelque chose casse ailleurs.Quatrième semaine : l'agent ne se souvient plus des décisions prises.Cinquième semaine : ce qui prenait une heure en prend maintenant trois. Ce n'est pas un bug. C'est l'absence d'artefact de référence partagé. --- La solution : la spec comme artefact primaire **Spec-Driven Development (SDD)** inverse l'ordre habituel. Le code ne sert plus de source de vérité. La spec l'est.Le code implémente la spec. Les tests vérifient la spec.Et quand quelque chose dérape, tu mets d'abord à jour la spec. Un `.md`. Versionné avec git. Toujours à jour. C'est tout. --- Ce que tu vas apprendre - Pourquoi le vibe coding se dégrade et les 3 symptômes universels- Ce qu'est réellement le SDD (et ce qu'il n'est pas)- Les 7 phases du développement sérieux avec l'IA- Comment écrire un PRD en ~500 mots qui guide tout le reste- Comment transformer un PRD en issues GitHub actionnables- La boucle d'exécution : spec → agent → révision → itération- Les outils : GitHub SpecKit, OpenSpec, et les flux agnostiques- Les antipatterns les plus coûteux et comment les éviter- SDD en équipe, en greenfield et en brownfield- 3 cas complets : webhook, notifications, API publique --- Ce livre est fait pour toi si… - Tu utilises déjà l'IA pour coder mais les projets deviennent ingérables- Tu veux livrer plus vite sans perdre le contrôle de l'architecture- Tu travailles seul ou en équipe et tu cherches un cadre reproductible- Tu veux comprendre la méthode, pas juste copier des prompts

Go from an empty cluster to a self-deploying GitOps pipeline, doing every step yourself: Applications, sync policy, hooks, RBAC, Helm, ApplicationSets, and a setup that ships every branch on push. You finish with a pipeline you can explain line by line, not a demo you watched run.

Go from monolithic frontend pain to a fully deployed micro frontend architecture. A hands-on, production-focused guide to Webpack 5 Module Federation, ending with a complete multi-team app you build and ship yourself.

Why learn one programming language when you can understand three at once? This book introduces the foundations of programming through a powerful side-by-side comparison of Python, Java, and C#, enabling readers to build strong conceptual understanding, transferable coding skills, and a solid pathway toward modern software engineering.

A leader at a company opens Slack one morning. The brief their virtual employee wrote looks normal: same headers, same prose voice, same cadence as every other brief that week. The last line ends mid-sentence. The API returned `stop_reason: "max_tokens"`. The system shipped it anyway. No exception. No log line. No retry. That bug doesn't look like the normal kind. This book is about why, and what to build instead.

With the advent of LLMs and AI coding assistants, we are generating code at an ever-accelerating rate. How do we manage this influx of code without getting fatigued and overwhelmed? How do we ensure coding standards are maintained? What practices and tools can we put in place to amplify our efforts while not introducing more bugs?

You are not losing velocity because your engineers are slow. You are losing velocity because every line of untested code is a landmine your team laid for itself — and sooner or later, someone steps on it. This is the book that explains why. No syntax. No tutorials. Just the argument, the evidence, and the standard your team should already be held to. A 30-minute read that changes how you lead software quality forever.

A typed, signed-deliverable playbook for the enterprise-scale Oracle 19c → Azure migration. Across fifteen chapters, thirteen signed JSON deliverables chain end-to-end from Migration Assessment Bundle to Decommissioning Readiness Report. Defensible at a code review. Sign-off-ready for a director.