filmov
tv
Practical Debugging at Scale Part 11: can't reproduce bug?
Показать описание
What do you do when "It works on my machine" but it doesn't work on theirs?
What do you do when you can't reproduce bug encountered by your users?
This video is a part of the second module covering debugging theory. Here we discuss the process that we need to follow when running into a bug. Ever spent all night on a bug only to find out it was a "stupid" thing that you missed in the beginning? We all have! There's a systematic process for tracking an issue that reduces the chance of this recurring.
By leveraging these tools and techniques you will gain access to the secret weapon of senior developers and consultants. This will make you a better developer and a happier one. Stop treating debugging like throwing out the garbage and treat it as a skill that you should improve.
In the following modules we cover:
* Debugging Theory - Ever spent all night on a bug only to find out it was a "stupid" thing that you missed in the beginning? We all have! There's a systematic process for tracking an issue that reduces the chance of this recurring.
* Tooling - Is your debugging session limited to the IDE? What do you do when there's a dead end or the problem only happens in the release version of your application? That's where external tooling can take you to the next level as a developer.
* Code - This isn't a course on coding. You should know how to do that before you start. But how do you write code that's easier to debug? Code that fails in predictable ways. Code whose failures are easy to understand and track. Code that doesn't drain your bank account because it overuses cloud resources.
* Kubernetes - Not only is Kubernetes hostile to debugging, it does that on a scale that creates its own set of problems. Add the complexity of production debugging to the mix and we've got a new set of problems.
* Serverless - Kubernetes has an ephemeral state problem, serverless takes that problem to a completely new level.
* Fullstack - As we chase a bug we need to venture outside our comfort zone. To tiers and tools we might not be as comfortable with. In this module we'll discuss debugging the frontend and the database to create a tongs motion around the bug.
* Observability - Production debugging is really about observability. Yet so many of us leave these tools to the DevOps team. In this module we'll cover these tools from a developer perspective.
cant reproduce bug,debugging,course,reproduce bug,debugging in intellij java,debugging in java,debugging javascript,reproduce bug testing,debugging in python,debugging in eclipse java,debugging in visual studio code,debugging in pycharm,debugging in visual studio,reproduce a bug,steps to reproduce a bug in jira,production bug fix,bug in production,bug in production environment,fixing bug in production meme,fixing bug in production
The full course includes more than 5 hours of video material.
00:00 Introduction
00:44 Replicate Environment
01:11 Sometimes it's the User
01:55 Communication
03:04 Commandline Tools
03:35 Containers Help
04:27 Onsite is Essential
04:53 Logging
05:12 Concurrency
05:33 Tracepoints
06:06 Automate
06:25 Longrun
07:11 Be Creative
07:45 Give Up (don't really)
08:19 We can't Always Reproduct
09:12 Case in Point
09:54 Final Word
What do you do when you can't reproduce bug encountered by your users?
This video is a part of the second module covering debugging theory. Here we discuss the process that we need to follow when running into a bug. Ever spent all night on a bug only to find out it was a "stupid" thing that you missed in the beginning? We all have! There's a systematic process for tracking an issue that reduces the chance of this recurring.
By leveraging these tools and techniques you will gain access to the secret weapon of senior developers and consultants. This will make you a better developer and a happier one. Stop treating debugging like throwing out the garbage and treat it as a skill that you should improve.
In the following modules we cover:
* Debugging Theory - Ever spent all night on a bug only to find out it was a "stupid" thing that you missed in the beginning? We all have! There's a systematic process for tracking an issue that reduces the chance of this recurring.
* Tooling - Is your debugging session limited to the IDE? What do you do when there's a dead end or the problem only happens in the release version of your application? That's where external tooling can take you to the next level as a developer.
* Code - This isn't a course on coding. You should know how to do that before you start. But how do you write code that's easier to debug? Code that fails in predictable ways. Code whose failures are easy to understand and track. Code that doesn't drain your bank account because it overuses cloud resources.
* Kubernetes - Not only is Kubernetes hostile to debugging, it does that on a scale that creates its own set of problems. Add the complexity of production debugging to the mix and we've got a new set of problems.
* Serverless - Kubernetes has an ephemeral state problem, serverless takes that problem to a completely new level.
* Fullstack - As we chase a bug we need to venture outside our comfort zone. To tiers and tools we might not be as comfortable with. In this module we'll discuss debugging the frontend and the database to create a tongs motion around the bug.
* Observability - Production debugging is really about observability. Yet so many of us leave these tools to the DevOps team. In this module we'll cover these tools from a developer perspective.
cant reproduce bug,debugging,course,reproduce bug,debugging in intellij java,debugging in java,debugging javascript,reproduce bug testing,debugging in python,debugging in eclipse java,debugging in visual studio code,debugging in pycharm,debugging in visual studio,reproduce a bug,steps to reproduce a bug in jira,production bug fix,bug in production,bug in production environment,fixing bug in production meme,fixing bug in production
The full course includes more than 5 hours of video material.
00:00 Introduction
00:44 Replicate Environment
01:11 Sometimes it's the User
01:55 Communication
03:04 Commandline Tools
03:35 Containers Help
04:27 Onsite is Essential
04:53 Logging
05:12 Concurrency
05:33 Tracepoints
06:06 Automate
06:25 Longrun
07:11 Be Creative
07:45 Give Up (don't really)
08:19 We can't Always Reproduct
09:12 Case in Point
09:54 Final Word
0:06:25
0:08:38
0:13:43
1:05:19
0:11:36
0:13:33
0:15:45
0:10:27
0:58:02
0:06:56
0:07:02
0:08:55
0:11:59
0:09:30
0:05:35
0:11:28
0:09:55
0:06:44
0:07:28
0:05:26
0:09:14
0:05:46
0:10:10
0:08:56