Carles Muiños

Frontend developer with a taste for design. Proud citizen of Vue land. Jamstack early player. Former backend coder. Curiosity 80 - 20 Serendipity

[Carles Muiños @xarlee_dev]

@TheAhmadOsman StarBook Horizon

[Carles Muiños @xarlee_dev]

@witcheer Out of curiosity, how would you do it with https://t.co/iW7FuG8BsU?

[Carles Muiños @xarlee_dev]

@HermesWatcher Both

[Carles Muiños @xarlee_dev]

@NousResearch Would be nice to have PearPass integration... https://t.co/isluT2caAR

[Antonio Lupetti @antoniolupetti]

Over the last few months, Algebrica has reached a much wider audience than I ever expected. Some posts shared on X received millions of views, bringing many new readers to the project. The decision to make the content openly available on GitHub also led to valuable feedback and appreciation, something that means a great deal to me.

Over the past three years, I have written around 230 entries. In the context of the web this may not seem like a large number, but for a project built entirely by hand it represents a substantial amount of work. Every page is researched, written, revised, illustrated, and maintained individually. My goal has never been to publish content as quickly as possible, but to produce explanations that are accurate, complete, and supported by diagrams that are both useful and visually clear.

For this reason, before expanding the knowledge base further, I decided to undertake a comprehensive revision of the existing material. The objective is to improve consistency, correct mistakes, refine explanations, and raise the project's overall quality. At the moment, I am approximately halfway through this process.

If everything proceeds as planned, I expect to complete most of the revision work by the end of the summer and then return to focusing on new topics and new entries.

Thank you to everyone who has shared comments, suggestions, corrections, and words of encouragement. They help me understand that Algebrica provides value to its readers and can become an increasingly useful resource for students, teachers, and anyone interested in mathematics.

#Mathematics #Math #MathEducation #STEM #OpenSource #GitHub

[Antonio Lupetti @antoniolupetti]

"Algebrica" is a free, open, and distributed mathematical knowledge base.

Since its earliest conception, I never wanted to include advertising or transform it into a click-driven platform. The goal has always been to build a rigorous, accessible, and independent space for mathematical knowledge.

Over the last few months, the project has grown significantly, thanks in part to several posts shared here on X that unexpectedly reached millions of people worldwide.

To continue growing Algebrica and progressively transform it from a personal project into a global mathematical resource, I now need your help. For this reason, I decided to launch a series of periodic fundraising campaigns.

The first one is called "The First Twenty".

The idea is simple: find the first twenty people willing to support the long-term development of Algebrica and help build an independent, ad-free mathematical infrastructure for the web.

The first supporters will appear on the Founding Supporters page with their photo and personal profile or website:

https://t.co/skqeS84FTR

No aggressive fundraising, no paywalls, no exclusive content. Just people helping sustain open knowledge together.

Thank you to everyone who has supported, shared, read, or simply spent time on Algebrica so far. It genuinely means a lot.

[Harminder Virk @AmanVirk1]

Can we tell every burnt-out JavaScript developer how much fun it is to use AdonisJS?

[Antonio Lupetti @antoniolupetti]

After the unexpected growth of the past few days, driven by the strong visibility Algebrica received on X, with over 220,000 views, I decided to follow one of the most common suggestions I received.

“Why not make the site collaborative?”

It is something I had already considered in the past but I have always been cautious. Allowing open, unsupervised contributions risks making the content less coherent, less consistent, and less aligned with the unified voice I am trying to build over time. At the same time, it is also true that more minds can lead to better outcomes. For this reason, I decided to move forward step by step.

Starting today, a new Community section is available, where users can suggest edits or additions directly within individual sections of the entries. This feature will not be enabled on all pages at once, but will be rolled out progressively. This approach preserves accuracy, avoids fragmentation, and allows focused work on a limited number of topics at a time, making the process more effective.

Contributions are intentionally constrained: short, targeted edits of up to 850 characters, and always subject to review before publication. The goal is simple: improve the content without losing its identity. Thank you to everyone who has shown interest in these past days and to those who will contribute to making Algebrica an even stronger, free, and open resource.

[Carles Muiños @xarlee_dev]

@antoniolupetti Amazing work, one that will last the years to come. I only wish someone from the Atmosphere (ATprotocol) help you make Algebraica an Open Social knowledge base. That would be awesome.

