Eve is a senior developer advocate at Progress and is enthralled in everything to do with web debugging and the world of network traffic. When not writing content or streaming, you can find her at your favorite developer events.
When it comes to how you approach web debugging, there are valuable techniques you can take advantage of, yet first you need a guide to help you uncover them. You’ve come to the right place and your resident Telerik Ninja Robert Boedigheimer recorded a video titled, “Expert Network Debugging Techniques You Won't Find Elsewhere.”
When it comes to evaluating website performance techniques, you can use Fiddler Everywhere for the job. Our Fiddler Everywhere Ninja, Robert Boedigheimer shares in this video how he responds when asked to give an opinion on how to improve a website’s performance. Here is the transcript of the video that walks you through Robert’s process, techniques, and tooling.
Let’s cover what a bug report is and its purpose. Bug reports are where support engineers and developers outline errors and end-user encounters. It includes the steps to reproduce this issue, details on the troubleshooting effort, and specific documentation on how to resolve it.
When you work on a support team, collecting end-user details takes most of your time. Imagine you could change how much time you spend communicating back and forth and put an end to video chats because you have a troubleshooting solution that does all that for you.
We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here.
Thank you for your continued interest in Progress. Based on either your previous activity on our websites or our ongoing relationship, we will keep you updated on our products, solutions, services, company news and events. If you decide that you want to be removed from our mailing lists at any time, you can change your contact preferences by clicking here.