lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

72
active users

#reactjs

4 posts4 participants1 post today

Happy Monday!

I believe that if you start the week by removing code is a good start of the week!

I learned how to leverage JWT to send encrypted data to the frontend.
And so I stripped down my system of hooks in React and also deleted completely an endpoint in Django that I was using solely to fetch user info.

Even more secure, with less code.

Holy ravioli.

I finally managed to have a working JWT authentication system between Django and React.

Major headache but I did it!

My only compromise (at least what it feels to me as a compromise) is that the SPA is abusing the refresh token to maintain the state of the logged in user, because I'm keeping the access token exclusively in memory.

Over-engineered solution for a simple CRUD app, but I'm learning a lot so I don't care.

How can something like a front end framework like #ReactJS that has supposedly been created to abstract and simplify writing #JavaScript “applications” be so fucking over-engineered and complicated, to the point that it needs dozens of libraries to simplify and abstract itself?

Where does this start to even make sense?

Continued thread

Thinking about this, I believe at least for me, what this course is breaking is the principle of learning new stuff ONLY if and when you need it.

There's no way you're gonna remember all the different React libraries for the rest of your life just by watching a few videos.

When I need to use something, I check it out.

And again, mixing too many different libraries to explain some basic workflow/pattern is particularly bad for a course like this.

Continued thread

An example?

Dealing with token authentication in #ReactJS.

The teacher attached this section to the previous section that was about React Router, by using the same code and expanding on it with the auth system.

Why? It's not a best practice IMO, I don't care about React Router all the times I build an auth system in React, at all!

I'd rather show how to implement token based authentication in a more vanilla React scenario.

And this is just one of the many bad practices in the course!

2/2

In the last few months I've been following this ReactJS course:

udemy.com/course/react-the-com

And I strongly advise against it.

Maybe it's very subjective but I now find that the course just made me waste a lot of time.

Not only is overly verbose and slow while treating the viewer like a dumdum, by repeating the same stuff over and over; but now that I know better, I can see so many pitfalls in the actual structure of the course.

1/2

I need to update my blog, the last two days have been very productive, I almost can't believe it.

I finished the back end API (at least to a functional state with all the basics I need), including all the endpoints and all the scraping functions as async jobs thanks to huey.

I set up the cors headers in Django and started a vite + ReactJS project.

Tested an API call from ReactJS and it works!!

I am now tired, I will post on my blog tomorrow.

🚀 Cinny v4.3 Update! 🚀

We're excited to introduce Cinny v4.3:

✨ New user settings design with Folds system for a cleaner, intuitive experience
🔐 Major security upgrade with vodozemac encryption
📱 Simplified device management with improved verification
💬 Pin messages and bulk import custom emojis & stickers
⚙️ Added developer tools for advanced customization
🌟 Emojiboard now supports emoji spec v15.1.0

Check out the update here: app.cinny.in/

Is there a better way to handle doing something after updating the state with #react `useState`?

Having a useEffect just feels a bit clunky especially when I have multiple states that I need to watch and do something whenever they're updated

Also on that, if useState is asynchronous, why doesn't it return a promise? I'm assuming there's a reason for that

🚨 🚨 🚨

Good Morning #FediHire friends - have a new role for ya!

Looking for a fairly senior frontend-focused #Software Engineer to join a team building a containerization product for the CI/CD pipeline called Dagger.

The role is looking for some fairly specific criteria so here are the key points:

* This role is not a UI Designer position, you must have a strong coding background ( #JavaScript / #TypeScript / #ReactJS preferred) in addition to design chops

* Must have at least some experience with #Golang

* You must have developed frontends for #devtools (the thought behind this requirement is that these tools are designed very differently than a typical B2C site so if you have done something substantially similar, answer yes).

* Americas (somewhere between EST to PST) timezones are required. We can hire in Canada, US, South America, and have hired in Europe before for exceptional candidates.

* We cannot sponsor visas at this time.

* Founder likes to discuss salary specifics on his call (2nd step in the process) but we typically don't lose people due to comp

* I've worked with this company for about 6 months and have only positive things to say about the team and culture

* There's currently a bug in the application coming from the ATS that's making the dropdowns funky. Don't judge me too harshly, I've submitted a ticket :blobfoxcrylaugh:

I'm the #recruiter on the role, so feel free to ask any questions here and I'll either have an answer or go find you one :)

Full JD and application here: grnh.se/a1934cb05us

grnh.seSenior Software Engineer (UI/Frontend Focus)Remote (Americas timezones only)