This one recruiter keeps calling me and leaving me messages on different phone numbers (mixed landline and mobile phones) and I have to block them all.

How unprofessional of an agency to continue harassing a candidate if they're not interested. I've muted their numbers now.
And this is not about being interested either on their side - I know them. They're full of recruiters whose sole purpose is getting their fat ass promoted by use of candidate database and track record filling. One of them even had the nerve to tell me he got promoted and how wonderful it is.
I think I'm gonna make a request to delete my data.

Can you guys believe this?

Is it just me or is the "pound me too" movement subliminally suggestive?

I don't know whether my keyboard needs cleaning, or I'm developing some sort of dyslexia , because I seem to be skipping letters and short words in my messages, or writing all te letters but in mixed up positions more often lately...

Following some new nextjs tutorial to learn how to efficiently build a web chat app, the guy built it very solid, but is it efficient?

Im having mixed feelings about this approach. The way he did it is, for example when you click on a user (imagine it as a list of users from your contacts), it actually calls a route, which stores that in database, and once its done Then the route triggers lets say socket.io event to notify the frontend to update the UI.

Not only that but each new message that gets sent it actually calls a route which stores that message in database and once that's successful Then it emits a socket.io event to the frontend to fetch that message.

As you can imagine constantly calling routes like this Does induce small delays. Creating conversations, navigating, opening someones profile and especially sending messages, is NOT instantaneous. When you do it theres a small delay, giving the impression as if the app is SO large that it lags

But it doesnt lag, it just needs a few ms to store that in db so it can return the socket.io bidirectional message event. Which does make sense because what if the internet broke and the user immediately gets sent a message, but the message fails to get stored in database? Or db storage gets fucked or something else fails but socket.io works while db doesnt? The data then may be inconsistent. This approach fulfulls the single source of truth principle

So thats why im having mixed feelings about this approach particularly because of small delays. It is not instantaneous like whatsapp discord telegram signal viber etc the input UI freezes until the message is successfully sent

---

Of course this can be a UI/UX decision and can be handled differently even if the backend works like that.

My concern is is this approach valid?

My question is... I had an idea what if i emit socket.io event to send the message while in the background also call the route to store that message in db? This way not only would it work asynchronously but the message gets sent instantaneously, and if the backend fucks up to store it in db then the UI gets updated with message failed to get delivered, switching the socket.io into polling state. Is this a good (proper, efficient, better) way to do it or not?