Computers and Programming

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.

Kubernetes exposes plenty of state, but operators still have to reconstruct operational meaning from scattered Pods, Services, EndpointSlices, Events, PVCs, owner references, and status fields. This ebook uses `kctx`, a small read-only Kubernetes context engine, to show how deterministic entities, relations, signals, graphs, namespace snapshots, CRD adapters, and stable JSON contracts can turn raw cluster data into reusable context for humans, tools, and AI agents. It is written for SREs, platform engineers, Kubernetes operators, infrastructure developers, and AI tooling builders who want better primitives than raw YAML and improvised troubleshooting pipelines.

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.

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.

Deliver What Matters, When It Matters is a practical guide to delivery optimization for teams working in complex environments. Through real-world stories and actionable tools, it helps coaches, product managers, and delivery leaders close the gap between effort and impact.

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.

The tech job market changed. Entry-level dropped 73%, AI screens resumes, interviews test system design. This is the no-BS guide: portfolio, resume, LinkedIn, interviews, negotiation, and your first 90 days. Written by someone who hires engineers.