/Recent content on BlogHugo -- gohugo.ioenTue, 02 Jun 2020 00:00:00 +0000/post/ip/Tue, 02 Jun 2020 00:00:00 +0000/post/ip/<p>In the previous <a href="./post/networks">post</a>, we introduced the concept of computer networks. In this post, we will go a little further and introduce the Internet Protocol (IP).</p>/post/networks/Wed, 27 May 2020 00:00:00 +0000/post/networks/<p>Networks are part of the foundation upon which the internet is built. A computer network is a set of computers that are connected together, enabling them to share resources. These connections can be both wired, or wireless (Think ethernet cable or Wi-Fi as an example). Each device on the network is called a node. A simple example of a computer network could be your home Wi-Fi, with your laptop, phone, smart watch, printer and tablet as the devices that are connected together. The internet is built upon sharing information. Networks allow us to share data across the internet - emails, phone calls, video, etc. It also allows us to share files and applications and allows everybody to access the world wide web.</p>/post/sre/Fri, 22 May 2020 11:36:33 +0800/post/sre/<p>As the first post, I thought it would be a good idea to talk about what SRE is and we do as SREs. So, what is SRE? The cliche answer is that SRE, or Site Reliability Enginering, is <em>what happens when a software engineer is tasked with what used to be called operations</em>^{<a href="./post/sre/#notes">1</a>}. This makes sense to only a few people, and instead raises even more questions for the rest. To me, being a SRE means being the gatekeeper of production systems an applications, with the main goal of making systems reliable. This encompasses a large number of things, such as instrumenting monitoring to measure performance, designing systems that scale over time, using automation to prevent toil and much more.</p>/about/Mon, 01 Jan 0001 00:00:00 +0000/about/<p>Hello everyone and welcome to my site!</p>