{"product_id":"the-missing-readme-isbn-9781718501836","title":"The Missing README","description":"\u003cb\u003eKey concepts and best practices for new software engineers — stuff critical to your workplace success that you weren’t taught in school.\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003eFor 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. \u003ci\u003eThe Missing README\u003c\/i\u003e 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.\u003cbr\u003e \u003cbr\u003eEarly 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.\u003cbr\u003e \u003cbr\u003eYou’ll learn:\u003cbr\u003e\u003cli\u003eHow to use the legacy code change algorithm, and leave code cleaner than you found it\u003c\/li\u003e\u003cli\u003eHow to write operable code with logging, metrics, configuration, and defensive programming\u003c\/li\u003e\u003cli\u003eHow to write deterministic tests, submit code reviews, and give feedback on other people’s code\u003c\/li\u003e\u003cli\u003eThe technical design process, including experiments, problem definition, documentation, and collaboration\u003c\/li\u003e\u003cli\u003eWhat to do when you are on-call, and how to navigate production incidents\u003c\/li\u003e\u003cli\u003eArchitectural techniques that make code change easier\u003c\/li\u003e\u003cli\u003eAgile development practices like sprint planning, stand-ups, and retrospectives\u003c\/li\u003e \u003cbr\u003eThis 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.\u003cbr\u003e \u003cb\u003ePreface\u003c\/b\u003e\u003cbr\u003e \u003cb\u003eChapter 1:\u003c\/b\u003e The Journey Ahead\u003cbr\u003e \u003cb\u003eChapter 2:\u003c\/b\u003e Getting to Conscious Competence\u003cbr\u003e \u003cb\u003eChapter 3:\u003c\/b\u003e Working with Code\u003cbr\u003e \u003cb\u003eChapter 4:\u003c\/b\u003e Writing Operable Code\u003cbr\u003e \u003cb\u003eChapter 5:\u003c\/b\u003e Managing Dependencies\u003cbr\u003e \u003cb\u003eChapter 6:\u003c\/b\u003e Testing\u003cbr\u003e \u003cb\u003eChapter 7:\u003c\/b\u003e Code Reviews\u003cbr\u003e \u003cb\u003eChapter 8:\u003c\/b\u003e Delivering Software\u003cbr\u003e \u003cb\u003eChapter 9:\u003c\/b\u003e Going On-Call\u003cbr\u003e \u003cb\u003eChapter 10:\u003c\/b\u003e Technical Design Process\u003cbr\u003e \u003cb\u003eChapter 11:\u003c\/b\u003e Creating Evolvable Architectures\u003cbr\u003e \u003cb\u003eChapter 12:\u003c\/b\u003e Agile Planning\u003cbr\u003e \u003cb\u003eChapter 13:\u003c\/b\u003e Working with Managers\u003cbr\u003e \u003cb\u003eChapter 14:\u003c\/b\u003e Navigating Your Career“This is an impressively thorough overview of the many skills a new software engineer will need to learn, beyond coding, to be successful in the job. A great book for new college grads and those just entering the profession who want to see what the next phase of their career curriculum will be.”\u003cbr\u003e\u003cb\u003e—Camille Fournier, former Vice President of Technology at Goldman Sachs and author of \u003ci\u003eThe Manager's Path: A Guide for Tech Leaders Navigating Growth and Change\u003c\/i\u003e\u003cbr\u003e\u003c\/b\u003e\u003cbr\u003e\"\u003ci\u003eThe Missing README\u003c\/i\u003e is exactly the book I wish I had when I started my career. Fun to read, full of sage advice and priceless stories. It is like having coffee with a senior mentor, except you don't even need to come up with the right questions. Very useful for engineers early in their career, and senior engineers who wonder what they missed.\"\u003cbr\u003e\u003cb\u003e—Gwen Shapira, Engineering Leader at Confluent\u003cbr\u003e\u003cbr\u003e\u003c\/b\u003e\"\u003ci\u003eThe Missing README\u003c\/i\u003e is an excellent practical introduction to the day-to-day realities of software engineering in the 21st century. It covers the wide range of essential skills, techniques and heuristics that you'll need to be an effective part of any team that builds, deploys and operates production systems.\"\u003cbr\u003e\u003cb\u003e—Adewale Oshineye, Developer Advocate at Google and co-author of Apprenticeship Patterns\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e\"This book puts together all the things you don’t learn on your own starting out. The information is well organized and a pleasure to read. I will be giving a copy to all my interns and new college grads.\"\u003cbr\u003e\u003cb\u003e—Thomas Hanley, Senior Engineering Manager\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e\"An accessible, handy guide to practical aspects of being a Software Engineer . . . The clear, Readme-style writing makes this book an excellent reference for any level Software Engineer from Intern to CTO.\"\u003cbr\u003e\u003cb\u003e—Tim Burns, Data Architect\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e\"\u003ci\u003eThe Missing README\u003c\/i\u003e provides practical and actionable insights for both new and seasoned developers. The authors cover, in detail, how to expertly navigate widespread obstacles software developers will encounter at any organization they join. This book is the README we all need.\"\u003cbr\u003e\u003cb\u003e—George D., Advanced Reviewer\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e“\u003ci\u003eThe Missing README\u003c\/i\u003e is like having a mentor on hand to give how-to tips and general encouragement. The book acknowledges that it will not describe every workplace or every situation, but the lessons offered should prove useful to both junior engineers and those already on their career path. For undergraduate students it could serve as a textbook for the things you don’t learn in Software Engineering Class . . . I plan to incorporate the chapter on 'Learning to Learn' as part of my lesson plans because I am always happy for my students to hear advice from another source.\"\u003cbr\u003e\u003cb\u003e—Mary Moore, Professor of Computer Information Systems at West Virginia University, Advanced Reviewer\u003c\/b\u003e\u003cb\u003eChris Riccomini\u003c\/b\u003e 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 Apache Samza.\u003cbr\u003e\u003cbr\u003e\u003cb\u003eDmitriy Ryaboy\u003c\/b\u003e is a software engineer and engineering manager. He’s worked at a variety of companies and organizations, including Lawrence Berkeley National Laboratory, Cloudera, and Twitter. He helped create and grow multiple open-source projects, including Apache Parquet. Dmitriy is currently the Vice President of software engineering at Zymergen.","brand":"No Starch Press","offers":[{"title":"Default Title","offer_id":46304439533797,"sku":"NP9781718501836","price":29.99,"currency_code":"USD","in_stock":false}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/1842\/7735\/files\/9781718501836.jpg?v=1767740535","url":"https:\/\/k12savings.com\/products\/the-missing-readme-isbn-9781718501836","provider":"K12savings","version":"1.0","type":"link"}