Week 9

While documentation may be one of the most preached practices for network and computer techs alike, it also seems to be one of the most neglected. Techs often forget to write documentation at all or write objectively bad documentation with not enough information to help the next guy.

I have started trying to get better at this myself and have taken to writing notes whenever I come across a problem I’ve never seen before and am working on creating documentation for well established processes that have never been documented, or have changed since the last documentation.

We have also implemented a new ticketing software that allows you to write internal notes and such on tickets which can be useful to refer to in the future.

Comments

Post a Comment

Popular posts from this blog

Week 1

Image
Hello everyone, my name is Ryan Bryngelson. I am enrolled in the BSIT220 course at Bellevue University and throughout the course, I will be posting to this blog weekly to share some of my findings of the IT world as it relates to networking. To share a little about me, I don’t quite know the reason it started but I have shown an interest in anything electrical basically since the day I was born. Some of my earliest memories include being fascinated with the light above our apartment door when I was 1-2 years old and taking apart the family computer when I was 12. As I recognize some of your names from my other classes this semester and I’ve already told these stories there I’ll spare them here for your sake. I don’t have much experience with the advanced networking skills that I would like to build, but my current home network setup should hopefully allow me to experiment with any topics I learn about in this class. It consists of a 1 gig link to our ISP handled by a Unifi Dream ...
Read more

Week 6

The instructions for the blog post say not to just copy discussion posts over, but we’ve only talked about one thing this week: IPv6 addresses, and the incredibly large number of addresses created with 2^128 bits is very fascinating to me so I’m doing it anyway! (Though with a few different examples than the discussion post). IPv4 addresses use 2^32 bits to store the information which gives you a little over 4 billion addresses. Since a billion in and of itself can be quite difficult to comprehend, let’s talk about a billion dollars for a second. If you made $100 a minute ($6000/hr) every day of your life, that would equate to $144,000 a day. Even with 4x my annual salary in a single day, it would take you 19 years to get up to just one billion dollars. Expanding on that, we can determine that it would take you 81.7 years to reach the amount of IPv4 addresses we have available. (On a side note, how much is Elon musk making to be evaluated at almost 400 billion dollars? With your *pat...
Read more

Week 5

Image
This week I would like to discuss the hosts file that used to be the directory for the entire internet.   Back when the internet was just a baby, the ‘hosts’ file was a file placed on every computer that was connected to the internet that had a list of IP addresses and friendly names for all other computers also connected to the internet. Every day at 2 AM, this list would be updated with any new computers that had been added. Of course, this system quickly became unsustainable and had to be replaced with a new system which later became known as DNS. Interestingly, this hosts file still exists on all computers today, and still works just as it always had, albeit you (or your system administrator) are now the people in charge of maintaining the list. One use for the hosts file that I have found recently is the Remote Desktop Connection app used within Pro versions of Windows. I’m not sure when the setting became a thing, but on the ‘Advanced’ tab on the connection dialog box is ...
Read more