I just did a cmd + shift + F6 on this newsletter. Meaning that I renamed it. It's only the name for now, perhaps at some point I'll create a separate brand for it, but for now it lives on my website.
I feel like giving the project a name makes it easier to share and brings more momentum to it.
The name I chose for the AI Frontend Architecture Newsletter is:
“”Layered
To me, this name represents what this newsletter is truly about: meaningful and deep conversations about technology, specifically the frontend ecosystem.
It's a multifaceted newsletter, hence "Layered" fits perfectly.
I want to put into simple language (as simple as I can), complex technical concepts that can help you build projects that last.
To gain this depth, we need to go layer by layer, getting to the most essential aspect of a problem to find solutions at their core, where they are more powerful.
Anyway, what do you think of the name?
#Past
With this new name, I want to share about the journey so far, where I am, and what's to come.
I've released 14 issues without missing a beat, ranging from Use Case-based architecture to creating high-quality agentic skills. You can see the full list in the archive.
I need to say I am proud of the achieved quality.
They all are hand-crafted, which means I write them myself, from scratch. All of them. I review them later for grammatical errors or expressions that can be reworded with AI, but that's it. I dare to follow my own AI policy.
And I do this on purpose, I could probably create a ton of issues like this, leveraging Claude Skills and N8N, but... What would be the point?
I want a space where you, the reader, can connect with me and the ideas that I share.
“”If a machine is behind an idea, do you value it the same?
#Present
I am now working at full capacity on multiple projects, leveraging the use of AI in Frontend Architecture and in Product Development. I've never been this productive.
I recently developed from scratch a course platform for my brother’s website, using HydrogenOpen in a new tab and ShopifyOpen in a new tab with MDXOpen in a new tab for highly interactive lessons.
Pretty neat.
If I were to host courses, I would follow the same approach.
You can check his latest course hereOpen in a new tab. We are launching today.
I've been also working on creating the website and Notion system for Adriana (my girlfriend) for her new business about Cellular Integrative Health, called Mind Your CellsOpen in a new tab.
I've had some chronic back pain issues (as many of you!) and she single-handedly was able to find the root cause and fix it for good. So I'm her number one fan.
I've recently started a full-time collaboration for a dream client. I can't share many details, but let me just say that as a freelancer, your network is of the utmost importance.
This year I've also been selected to speak at some of the most important conferences in Spain:
- Codemotion
- CommitConf
- React Alicante
And some international ones as well!
- JSNation
- React Summit
I have some discounts for tickets for JSNation and React Summit. HereOpen in a new tab and hereOpen in a new tab.
The main talk that I've proposed was how to create a newsletter with React. Yes, I was selected to speak about how I created this very same newsletter.
You can see the interactive slides hereOpen in a new tab.
So... Loads of projects and business opportunities.
However, to me, crafting the newsletter is essential.
It is a profound space that forces me to be meaningful and share treasured learnings.
With that in mind, let's talk about what's coming.
#Future
The future of the Layered Newsletter (it does have a nice ring to it, right?) is like an emerging architecture. I know the foundations are all about deep and meaningful conversations, so the next natural question is... What should be those conversations?
AI is changing how we code.
I'm a firm believer that the architectural knowledge I share is more relevant than ever. I know it because I see how my clients suffer without robust foundations.
I would like to help more people, which means slightly shifting the language to be more AI-oriented, while keeping the underlying focus on robust, scalable systems.
That means that even though you might see more issues regarding AI, the focus remains the same.
I want to ask you what kind of ideas you want more of:
P.S.: Back in Madrid after a month in a Coliving called RooralOpen in a new tab.