Debug, create clean code, restructure, learn to fix bugs and understand this code, and you will surely become the developer of tomorrow.

The ability to create projects has become much more important.

To train yourself mlv.sh/ai !

NO they should no longer spend 100 hours coding an app from scratch without AI.

I know what it is: I did it and it's really annoying.

Don't do that.

Use AI.

Let it make mistakes.

Then it changed... because the calculator became a commodity almost impossible to ban (thanks phones)

AI will follow the same path.

It's seen as a cheat code.

When it will become a commodity.

YES developers must learn to "think without AI"

The market has no more borders.

A dev in Paris can work for a US company.

A dev in Berlin can charge in dollars.

A dev in Lisbon can earn an SF salary.

The question is no longer "why are we paid less"

It's "why do we still accept it"

We solve the same problems.

We use the same tech.

But we're paid a fraction of the price.

Why?

Because "it's the European market".

Because "the cost of living is different".

Because "that's just how it is".

Except now, with remote...

DHH (creator of Ruby on Rails) just posted a tweet about this.

1.5 million views.

He says: "When I see the salaries of devs in Europe, I have to look twice.
It's hard to believe we work in the same industry."

And he's right.

We write the same code.

Une IA ne sera jamais capable de faire tout ça sans humain.

Mais un bon développeur peut réaliser tout ça... en quelques heures... comme moi !

Si tu veux booster ta carrière : mlv.sh/ai ! (nouveaux prompts et cours)

TOUT le code a été fait par l'IA.

Mais je l'ai supervisé...

J'ai fait les bons choix techniques...

J'ai comparé...

J'ai testé...

Et c'est uniquement pour cette raison que j'ai réussi à déployer et à faire tout fonctionner (du deuxième coup, au début les events étaient dupliqués).

Créer une queue. J'ai utilisé une stream Redis afin de passer de :

AVANT :
20 000 emails = 20 000 events = 20 000 connexions

MAINTENANT :
20 000 emails = 20 000 events stockés dans une queue = ~20 connexions (1/1000 events)

Pour résoudre ce problème :

• doit être stocké
• va trigger des webhooks qui vont refaire des calls
• chaque ouverture va trigger la création d'un event

Résultat ?

Ma database complètement down quand j'envoie des campagnes car je dépasse la limite de connexions à cause des events, etc...

Solution ?

Et depuis que j'ai commencé mon projet Lumail.io, j'ai été choqué par la complexité grandissante d'un outil d'envoi d'email.

Imagine...

Mon SaaS peut envoyer des campagnes d'email, par exemple 20 000 emails.

Chaque email :

• doit être envoyé au rythme maximum de 40 emails/seconde

I thought about it every day.

And as soon as I earned €10,000 I left.

Since then I've spent 1 month in Europe in 3 years.

I have my buddies, my girlfriend, my house, my scooter and everything I need to have an insane life.

So here's a little glimpse of my life:

I had trouble believing that it was possible for a government to forbid me from doing anything for several months.

And there I see and hear people in Bali, in Thailand who have almost no rules.

Who live the dream life.

And I tell myself: I want exactly this life.