Ryaboy dmitriy (8 Ergebnisse)

Zustand: good. Gently used with minimal wear on the corners and cover. A few pages may contain light highlighting or writing, but the text remains fully legible. Dust jacket may be missing, and supplemental materials like CDs or codes may not be included. May be ex-library with library markings. Ships promptly. …

Zustand: New.

Paperback. Zustand: Brand New. 224 pages. 9.00x6.00x0.78 inches. In Stock.

Zustand: New. In English.

Taschenbuch. Zustand: Neu. Neuware - 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 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.…

Kartoniert / Broschiert. Zustand: New. Chris Riccomini is a software engineer, startup investor, and advisor with more than a decade of experience at major tech companies such as PayPal, LinkedIn, and WePay. He has been involved in open source throughout his career and is the author of Ap.

Taschenbuch. Zustand: Neu. Neuware -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 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.eucomply OÜ, Pärnu mnt 139b-14, 11317 Tallinn Englisch.…

Taschenbuch. Zustand: Neu. Neuware -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 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. Englisch.…