loading...

Don't be one of these React Devs🙄

Rohan Salunke on November 10, 2019

I have been working with React for a couple of years now and I have seen stupid practices that developers do while working on a React App. In this ... [Read Full]
markdown guide
 

Thanks for the article.

Just one small inconsistency. In last group of point you say:

You need to understand that React is a View Library💡.
How you manage your state is none of its concern.

and

Or you can just simply use React hooks and context.

So in one you are stating that React doesn't care and in second that you have build in tools for that.

React was a lib, and React was dedicated only for the view part. Was, not is, now React is a framework, because you can do fully flavored app only using it (lack of routing is not a point against this statement). Also React has own state management tools, and even React team constantly is saying you should use them, and also constantly saying some critic words about Redux and Mobx.

For other points, React is kinda DSL, so learning only it creates DSL programmers, this means that such kind of developer has problems with understanding the language below React - JS, it can have very bad implications. Like not optimal, or just copy/pasted code. Learning JS should be a rule here.

For using React with JQuery, this is a violation of every principle of React. As React is a way to achieve declarative UI. Where data flow is top-down, and DOM is representing the data. JQuery exactly targets DOM and manipulate it directly, so React loose ability to be declarative too, as JQuery plays a role of Trojan horse.

 

Thanks for the comment!
I do agree things are seem a bit contradictory for state handling.
It might also seem like React has became more like a framework. But i'd also like point out the fact that, React doesn't forces you to use its state management tools (like a framework might do). I mean it's there, you can use it, but you are still open to try better solutions.

 
 

I have seen stupid practices that developers do while working on a React App.

This is a highly inappropriate statement.

  1. I encourage you to do some research on what ableist language is and then avoid using ableist terms.

  2. There's no need to demean folks who do any of these things. The DEV community encourages a safe space for learning and this post works against that.

 

First of, apologies if that sounds rude.
"stupid practices" that developers do
I'm pointing the "practices to be stupid", I don't think so I called the folks stupid nor did I meant that.

PS: I might still be wrong here, English is not my first language. Also I hope you're not taking the sentence personally 😅

 

See:

Impact is contextual from person to person. Still feel free to report abuse or reply with a sentence that could be replaced in the article. I'm open to edit the article and replace potentially harmful language.

I've already linked a sentence. Start off by reading about ableist language and then remove it from your article. After that, work on making this article less about insulting to people who may be like these "stereotypes" you've listed and more about teaching people how to become better developers.

I have my trigger words, but saying an act is "stupid" or "foolish" is different when a person directly calls you "stupid." Personally, I would write that something is a "bad practice," but that's just my style. I come from a jQuery and Vanilla JS background, so I appreciate someone guiding my way, even with strong wording. I would think it's insulting to assume that "stupid" should be a trigger word for those who have disabilities. I worked with an programmer who was an amputee who used the word, "lame," although I would never use that word myself around him (and try not to in general). Obviously, he meant it to say something was "foolish." I have children, so I substitute the word "silly" for "stupid," but when I'm speaking with my wife, we use the word "stupid," for example, to describe some kind of harmful or useless policy.

I love this article: skepchick.org/2014/02/insults-slur...

 

I don’t know what would be your native language in which saying that people makes “stupid practices” is not insulting. May I assume calling this article “stupid” doesn’t bother you?

Yes it won't bother me if it was stupid.
Feel free to report abuse if you think this article is stupid.

 

The word "stupid" is completely acceptable and normal people use it quite regularly. Don't let the bullies get you down.

 

Thanks!, I also thought it wasn't such a big deal.

 

To clarify, I don't think using "stupid" in this context was a good idea. It was unnecessarily negative. But don't be shamed about using the word in general. It is not a dirty word or an "ableist" word.

 

There is nothing wrong with trying to avoid writing code, in fact that's pretty healthy. I agree with the rest, although I am not a react dev.

 

No code is the best way to write secure and reliable applications. Write nothing; deploy nowhere.

github.com/kelseyhightower/nocode

 

I am aware of the fantastic work of nocode and vanilla.js, without such effortless work, something would be possible 😂

 
 
 

Now am fully encouraged to learn react. Have been discouraged based on the things have been told about state management e.t.c this post just guide me through.. thanks so much.. #reactweek

 
 
 

Don't be one of these React Devs that call what they don't like "stupid". English language is rich, you could use more appropriate expressions.

 

The article is much based on facts and not my liking, I've also provided necessary arguments regarding what makes it stupid. Stupid is just stupid, will be stupid, no matter who likes it or not its just Stupid!

 
Sloan, the sloth mascot Comment marked as low quality/non-constructive by the community View code of conduct

The one who thinks React is a framework, when it's really a shitty pair of training wheels

code of conduct - report abuse