خرید و دانلود نسخه کامل کتاب زبان اصلی Foundations of Debugging for Golang PDF | دانلود کتاب خارجی

آنتونی رابینز میگه : من در 40 سالگی به جایی رسیدم که برای رسیدن بهش 82 سال زمان لازمه و این رو مدیون کتاب خواندن زیاد هستم.

 
Book DescriptionDebugging is probably the most important skill that most people are never taught.Being able to debug locally and in production is a critical skill for any Go engineer, but it is rarely taught explicitly. It has taken me many years of working with Go in production to get comfortable debugging, and I want to accelerate your learning by teaching you everything I wish I had known when I started out.In this book you’ll learn:How to get better at spotting issues by eye.Logging patterns and how to build an enterprise logging strategy.What are metrics, how to create them and how to build great dashboards.What distributed tracing is, and how to set it up in your company.How to use Go’s profiling tools to debug performance issues use and squeeze every ounce of performance out of your application.Who’s this book for?This book is aimed at junior and intermediate Go Developers. A working knowledge of Go is assumed.Table of contentsWelcome!What is Debugging and why do we do it?Debugging by eyeA simple exerciseStrategies for effective code inspectionLearning Code patterns and being aware of common errorsError handlingInterfacesConcurrencyStyleguidesAnother ExerciseWrapping upPair ProgrammingWhat is pair programming?The driver & the navigatorSwitching rolesThe power of two mindsAccelerating learning and knowledge transferBuilding rapport & Fostering CommunicationTo pair or not to pair?Tips for being a great driverTips for being a great navigatorPairing remotelyHow I have used pair programming to solve production issuesLogginglogging locally with the fmt packageUpgrading logs with the logs packageSo which should I use for local logging?SlogCreating a logging strategyWhat should I do with all these logs?An exerciseWrapping upThe DebuggerSetting up the debugger in VScodeSetting up the debugger in GolandBreakpointsDebugging panic tracesStepping overStepping intoConditional breakpointsDebugging goroutinesTests as an entry point to debuggingYou try – exerciseMetricsViewing MetricsIntroduction to PromQLUsing metrics to help you debug productionAlertingExerciseA warning on measuring too muchDistributed tracingOpen telemetryAdding traces to a Go APIAdding attributes to spansCapturing errorsTracing between different servicesAutomatic dependency mapsTracing beyond httpWrapping up and a warningProfiling & pprofWhy profile?Adding profiling – the simple wayProfiling without side effectsprofiling the heapCPU profiling and pprof listProfiling goroutine usageExerciseWrapping up – Should I just leave pprof running all the time.Thank you!