I recently ran into a permission error when trying to access a table in a schema on Supabase:

Error 42501: "Permission denied for [TABLENAME]"

Resulting in a 403 Forbidden error.

After some troubleshooting, I found that granting access to specific tables in the schema solved the issue. I'm sharing my solution here in case it helps you too!

A Funny Yet Familiar Story​

I was once in a technical interview with a senior Java developer who shared a hilarious yet painfully relatable experience. At his company, developers weren't confined to just one or two languages; they had to jump between different languages depending on the project. One day, after a code review, a senior Go developer told him:

"You code Go as if you were coding Java." 😅

Oof. That hit hard. But it's also a perfect illustration of why languages aren't interchangeable.

Java is a powerful programming languages, widely used in enterprise applications, and large-scale systems. Yet, is not known for being beginner-friendly, until JBang comes to the rescue. Let's discuss the Love-Hate relationship with Java and how to make it easier to learn and use.

Sometimes, you may accidentally commit sensitive information like passwords or API keys to your Git repository. If the sensitive information is in a file like .env, you should remove it from the commit history to prevent it from being exposed. Oh, my... I have been there before. 😰

AI is reshaping the developer landscape, and Java refuses to be left behind. With the introduction of Model Context Protocol (MCP) into Java, thanks to the Quarkus framework, developers can now build AI-powered applications with minimal effort. As Max Andersen brilliantly put it in the Quarkus Insights video: "If AI doesn't come to Java, Java goes to AI."

Setting Bold Goals for 2025: My Journey of Growth and Knowledge Sharing​

I've never aimed to be the smartest person in the room. I'm not a genius by any means and I don't have all the answers, but I'm always driven to push boundaries and solve problems that excite me. Recently, my blog has reached the top 3 search results for Kubernetes in airgap environments; a big win for me, because it means people are finding value in what I'm sharing. But, of course, I'm aiming even higher for that number one spot!

Not all developers solve problems the same way. Some build features that are "nice to have," while others address urgent, pressing issues. The difference? They're either a "Vitamin Developer" or a "Painkiller Developer."

In the startups world, the term "painkiller" is often used to describe a product or service that solves a pressing problem for customers, it is expected to be a must-have in order to solve a pain point, while a "vitamin" is a product or service that is nice to have, but not essential, as an example, a painkiller would be a CRM system for a sales team, while a vitamin would be a team chat tool. It's something they need, not just something they want. Taking this analogy further, I think that in the tech world, the same concept applies to developers, but we need both types if we want to build a successful team less reactive and more proactive.

I'm excited to share some great news with you all; my blog has made it to the top 3 for Kubernetes in airgap environments. For those unfamiliar, airgap environments are places where there's no direct access to the internet or public registries. This poses unique challenges, especially when deploying and managing Kubernetes clusters. Seeing my work recognized for such a critical subject is incredibly rewarding, but I'm not stopping here. I'm aiming for the top spot! 🎯

From time to time, we run into issues that seem trivial but can be quite frustrating, when VS Code doesn't open from WSL, it can be one of those issues and it happens after a Windows update or a VS Code update. Here's how to fix it.

I recently ran into an issue where I couldn't open Visual Studio Code from WSL. I would get the following error:

$ code .
/c/Users/adria/AppData/Local/Programs/Microsoft VS Code/bin/code: 61: /c/Users/adria/AppData/Local/Programs/Microsoft VS Code/Code.exe: Exec format error

Read on to learn how to fix this issue.

A slight pivot in the airgap bundler tool MVP to add SBOMs.

This weekend has been a breakthrough—not necessarily in pushing my tools forward for the community, but in expanding my knowledge. I discovered Refine, and it is honestly a game changer (for a backend developer like me). It lets me scaffold React projects with a robust, reusable architecture, perfect for developers and solopreneurs. Instead of wasting time reinventing the wheel, you get a clean structure right from the start. Combine this with Docusaurus in a mono-repo setup, and you've got limitless potential. The combination of these two can redefine how we manage documentation and dashboards in our projects.

That said, I'm going to dedicate another weekend (and nights) to improving the airgap bundler MVP or SABOR (flavor in Spanish, Software Airgap Bill of Materials Resolver) as I like to call it (check the demo video below 👇🏻). I have decided to pivot slightly, the community has given great feedback so far, but after thinking it through, I realized tools like Skopeo and Crane might already be top choices for many. And while the CLI MVP has gotten positive reception, we all know the problem with CLI tools—they are great until you're swimming in flags and options that are impossible to remember.