This space is my wisdom blog: I don't claim to have it all. Instead, I'm writing down what I learn with every project. Every entry will essentially be an honest summary of stumbles, discoveries, and tools I'm finally starting to understand.

Project 1: Blurgy

🌍 Try the live extension: Visit the official project website and try it at alejandroramirezj.github.io/Blurgy

Blurgy was my first Chrome extension. The idea was simple in my head and got complicated as soon as I touched real code: permissions, the manifest, the popup, the content script, publishing something another human can install without breaking their browser… All that was Blurgy.co and the ecosystem around the project.

I wrestled a lot with Cursor (yes, that; if you use it heavily, you know the pain; if not, imagine the part of the flow that makes you sweat at 3 AM).

At first, I created a monster: something that half-worked, grew in all directions, and was hard for even me to explain. Then I kept editing with Cursor without being entirely sure what each piece did. I made many mistakes and many inefficiencies — unnecessary refactors, blind testing, copied solutions that didn't fit. But it was also a lot of fun: seeing the monster slowly respond and starting to read errors with less panic.

Core Takeaways from Blurgy

Read the documentation before adding another wild dependency.
Version and test on a clean Chrome profile before claiming victory.
Small steps: one change that compiles, one flow that makes sense, then move to the next.
The real wisdom here isn't "never fail," but documenting the failure so it's not repeated in vain.

If you're reading this in the future: the next project will have its own entry and its own organized chaos. Thanks for joining the experiment.

🦔Article

·🗓️2026-03-28·🕒~2 min read

Blurgy: My First Project

Blurgy was my first Chrome extension and the start of Blurgy.co: messy, great learning, and a monster I eventually tamed with Cursor.

#Projects #Chrome #Learning

Project 1: Blurgy

🌍 Try the live extension: Visit the official project website and try it at alejandroramirezj.github.io/Blurgy

I wrestled a lot with Cursor (yes, that; if you use it heavily, you know the pain; if not, imagine the part of the flow that makes you sweat at 3 AM).

Core Takeaways from Blurgy

Read the documentation before adding another wild dependency.
Version and test on a clean Chrome profile before claiming victory.
Small steps: one change that compiles, one flow that makes sense, then move to the next.
The real wisdom here isn't "never fail," but documenting the failure so it's not repeated in vain.

If you're reading this in the future: the next project will have its own entry and its own organized chaos. Thanks for joining the experiment.

Project 1: Blurgy

🌍 Try the live extension: Visit the official project website and try it at alejandroramirezj.github.io/Blurgy

I wrestled a lot with Cursor (yes, that; if you use it heavily, you know the pain; if not, imagine the part of the flow that makes you sweat at 3 AM).

Core Takeaways from Blurgy

Read the documentation before adding another wild dependency.
Version and test on a clean Chrome profile before claiming victory.
Small steps: one change that compiles, one flow that makes sense, then move to the next.
The real wisdom here isn't "never fail," but documenting the failure so it's not repeated in vain.

If you're reading this in the future: the next project will have its own entry and its own organized chaos. Thanks for joining the experiment.