About Me

Who I Am

I'm A.M. Rinas — a Full-Stack Software Engineer and DevOps professional based in Sri Lanka. I work at Wincore Solutions as a Full Stack Software Engineer, where I build and maintain production-grade web applications, automate infrastructure, and push the boundaries of what small engineering teams can deliver.

My engineering journey started with a fascination for how software systems work under the hood — not just what they do on the surface, but how they communicate, fail, recover, and scale. That curiosity hasn't gone away. It drives the work I do every day and the articles I publish on this blog.

My Professional Background

I hold a degree in Computer Science and have been working in software engineering professionally for over two years. During that time, I've worked across the full stack — from designing REST APIs in Java Spring Boot and Python Flask, to building React and Next.js frontends, to containerising and deploying services with Docker and Kubernetes on cloud platforms.

At Wincore Solutions, my day-to-day work covers:

Technical Skills and Stack

Over the years I've built up a broad and deep toolkit. Here is an honest breakdown of where I spend most of my time:

Languages

Infrastructure and DevOps

Databases

Testing and Quality

Certifications

I hold 25+ certifications across a range of disciplines. Some of the most relevant include:

I pursue certifications not to collect badges but to fill specific gaps — when I encounter a technology at work that I don't yet understand deeply enough, I find a structured course and work through it systematically.

Open Source and Side Projects

Outside of work I maintain a handful of projects on GitHub. These include tooling scripts for Linux server automation, a codelab collection of solved programming exercises, and small full-stack applications I use to experiment with new frameworks before adopting them in production.

I'm also active on Medium and previously maintained a QA-focused blog at QA Mastery, where I published testing guides before moving to rinas.tech as a unified home for all my technical writing.

Why I Write This Blog

Every article on this blog started as a problem I actually hit in production or while learning something new. The debugging session that took three hours. The configuration change that fixed a cryptic SSL error. The command that finally made a Docker networking issue make sense.

I write them up for two reasons. First, writing forces me to understand the problem completely — I can't hand-wave a vague fix in prose the way I can quietly move on from one in a terminal window. Second, these exact problems are the ones other developers search for at 11 PM when a deployment is broken and Stack Overflow doesn't have a clean answer. If one of these articles saves someone an hour, that's enough.

I make a deliberate choice to include real terminal output, real error messages, and real code from actual projects — not sanitised pseudo-examples. That's what makes a technical article genuinely useful versus one that looks complete but doesn't actually help.

What I'm Currently Learning

Right now I'm deepening my knowledge in:

Get in Touch

I'm always open to interesting conversations, technical questions, or collaboration opportunities. The best ways to reach me are via LinkedIn, email at hello@rinas.tech, or through the Contact page.