About Us

Let’s cut the corporate introduction short. I’m Arlina Clay.

For the past 13 years, I’ve lived in the messy, high-pressure reality of production code. I didn’t learn this industry from a polished bootcamp with perfect tutorials; I forged my expertise managing critical data infrastructures at Faster and shipping high-performance web interfaces at Flash Computer.

While most developers eventually pick a side—retreating into the logic of the backend or focusing on the visual flair of the frontend—I chose the harder path. I chose to master the entire stack. MyAngle isn’t about reciting documentation or sharing generic “Hello World” examples. It’s about the hard-earned lessons of what actually works when the server is down, the client is screaming, and the deadlines are yesterday.

The 2 AM Reality Check

It’s 2:43 AM. The coffee in my mug is freezing cold. There’s a distinct hum from my laptop fan that sounds worryingly like a jet engine preparing for takeoff. And I am staring at a semi-colon.

Just one.

It was a race condition I missed on line 402, causing the entire application to throw a tantrum that would make a toddler jealous. You know this feeling, don’t you? If you are here, reading an “About” page on a tech site, you’ve probably felt that specific mix of rage and exhaustion. The screen glare burns your eyes. You question your career choices. You wonder if you should have just opened a bakery instead.

But then you fix it. The error log clears. The script runs. And suddenly, you feel like a god.

That right there? That cycle of struggle and breakthrough? That is my life. I’m Arlina Clay. I’ve been breaking code (and fixing it) for over 13 years. This isn’t just a hobby for me; it’s a lifestyle etched into the dark circles under my eyes. Welcome to Myangle.net.

The “Faster” Years: When Speed Was Just Math

Let’s rewind a bit. My career started at a company ironically named Faster. I spent five years there. You might think a place with a name like that would be chaotic, rushing from one deadline to the next. And sure, we had deadlines. But working as a Database Engineer taught me something that still sticks with me: Speed isn’t magic. It’s math.

People think a fast website happens because you bought a better server or used a trendy framework. Wrong. It happens because someone (me) spent three days staring at a slow SQL query, obsessing over indexes and execution plans.

At Faster, I lived in the backend trenches. I didn’t care what the buttons looked like. I didn’t care about color theory or user flow. I cared about Data Integrity. I cared about Normalization. I honestly hate spaghetti code in databases more than I hate bad traffic. If your schema is messy, your app is doomed. It doesn’t matter how pretty the frontend is if the engine is full of sludge.

That experience hardened me. It taught me that technology isn’t about guessing; it’s about knowing the structural limits of your tools. (And yes, SELECT * is still a crime in my book. Fight me.)

The Shift to “Flash Computer”: Learning to See Pixels

After five years of staring at tables and rows, I needed a change. I needed to see the light. So, I moved to Flash Computer.

Talk about a culture shock. I spent eight years here, transitioning into a full-fledged Web Developer. Suddenly, my clean, logical database world collided with the messy, subjective reality of the frontend. In the database, things are either right or wrong (ACID compliance doesn’t negotiate). In web development? Things are… fuzzy.

I fought with CSS Z-indexes. I battled browser compatibility issues—writing code that looked beautiful on Chrome, while Internet Explorer (may it rest in peace) chewed it up and spat it out. I watched the ecosystem shift from jQuery spaghetti to the component-based architecture of React and Vue.

At Flash, I learned that technical perfection means nothing if the user hates using it. I moved from the engine room to the driver’s seat. I had to learn how a user feels speed. It wasn’t just about milliseconds anymore; it was about perception. Animation timing. Layout shifts. The psychology of a button click.

This was where I really cut my teeth on the Full Stack. I stopped seeing code as just instructions and started seeing it as a Product. A database engineer sees structure; a web dev sees pixels. I had to learn to see both at the same time.

Why “MyAngle”? The Philosophy

So, why build this site? Why add another tech blog to an internet that is already drowning in them?

Here’s the thing. Most tutorials suck.

I’m serious. You Google a problem, you find a solution on StackOverflow or some generic tech site, and you copy-paste it. It works. Great. But do you know why it works? Or more importantly, do you know why it might break six months from now when your traffic spikes?

Technology looks different depending on where you stand. That’s the concept behind MyAngle. I don’t just want to give you the code snippet. I want to show you the perspective.

• Context is Everything: A solution that works for a startup might kill an enterprise app. A quick fix for a hobby blog is a security risk for an e-commerce store.
• The “Why”, Not Just the “How”: If we talk about a WordPress theme, I won’t just tell you how to install it. I’ll explain how the database calls might slow down your site if you use too many plugins.
• Backend Caution + Frontend Creativity: I want to give you the database engineer’s risk-aversion mixed with the web developer’s innovation.

From Indonesia to the World

I write this from Indonesia. We aren’t Silicon Valley. We don’t have endless venture capital flowing like water. What we have is grit.

Here, the internet connection can be… let’s call it “temperamental.” Hardware is expensive. We learn to optimize because we have to. We learn to make heavy software run on older machines. We learn resilience.

That geography shapes my coding style. I don’t like bloat. I don’t like wasted resources. When I write a guide or analyze a piece of tech, I’m looking at it through the lens of efficiency. I believe good code should be accessible, lightweight, and tough. It should work when the network is slow. It should work on a five-year-old phone. That’s the standard I hold myself to, and it’s the standard I bring to this blog.

A Quick Reality Check (The Legal Stuff)

Look, I know my stuff. I’ve been doing this for over a decade. But I am not sitting at your desk. I am not logged into your server.

Technology changes fast. A command that works today might be deprecated tomorrow. A security patch might change how a plugin behaves next week. While I strive for absolute accuracy in everything I write on Myangle.net, you need to be smart. Test everything. Never run a command in production just because a stranger on the internet (even a qualified one like me) told you to. Use a staging environment. Back up your database. Use your head.