DEV Community: Francisco Juan

Athenas — My Meeting Assistant

Francisco Juan — Thu, 11 Jun 2026 19:06:41 +0000

Hey everyone,

I’m stopping by mostly to share something I built that has been helping me a lot in my day-to-day work.

I created Athenas. I’m not a huge fan of calling it a SaaS, so I’ll just call it a system.

The idea came from a very simple problem that I imagine many of you have faced as well: I would leave meetings and often couldn't remember everything that had been discussed, decided, agreed upon, or questioned. It's not always possible to take notes on everything, and it's not always easy to stay fully engaged while writing at the same time. In the end, a lot of valuable information gets lost.

So I decided to build a tool to help solve that problem.

Athenas listens to your meetings directly through your browser, transcribes the conversation in real time, and then organizes everything into something much more useful once the meeting ends.

Today, it can:

Transcribe meetings in real time
Generate a summary at the end
Show who participated and what was discussed
Extract action items and tasks
Highlight discussion topics
Identify decisions that were made
Surface unanswered questions
Generate a mind map of the meeting
Provide a chat interface so you can quickly ask questions about what happened during the meeting

During the meeting, you can also enable live insights if you'd like additional support while the conversation is happening.

One important detail: it runs locally in your browser. It's not one of those bots that joins meetings on your behalf. The goal was to keep the experience simple, lightweight, and natural to use.

It's not "the next Facebook" or some revolutionary invention, but it's a tool that has genuinely helped me over the past few weeks. Since it solved a real problem for me, I thought it was worth sharing because it might be useful to others as well.

At the moment, the platform is completely free because I'm still in the validation phase—trying to understand how it performs in real-world use, collecting feedback, and testing it with other companies in my region.

So if you find it interesting and would like to give it a try, I would be extremely grateful.

Right now, feedback is worth its weight in gold to me.

If you use it and have any comments, criticism, suggestions, or ideas, please don't hesitate to reach out. My contact information is available on the platform, and you can also contact me through comments here, LinkedIn, direct messages, email, WhatsApp, phone calls—whatever is easiest for you.

If you'd like to try it out, you can access it here:

https://athenas.juansev.dev

Thanks, everyone.

[Boost]

Francisco Juan — Mon, 26 Jan 2026 01:06:06 +0000

Why NaN !== NaN Makes Perfect Sense (I Promise)

Sylwia Laskowska ・ Jan 25

#javascript #node #frontend

npm vs npx: whats the difference?

Francisco Juan — Mon, 26 Jan 2026 00:48:09 +0000

Hello there!

If you are starting on Node.js ecossistem its very usually confusing with the differences understanding npm and npx. What do they? What the diffence? Where do they live?

npm

The npm is the package manager of node, (Node Package Manager).

You use npm maining for install dependences and run scripts of project, those one writed into manifest package.json

What is a manifest?

For example:

npm install react # Installing a normal package
npm install -D eslint # Installing a developer package
npm run dev # Running a dev script from `package.json`

In the end, the npm do this sequence:

download the package
add it into node_modules
register into package.json

npx

The npx was made for execution of packages, with no need of a global installation.

Examples:

npx create-react-app my-app
npx eslint .
npx prisma migrate dev

For curious devs, you already must seen the .bin folder into node_modules, if you open that, you can see the execution binaries of your package, usually it be of packages that you can run on your CLI.

On running npx, it:

use local version of package (if it exists)
or download the package temporarily, execute, and discard

It's like, getting of example create-react-app, the npx download temporarily the create-react-app package, runs it, without installing global avoiding the risks of conflicts with other global versions.

Now, when you run inside of your working directory, and you already have this package installed into your project scope, the npx only runs it, like the prisma and eslint into examples.

Difference in the practice

npm → install and manage dependences
npx → run package binary

A simple rule to remember is:

npm install and npx runs

Since npx, make no sense install tools globally.

If this post help you, tell us more examples, your uses, etc.

very thank you!

a main()

npm vs npx: qual a diferença?

Francisco Juan — Mon, 26 Jan 2026 00:23:02 +0000

Se você está começando no ecossistema do Node.js, é bem comum confundir e nem entender o npm e npx. O que eles fazem? Qual a diferença? Onde moram? De que vivem?

npm

O npm é o gerenciador de pacotes do node, (Node Package Manager).

Você usa o npm principalmente para instalar dependências e rodar scripts do projeto, aqueles scripts declarados no manifesto package.json.

For example:

npm install react # Instalando um package normal
npm install -D eslint # Instalando um package de desenvolvimento
npm run dev # Rodando o script dev declarado no package.json

No fim do dia, o npm faz essa sequência:

baixa os pacotes
adiciona ao node_modules
registra no package.json

npx

O npx serve para executar pacotes, sem ter que instalar globalmente.

Exemplos:

npx create-react-app meu-app
npx eslint .
npx prisma migrate dev

O npx:

usa a versão local do pacote (se existir)
ou baixa temporariamente, executa e descarta

É como se, pegando como exemplo o create-react-app, ele baixasse temporáriamente o pacote create-react-app, e o executasse, sem ter que instalar globalmente e correr riscos de conflitos de versões posteriormente.

Já quando você chama ele dentro do seu working directory, e você já tem esse pacote instalado localmente no escopo do projeto, ele apenas executa ele, como eh o caso do prisma e do eslint dos exemplos.

Diferença na prática

npm → instalar e gerenciar dependências
npx → executar comandos de pacotes

Uma regra simples de lembrar:

npm instala, npx executa

Desde o npx, quase não faz mais sentido instalar ferramentas globalmente.

Se esse post te ajudou, deixa um comentário ou complementa com mais exemplos, valeuzasso!