Software Engineering

A practical handbook packed with real-world advice to help you write better code, adopt effective developer habits, and build great software.

What if AI could help build software that is not just functional but mathematically proven to work? This book shows how to combine Claude’s coding capabilities with Lean 4’s formal verification to create more reliable software. A practical guide to turning ambitious ideas into verified systems, without losing sight of real-world constraints.

Go beyond the basics of Claude Code with a practical engineering reference built for real-world development. Explore architecture, workflows, security, team adoption and advanced agentic patterns, with concrete commands and working examples throughout. Learn how to use Claude Code effectively, reliably and safely in professional software projects.

Build a real language server from the ground up in Rust. Learn how LSP works, then turn parsing, analysis and async Rust into autocomplete, diagnostics, go-to-definition, refactoring and more. By the end, you’ll have a production-ready server that works with VS Code, Neovim and other modern editors.

Go from your first line of Rust to building fast, safe, and production-ready applications with confidence. This practical guide explains every essential language feature, modern development tools, and key ecosystem crates through clear explanations and real-world examples, helping you write idiomatic, efficient and maintainable Rust code from day one.

This book is a practical guide to building and running local AI systems in 2026. Learn how to choose hardware, run modern LLMs, build RAG pipelines and AI agents, and deploy secure, efficient infrastructure while keeping full control of your models and data.

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?

An approachable, well-written, practice-oriented, academism-free guide into programming with types. How to build useful real-world type-level programs with low complexity and low risks.

Get yourself a new tool to manage your Rails application and your growing engineering organization! Prevent the ball-of-mud (and fix it!). Go for microservices or SOA if it makes sense not just because you don't have any other tool. Do all this through a low-overhead tool: packages. Enable better conversations to make practical changes today.

This is a book on Agile technical practices, principles and values. The readers will first learn individual practices (TDD, Refactoring, Pair Programming, simple design and more). Afterwards they will focus on principles of Software Design, their relationships and systemic reasons, ending with a business oriented and sociotechnical perspective.

Build a personal team of Grok Bot assistants and a second brain that preserves what you learn, without handing over your judgment or your security boundaries. This evidence-first playbook gives software engineers the roles, prompts, workflows, and metrics to test what actually improves their work.

In just a matter of days, a wave of rushed AI products exposed how far we are from the robots sci-fi writers spent decades crafting. Remember Commander Data, producing Sherlock Holmes–like deductions from his positronic brain; or WALL-E, spinning his tiny treads across a cosmic hush just to chase a crush. Even Arnie the Terminator was really polite when he decimated several police vehicles, with no intention of grazing a single cop. James Cameron even subtitled the sequence “Human Casualties: 0.0” just to soothe our nerves. Our actual machines are far from the level of Schwarzenegger excellence, but I’m not beginning this book by rattling the familiar skeletons in the AI closet. That topic belongs in the last part. What matters here is the connected narrative that robots will automagically create entire software suites, clean our inboxes, cure cancers or make coffee in a stranger’s house, with the last one being an unusual holy grail. Some gurus go further, promising the revolution will wipe illustrators, screenwriters, and musicians off the Earth, while the surviving coders will turn into sweaty blue-collars tapping ceramic tiles instead of their clickety keyboards. But just like WALL-E, we’ve tread this space before. I wrote my first QBASIC video game somewhere around 1996, right around the time Microsoft released IntelliSense, a little helper-bot that could pop up and write substantial chunks of code. It was followed by a long parade of development tools: Heftier code generators, collections of prebuilt components such as Bootstrap, content management systems such as WordPress and Drupal, and low-to-no-code builders such as Replit or Tabnine. Even Figma, the designer’s weapon of choice, was made to spout complete user interfaces. On top of that, gig platforms such as Fiverr began offering ghost-coding for just a couple of bucks. You’re guessing it right: Communities around these tools kept shouting that developers could finally rest and sip beach cocktails. But the opposite happened, and the number of programmers kept growing over the last 30 years, which brings us to the first irony. Pair the shortage of engineering talent with the ever-growing demand for software, and you get a simple revelation: It was precisely those sleep-deprived programmers who pushed hardest for stronger, more efficient tooling. For example, the JetBrains study shows that three out of four programmers had already embraced coding copilots. Stack Overflow, the site which has been steadily drained by those copilots, reports similar numbers. The result is the same: The people supposedly being automated away were first in line to build – and buy – that very same automation.

You Don’t Know JS Yet: The Unbooks is the final, draft-edition release of the second edition series—featuring the complete but unedited drafts of Book 3: Objects & Classes and Book 4: Types & Grammar, plus two bonus chapters reflecting on the “lost” books that were never written. This is the raw, honest conclusion to You Don’t Know JS Yet—a gift for readers who still care about deeply understanding JavaScript.

Olvídate de los frameworks de caja negra. Construye un agente de programación de IA de nivel profesional desde cero en Python puro — en la nube o local, probado con pytest, todo en un solo archivo.

Top 3 reasons why a software engineer might be interested to work at capital markets firms1) work with top Hedge Funds, Investment Banks, HFT firms, Algorithmic Trading firms, Exchanges, etc.2) implement smart algorithms and build low-latency, high-performance and mission-critical software with talented engineers3) earn top compensation