I enjoy sharing my knowledge and ideas with people around the world. In addition to providing software engineering, infrastructure administration, and cybersecurity services, I also write articles in my spare time. These articles mainly cover software, infrastructure, cybersecurity, experiences I have had with people, and my thoughts on various topics.
This research highlights a troubling pattern I repeatedly encounter while assessing real-world web applications in Sri Lanka: security is often treated as an afterthought. Based on manual security assessments of 22 websites, this article examines the vulnerabilities I discovered, why they existed, how organizations responded, and what those findings reveal about the current state of application…
Modern technologies solve specific problems, but using them outside their intended purpose often creates new ones. In this real-world case study, I'll show how a well-built application became less secure because its developer treated WebAssembly as a security mechanism. The issue wasn't the technology itself, but forgetting fundamental security principles while overengineering the solution.
The most important part of a website's lifecycle is probably the development skills, with infrastructure skills coming second. I often come across websites built with poor development practices that are easy to hack. Seeing this so often has frustrated me and inspired me to write this article. So without wasting any more time, let's get straight to the point.
In a previous article, I discussed shared hosting. In this one, I'll be experimenting with a shared hosting server. My goal is to highlight a vulnerability and help you approach certain aspects from a different perspective. Let's get started!
In a previous article, I provided a low-level overview of DNS servers. While it wasn't an exhaustive guide, it covered the fundamentals to help you understand how DNS works. In this article, I'll build on that foundation with real-world examples. Let's dive in!
Most developers have a high-level understanding of DNS. However, for web developers, grasping DNS at a low level is crucial. Writing yet another article explaining DNS from a high-level perspective would be redundant. Instead, this article delves into the DNS protocol and its inner workings at a low level, offering a system administrator's perspective. Let's dive in.
This isn't just another article explaining shared hosting. Instead, I'll break it down from a system administrator's perspective—why you should never use shared hosting, even for a small web application, and what better alternatives exist. If you're looking for affordable hosting solutions, this will be a comprehensive guide, much like my previous article on web development. Let's dive in!
In a previous article, I provided a high-level overview of HTTP. In this article, I will dive into the low-level implementation of HTTP, covering topics such as creating HTTP servers and even lower-level TCP servers. Discussions on HTTP and TCP clients will be reserved for a separate article. Expect plenty of code examples. So, let's get started.
There are countless articles and videos on the internet explaining what HTTP is. If I were to write this post in the same way, it would just be another one among many. Instead, I'll be breaking down HTTP from the perspective of a back-end engineer, highlighting common issues developers face with it. Let's dive in.
I come across numerous web development groups on Facebook every day. These groups are filled with people—some searching for web developers at low prices, while others are offering their services for equally low rates. This obsession with cheap work has distorted the true value of web development in recent years. The reality is, web development is not cheap at all.
I have upgraded the Laravel framework to version 12, made significant improvements to the front-end design, and added service pages to the website. This means I am now officially offering my services as a freelancer. Read below to learn more about these updates.