Books

Closures, this, the event loop, async: the five topics that make people quit JavaScript, finally explained, so they click. Learn them all by building a retro arcade, one machine at a time.

Master copywriting by doing it: 16 modules, 35+ templates, 16 worksheets, and a full portfolio project — learn to write copy that gets read, clicked, and acted on.

Certainty feels safe - but in an uncertain world, it's a bug, not a feature. A Data Engineer shows how the craving for absolute truth is a form of "overfitting," and how thinking in probabilities makes you more creative, resilient, and right more often.

O abordare vizuală și practică a programării C/C++, bazată pe ani de experiență în predare. Cartea combină teoria, exemplele și schițele inspirate din caietele reale ale cursanților pentru a facilita înțelegerea conceptelor complexe.

An enterprise-focused guide to building a safe, governed AI SRE agent skill that reviews Kubernetes platforms on Talos Linux. Read-only by default, auditable, and grounded in evidence rather than guesswork.

In this practical and insightful guide, Mohammed Hamed Ahmed Soliman brings the proven principles of Lean to the world of software development. Whether you’re managing large-scale enterprise applications or agile startup teams, this book will show you how to eliminate waste, optimize flow, and deliver real customer value—faster.

Personally, I think that the Assembly system of conditional jumps makes a lot of sense. Other programming languages such as BASIC and C have "goto" statements that work like this. For example, `if(eax<ebx){goto less;}`. Modern programming languages tend to discourage the use of goto or not allow it at all. However, these languages still use jumps I have described in this section because it is required by the hardware. Both "if" and "while" statements are written by using the conditional jump statements most relevant to what you are trying to do. The only thing I have found difficult about jumps in assembly is remembering which acronym means which condition. However, since I created the chart in this chapter, now I can refer to it, and you can too! As long as I keep these six main types of conditions in my head and am working with unsigned numbers, I can write almost any assembly program from scratch.

Stop maintaining CLAUDE.md and AGENTS.md as two files that drift apart. This handbook documents which file each of nine tools reads — checked on 2026-06-02 against each tool's official docs — and ranks six ways to keep one instruction file in sync, from an @AGENTS.md import to a symlink to a CI drift check. It is also precise about where official support still is not: issue #6235 was closed as completed, but the official CHANGELOG does not mention AGENTS.md anywhere, and on v2.1.246 AGENTS.md is still not loaded into the model's context the way CLAUDE.md is.

Between March and April 2026, Claude Code subscribers lived through six weeks of stacked regressions: cache TTL shortened from sixty minutes to five, a tokenizer that charged 1.35 to 1.46 times more for the same prompts, Pro access that briefly disappeared, and a third-party tool ban. This playbook turns that window into a decision instead of a guess: five measurable triggers, three paths — stay and fortify, switch, or build your own stack — and a decision tree that returns one specific recommendation, with a 30-day cost projection for each path. Edition 2 is 251 pages: ten chapters, six path supplements and four appendices, reconstructed from public GitHub issues, Hacker News threads, and independent measurement posts.

Once the five essential hooks are in place, the incidents that keep happening are the guards themselves failing, silently. Eight 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.

Build four real mobile apps from scratch — no coding experience required. Claude Code handles the code. You handle the idea.

Most iOS interview books teach you the answer. This one shows you what a senior sounds like giving it: three versions of every answer, candidate, senior, and staff, side by side, so you can see the gap between correct and hired. 178 questions across six career levels, each with the follow-up that decides it and the red flag that ends the loop.

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.

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.