I was once presented the following question as a part of a job interview: ‘You have a web page that is running slowly. How do you find out why it’s running slowly.’ I really enjoyed answering this question and have used it myself when conducting interviews. Why do I like it? Firstly it shows how someone approaches a problem and how they can systematically work through it. Secondly there is no single correct answer, but many possible solutions.
HTML tables can be difficult to make responsive so that they work on both desktop and mobile devices. By default if the table is too big for a smaller device it will just extend of the side, and the user has to scroll the whole page:
Using Bootstrap responsive tables help to a certain extent, and they make the whole table scroll, and not the whole page. But the content still disappear off the screen to the right.
On a recent project I wanted my tables row to be clickable, so a user could click on a row and perform a default action. This action could be to edit the details of the row item. For example, if a user wants to edit a row they could the click edit link, but also click anywhere else on the row (except for the other links).
To achieve this I used the following JavaScript (which requires JQuery):
When performing a penetration test on a .Net Core web site to find security vulnerabilities, some common issues may be found that are not handled by the default .Net Core template in Visual Studio. One of the tools I use to carry out penetration tests in the Zed Attack Proxy (ZAP) that is part of Open Web Application Security Project (OWASP).
Below is a list of some of the common alerts that may be flagged by ZAP or similar tools, and how to fix each one in .
Have you ever wanted to know how much disk space your Web App or Service is using in Azure, or wanted a quick way to find out the size of various folders in Azure.