I M Wright S Hard Code

Get the brutal truth about coding, testing, and project management—from a Microsoft insider who tells it like it is. I. M. Wright's deliberately provocative column "Hard Code" has been sparking debate amongst thousands of engineers at Microsoft for years. And now (despite our better instincts), we're making his opinions available to everyone. In this collection of over 80 columns, Eric Brechner's alter ego pulls no punches with his candid commentary and best practice solutions to the issues that irk him the most. He dissects the development process, examines tough team issues, and critiques how the software business is run, with the added touch of clever humor and sardonic wit. His ideas aren't always popular (not that he cares), but they do stimulate discussion and imagination needed to drive software excellence. Get the unvarnished truth on how to: Improve software quality and value—from design to security Realistically manage project schedules, risks, and specs Trim the fat from common development inefficiencies Apply process improvement methods—without being an inflexible fanatic Drive your own successful, satisfying career Don't be a dictator—develop and manage a thriving team! Companion Web site includes: Agile process documents Checklists, templates, and other resources

From the popular I.M. Wrights Hard Code column at Microsoft, this book presents a series of thematically-arranged essays. It features provocative insights about development processes that can spark the imaginationand help simulate productivity.

Blend the art of innovation with the rigor of engineering Great technology alone is rarely sufficient to ensure a product’s success. Scenario-Focused Engineering is a customer-centric, iterative approach used to design and deliver the seamless experiences and emotional engagement customers demand in new products. In this book, you’ll discover the proven practices and lessons learned from real-world implementations of this approach, including why delight matters, what it means to be customer-focused, and how to iterate effectively using the Fast Feedback Cycle. In an engineering environment traditionally rooted in strong analytics, the ideas and practices for Scenario-Focused Engineering may seem counter-intuitive. Learn how to change your team’s mindset from deciding what a product, service, or device will do and solving technical problems to discovering and building what customers actually want. Improve the methods and mindsets you use to: Select a target customer to maximize carryover Discover your customer’s unarticulated needs Use storytelling to align your team and partners Mitigate tunnel vision to generate more innovative ideas Use experimentation to fail fast and learn Solicit early and ongoing feedback Iterate using a funnel-shaped approach Manage your projects around end-to-end experiences Build a team culture that puts the customer first

Chapter 5. Knowing What to Comment; What NOT to Comment; Don't Comment Just for the Sake of Commenting; Don't Comment Bad Names--Fix the Names Instead; Recording Your Thoughts; Include "Director Commentary"; Comment the Flaws in Your Code; Comment on Your Constants; Put Yourself in the Reader's Shoes; Anticipating Likely Questions; Advertising Likely Pitfalls; "Big Picture" Comments; Summary Comments; Final Thoughts--Getting Over Writer's Block; Summary; Chapter 6. Making Comments Precise and Compact; Keep Comments Compact; Avoid Ambiguous Pronouns; Polish Sloppy Sentences.

It may surprise you to learn that Microsoft employs as many software testers as developers. Less surprising is the emphasis the company places on the testing discipline—and its role in managing quality across a diverse, 150+ product portfolio. This book—written by three of Microsoft’s most prominent test professionals—shares the best practices, tools, and systems used by the company’s 9,000-strong corps of testers. Learn how your colleagues at Microsoft design and manage testing, their approach to training and career development, and what challenges they see ahead. Most important, you’ll get practical insights you can apply for better results in your organization. Discover how to: Design effective tests and run them throughout the product lifecycle Minimize cost and risk with functional tests, and know when to apply structural techniques Measure code complexity to identify bugs and potential maintenance issues Use models to generate test cases, surface unexpected application behavior, and manage risk Know when to employ automated tests, design them for long-term use, and plug into an automation infrastructure Review the hallmarks of great testers—and the tools they use to run tests, probe systems, and track progress efficiently Explore the challenges of testing services vs. shrink-wrapped software

Teach yourself SQL Server 2008—one step at a time. Get the practical guidance you need to build database solutions that solve real-world business problems. Learn to integrate SQL Server data in your applications, write queries, develop reports, and employ powerful business intelligence systems. Discover how to: Install and work with core components and tools Create tables and index structures Manipulate and retrieve data Secure, manage, back up, and recover databases Apply tuning plus optimization techniques to generate high-performing database applications Optimize availability through clustering, database mirroring, and log shipping Tap business intelligence tools—Reporting, Analysis, and Integration Services CD features: Practice exercises and code samples Fully searchable eBook For customers who purchase an ebook version of this title, instructions for downloading the CD files can be found in the ebook.

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions