Having a different internet browser makes handy for people whose job is to make sure any web service or application, and their behavior, would not fail before and after making any changes, or upgrade. In our definition, it is that it would not fail regardless of methods, not the geeky ones and without harm of course, applied to access, in a regular way, a resource designed and made available to the public. We think that premise, which is to "make sure it will work, somehow a little better", characteristic of our work @𝖎𝖈𝖑𝖆𝖘𝖘𝖊𝖉, is true to any technology designed for use mainstream but which this post is toned or using such example, specifically. Do you know what causes a browser to process a web service or application like this in the image? We would see it is due to an HSTS, primarily, not being processed or some bug prevented to load by, in here we have, Microsoft Edge Dev browser where a notice is produced. Then it could be that, with other browsers, this is not at
IT documents comes with different names such as the following:
- Manual or handbook,
- Policies and procedures,
- Management systems,
- Project plans.
In the real world we have various names with unique descriptions and purposes when in fact they could be made to do a uniform direction for which actions are based for the entire IT initiatives, probably the longest in IT lifecycle is operation.
The problem is our inclination on something else which is wrong. IT remains an IT area. Business remains a business area.
The same problem is carried out when we conduct IT audit. Most audit are missing the gists in which IT is being used by businesses. We once said that an effective IT audit is conducted by IT people themselves but there is something wrong with that even. Business and accounting people have been doing it with a different bias and preconceived notions which doesn't make the cut for IT direction and audit respectively.
Leaders play the same game and so the problem continues and they are dependent on their technology people to carry out related stuff just like they made their businesspeople do theirs even before technology became the premium facility for doing business.
But the actions are taking technology to make things work and every document created must consider the former always and not the latter. If you've seen the SCF which stands as structure, content and facilities, these has a lot to do with any decent IT work document including any outcome- or case-based education.
Comments