https://t.co/jas9UAa4ER

[Carles Muiños @xarlee_dev]

@dok2001 Kudos!! Cannot feel more excited!! Looking forward to starting to play with it! Go @astrodotbuild!

[Carles Muiños @xarlee_dev]

@rumgewieselt About "Separation of Concerns" broken. This is from 2017 and more people should have read it back in the day:
https://t.co/rG5BrBy9OS

[Carles Muiños @xarlee_dev]

#n26 do not sleep on this...

[Albert Cuesta Zaragosí @albertcuesta]

El neobanc @Revolut busca traductor al català.

Pot ser només per al programari dels caixers que està instal·lant a Barcelona, però també per a la seva web i aplis mòbils.

En qualsevol cas, bona notícia.

/via @martibrav0 @maxkarpis

@digitalencatala
https://t.co/XAbQS7jvoo

[Carles Muiños @xarlee_dev]

@kodykendall @obie @garrytan Aren't you sleeping on @adonisframework? JS convention over configuration...

[Carles Muiños @xarlee_dev]

@rough__sea I never heard a mathematician giving up on crafting their thing only because calculators and computers were far more powerful. Writing code, building software is a human thing, it would not make sense handing it over to AIs and start forgetting what once was such an amazing craft

[Carles Muiños @xarlee_dev]

This 👇🏻💯

[Addy Osmani @addyosmani]

Vibe-coding is not the same as AI-Assisted engineering.

A recent Reddit post described how a FAANG team uses AI and it sparked an important conversation about semantics: "vibe coding" and professional "AI-assisted engineering". While the post was framed as an example of the former, the process it detailed - complete with technical design documents, stringent code reviews, and test-driven development - is a clear example of the latter imo.

This distinction is critical because conflating the two risks both devaluing the discipline of engineering and giving newcomers a dangerously incomplete picture of what it takes to build robust, production-ready software.

As a reminder: "vibe coding" is about fully giving in to the creative flow with an AI (high-level prompting), essentially forgetting the code exists. It involves accepting AI suggestions without deep review and focusing on rapid, iterative experimentation, making it ideal for prototypes, MVPs, learning, and what Karpathy calls "throwaway weekend projects." This approach is a powerful way for developers to build intuition and for beginners to flatten the steep learning curve of programming. It prioritizes speed and exploration over the correctness and maintainability required for professional applications.

There is a spectrum between vibe coding and doing it with a little more planning, spec-driven development, including enough context etc and what is AI-assisted engineering across the software development lifecycle.

In stark contrast to the post, the process described in the Reddit post is a methodical integration of AI into a mature software development lifecycle. This is "AI-assisted engineering," where AI acts as a powerful collaborator, not a replacement for engineering principles. In this model, developers use AI as a "force multiplier" to handle tasks like generating boilerplate code or writing initial test cases, but always within a structured framework.

Crucially, the big difference here is the human engineer remains firmly in control, responsible for the architecture, reviewing and understanding every line of AI-generated code, and ensuring the final product is secure, scalable, and maintainable. The 30% increase in development speed mentioned in the post is a result of augmenting a solid process, not abandoning it.

For engineers, labeling disciplined, AI-augmented workflows as "vibe coding" misrepresents the skill and rigor involved. For those new to the field, it creates the false and risky impression that one can simply prompt their way to a viable product without understanding the underlying code or engineering fundamentals.

If you're looking to do this right, start with a solid design, subject everything to rigorous human review, and treat AI as an incredibly powerful tool in your engineering toolkit - not as a magic wand that replaces the craft itself.

[Carles Muiños @xarlee_dev]

@Bundle_it_app If it is as good as it sounds, please take my money asap. I need to stop struggling with my digital diogenes syndrome and take back some mental space. May it be my best companion in the near future? Looking forward to it!! #Bundle

[Carles Muiños @xarlee_dev]

@Bundle_it_app Looking forward to it!! Take my money!!

[Carles Muiños @xarlee_dev]

@Bundle_it_app Too many in-memory things floating around. Cannot wait!!

#WenRelease

[Carles Muiños @xarlee_dev]

@AmanVirk1 Awesome! You rock man!

@adonisframework is so cool ⚡

[Carles Muiños @xarlee_dev]

@astrodotbuild server islands deployed on @fleek_net , how cool is that?! 👋🏻

[Astro @astrodotbuild]

[3/3] Server Islands