SonarLint vs. Progress Telerik Fiddler

I am a senior software engineer and I have actively made fiddler a requirement for all of our engineers to have on their laptops by default. I have recommended it to all web developers that I have worked with and contractors that I have worked with as it has saved my mental stability on numerous occasions when trying to show people details of various web requests when working on integrations between different systems This is an absolutely fantastic product that I have used in a technical capacity many, many times and I will always suggest it as a tool when someone is debugging specifically but also for initial development to see how the requests are formed and for sharing responses and requests details so that others can recreate the request that you have sent through right down to the smallest detail

• SonarLint highlights all the issues in our codes and also displays the severity of each issue.
• SonarLint also provides suggestions for how to fix those code issues which are highlighted.
• SonarLint starts the processing of the file as soon as it is opened and highlights all the issues which it found.
• When we fix the issue, we don't even need to create a new build or generate fresh code quality report, as soon as we save the file with the changes, it does the processing again and shows the result if the issue is fixed or not.
• SonarLint saves a lot of time and effort by saving us from doing fresh build every time and generating new code quality report every time, thus increasing the efficiency and output which is in return beneficial for the client.

Incentivized

• Sometimes, SonarLint does not highlight the issues in the code correctly.
• The severity of the issues highlighted is according to the default rules set, we should also be given authority to set the severity of the issues.
• The default fixes which SonarLint provides should be more enhanced and there should be more fixes available.
• Sometimes it takes a lot of time for processing of the file when any new file is loaded or changes are saved in a file.

Incentivized

• The display could potentially become a bit more user-friendly over time, it's pretty easy to follow but for example, I always view the raw request/response information by default and this is not the default selection, being able to choose the default selection would be nice
• Clearer information and options to reduce 'noise' when viewing the requests, there are often a lot of background requests being sent on a computer, you can filter to roughly see what you want and filter out things that you don't want but there are different types of requests and I can't see how to filter between those - possibly a feature but could be made easier to use potentially
• Nothing else to put, this is a fantastic product so there isn't much else to suggest at this stage of using it and I have been using fiddler for years now in my role as a software engineer

SonarLint works along with SonarQube

Incentivized

• SonarLint helps in achieving all the business requirements in a more efficient way.
• It reduces the manual and redundant work which we would have to do else every time if we did not use SonarLint.
• SonarLint helps in maintaining code quality, and thus also highlights the loopholes for the cyber attacks and phishing attacks.
• SonarLint makes work easy and helps the developer to invest less time in manual work thereby increasing their capacity to deliver the maximum output to the client.

Incentivized

• Overall this tool has sped up the process of integrating with new systems infinitely
• The cost of fiddler everywhere which is what we use specifically is nothing in comparison to the cost of dev time saved when debugging processes
• Being able to send information around so simply to other support teams to show them what responses we are getting along with the request detail have made communications much quicker and saves a lot of time going back and forth discussing what is being done and what the request is being sent