Hello World: Why I Started This Blog

title: "Hello World: Why I Started This Blog" date: "2024-11-01" description: "Every developer should write. Here's why I finally started, what I plan to write about, and why sharing knowledge matters more than perfection." tags: ["meta", "intro", "blog"] published: true image: ""

After months of thinking "I should start a blog," I finally did it. Not because I have everything figured out — far from it — but because I realized waiting for the perfect moment means never starting.

The imposter syndrome problem

Every developer I know has felt this: "Who am I to write about this? Someone smarter has probably covered it better."

The thing is — your perspective is unique. Your specific combination of experiences, the bugs you've hit, the patterns you've discovered, the way you explain things to yourself — none of that is duplicated anywhere else. Someone out there will benefit from exactly how you explain something.

What this blog is about

I'm a Software Engineer at Protectt.ai, where I work on Android security. Day to day, that means:

• Building and maintaining an Android security SDK that protects apps at runtime
• Writing code obfuscation tooling — renaming, string encryption, control flow obfuscation — using bytecode manipulation
• Working on RASP (Runtime Application Self-Protection): detection and response to tampering, debugging, and hooking attacks
• Building Gradle plugins and IntelliJ plugins that integrate security tooling into developer workflows
• Reading a lot of Smali and modified Dalvik bytecode

Before this, I spent five years at IIITDM Kancheepuram doing a dual-degree B.Tech + M.Tech in Computer Science, where I built everything from Java desktop applications and Spring Boot APIs to Android apps and ML pipelines.

So that's what I'll write about — things I've genuinely built, problems I've actually hit, and lessons that only came from doing the thing and watching it break.

The format

Some posts will be deep technical dives — how a particular obfuscation technique works, why a Gradle plugin DSL decision bit me, what the MediaStore API actually does under the hood. Some will be short project retrospectives. I'm not going to commit to a posting schedule I'll break immediately.

What I will commit to: writing honestly about the actual experience of building software.

fun main() {
    println("Hello, blog!")
    // First post. Took longer than it should have.
    // The second one will be faster.
}

Why you should write too

If you're a developer who hasn't started writing yet, here's the argument:

1. Writing forces clarity. If you can't explain something in writing, you don't fully understand it. The act of writing is the act of thinking. I've realised things were wrong with my own mental models halfway through drafting a post.

2. Your future self will thank you. I've already gone back to notes I wrote about a particularly gnarly bytecode modification problem and found them more useful than anything on Stack Overflow — because they were written by someone who hit exactly my problem.

3. It compounds. One post isn't much. Fifty posts is a body of work. Start now.

4. The bar is lower than you think. People don't need a masterpiece — they need something that helps them solve the problem they're stuck on right now.

So here we go. First post done. Let's see where this goes.