

Beschreibung
Informationen zum Autor Chris Riccomini and Dmitriy Ryaboy Klappentext Key concepts and best practices for new software engineers stuff critical to your workplace success that you weren't taught in school. For new software engineers, knowing how to program is ...Informationen zum Autor Chris Riccomini and Dmitriy Ryaboy Klappentext Key concepts and best practices for new software engineers stuff critical to your workplace success that you weren't taught in school. For new software engineers, knowing how to program is only half the battle. You'll quickly find that many of the skills and processes key to your success are not taught in any school or bootcamp. The Missing README fills in that gapa distillation of workplace lessons, best practices, and engineering fundamentals that the authors have taught rookie developers at top companies for more than a decade. Early chapters explain what to expect when you begin your career at a company. The book's middle section expands your technical education, teaching you how to work with existing codebases, address and prevent technical debt, write production-grade software, manage dependencies, test effectively, do code reviews, safely deploy software, design evolvable architectures, and handle incidents when you're on-call. Additional chapters cover planning and interpersonal skills such as Agile planning, working effectively with your manager, and growing to senior levels and beyond. You'll learn: How to use the legacy code change algorithm, and leave code cleaner than you found itHow to write operable code with logging, metrics, configuration, and defensive programmingHow to write deterministic tests, submit code reviews, and give feedback on other people's codeThe technical design process, including experiments, problem definition, documentation, and collaborationWhat to do when you are on-call, and how to navigate production incidentsArchitectural techniques that make code change easierAgile development practices like sprint planning, stand-ups, and retrospectives This is the book your tech lead wishes every new engineer would read before they start. By the end, you'll know what it takes to transition into the workplacefrom CS classes or bootcamps to professional software engineering. Zusammenfassung Key concepts and best practices for new software engineers stuff critical to your workplace success that you weren't taught in school. For new software engineers, knowing how to program is only half the battle. You'll quickly find that many of the skills and processes key to your success are not taught in any school or bootcamp. The Missing README fills in that gapa distillation of workplace lessons, best practices, and engineering fundamentals that the authors have taught rookie developers at top companies for more than a decade. Early chapters explain what to expect when you begin your career at a company. The book's middle section expands your technical education, teaching you how to work with existing codebases, address and prevent technical debt, write production-grade software, manage dependencies, test effectively, do code reviews, safely deploy software, design evolvable architectures, and handle incidents when you're on-call. Additional chapters cover planning and interpersonal skills such as Agile planning, working effectively with your manager, and growing to senior levels and beyond. You'll learn: How to use the legacy code change algorithm, and leave code cleaner than you found it How to write operable code with logging, metrics, configuration, and defensive programming How to write deterministic tests, submit code reviews, and give feedback on other people's code The technical design process, including experiments, problem definition, documentation, and collaboration What to do when you are on-call, and how to navigate production incidents Architectural techniques that make code change easier Agile development practices like sprint planning, stand-ups, and retrospectives This is the book your tech lead wishes every new engineer would read ...
Autorentext
Chris Riccomini and Dmitriy Ryaboy
Klappentext
Key concepts and best practices for new software engineers — stuff critical to your workplace success that you weren’t taught in school.
For new software engineers, knowing how to program is only half the battle. You’ll quickly find that many of the skills and processes key to your success are not taught in any school or bootcamp. The Missing README fills in that gap—a distillation of workplace lessons, best practices, and engineering fundamentals that the authors have taught rookie developers at top companies for more than a decade.
Early chapters explain what to expect when you begin your career at a company. The book’s middle section expands your technical education, teaching you how to work with existing codebases, address and prevent technical debt, write production-grade software, manage dependencies, test effectively, do code reviews, safely deploy software, design evolvable architectures, and handle incidents when you’re on-call. Additional chapters cover planning and interpersonal skills such as Agile planning, working effectively with your manager, and growing to senior levels and beyond.
You’ll learn:
How to use the legacy code change algorithm, and leave code cleaner than you found itHow to write operable code with logging, metrics, configuration, and defensive programmingHow to write deterministic tests, submit code reviews, and give feedback on other people’s codeThe technical design process, including experiments, problem definition, documentation, and collaborationWhat to do when you are on-call, and how to navigate production incidentsArchitectural techniques that make code change easierAgile development practices like sprint planning, stand-ups, and retrospectives
This is the book your tech lead wishes every new engineer would read before they start. By the end, you’ll know what it takes to transition into the workplace–from CS classes or bootcamps to professional software engineering.
Inhalt
Preface
Chapter 1: The Journey Ahead
Chapter 2: Getting to Conscious Competence
Chapter 3: Working with Code
Chapter 4: Writing Operable Code
Chapter 5: Managing Dependencies
Chapter 6: Testing
Chapter 7: Code Reviews
Chapter 8: Delivering Software
Chapter 9: Going On-Call
Chapter 10: Technical Design Process
Chapter 11: Creating Evolvable Architectures
Chapter 12: Agile Planning
Chapter 13: Working with Managers
Chapter 14: Navigating Your Career
