Show notes
Panel:
Aimee Knight
Charles Max Wood (DevChat TV)
Christopher Ferdinandi (Boston)
Cory House (Kansas City)
Joe Eames
Special Guests: Nicholas Zakas
In this episode, the panel talks with Nicholas Zakas who writes on his site, Human Who Codes. He is the creator of ESLint, also the author of several books, and he blogs, too. He was employed through Box and today he talks about ESLint in full detail! Check it out!
Show Topics:
0:05 – Advertisement: KENDO UI
Nothing was working and after investigating someone had written a JavaScript code that was using a native code to make an Ajax request. It wasn’t the best practice for the company at the time. For whatever reason the person was unaware of that. When using that native XML...there was a little bit of trickiness to it because it was a wrapper around the...
We used a library to work around those situations and add a line (a Linter) for all JavaScript files. It was a text file and when you tried to render code through the process it would run and run the normal expression and it would fail if any of the...matched.
I am not comfortable using normal expressions to write code for this. You could be matching in side of a string and it’s not a good way to be checking code for problems. I wanted to find a better way.
I went back to look at JSHint and I saw that on their roadmap you could create your own rules, and I thought that’s what we need. Why would I build something new? I didn’t see anything on GitHub and didn’t see the status of that. I wanted to see what the plan was, and they weren’t going to get to it. I said that I really needed this tool and I thought it would be helpful to others, too.
The guest continues to talk about how pluggable ESLint is and the other features of this tool.
Guest goes into what this can teach people.
Do you get the whole team in a room and show them the options or take the best guess and turn it on?
Get Syntax checking and you will se improvements on the number of bugs that are getting out of production. I recommend using the default the ESLint configuration. This has all of the things that we have found that are most likely errors and runtime errors vs. syntax errors. You can go through with those and sometimes it is easier to run that check with...
Using those ESLint rules will clean up a lot of problems that you didn’t know you had with your code. There are too many problems with those rules. I recommend instead of turning them off then put the severity to warning and not error. That is something we started with in the beginning. We turned on as many rules as we could and it drove people crazy. They didn’t feel like when they were committing to a file why should I be...
The idea with the different scenario levels you don’t’ want to turn off rules so people don’t know there is a problem. There can be a rule on so people will know that there is a problem, but...
Doing that alone will give you a lot of benefit in using ESLint. How do you decide as a team on the rules that are maybe not for finding errors but for stylistic in error? Do we use four spaces, semi-colons, etc. To figure that out I am a big component on finding a pre-existing style guide and adapting it. Get everyone to agree.
There is no right or wrong when it comes to stylistic preferences. It really is just getting everyone to do the same thing. I think it was Crawford that said: Whether you drive on the right side of the left side of the road – it doesn’t matter as long as everyone is dong the same thing. I agree with that and it applies to style guides. It can get heated but for the best thing for the team is stick with a guide and work together.
But my favorite rules I tend to lean towards the ones that saved me.
The Guest goes through his favorite rules with ESLint. Check it out!
30:07 – Advertisement – Sentry!
As a pre-commit hook it could be to fix things and part of the built system you wouldn’t want...
People are probably wondering: Why doesn’t ESLint doesn’t fix all the time?
It can be a team decision: do you want to run Fix at the point that the developer is writing the code, do you want to use Fix as running it as a build when you are bundling? It really seems more of a personal preference. I am on the fence about it. Even though I am leaning more towards...
35:20 – Guest: No I don’t. I don’t have anything against Premier but I think Prettier uses a very interesting space.
For myself, and the future, I haven’t been involved with ESLint because I am focusing on my health. I was diagnosed with Lyme Disease and it meant that I needed to focus on my health. That’s why, too, I wasn’t able to join a few years ago. I am doing better but I am a few years away for working fulltime and writing books and blogging, again. The trajectory is upward. I want to stress that you need to take care of yourself.
There is interesting stuff that we are doing and I love it, but make sure you take care of yourself! If you don’t have your health then nothing will really matter. I want to encourage you all to take care of yourselves better. This industry can take a toll on your body b/c it is high-stressed. If you are stressed your immune system will shut down. For a lot of us we are working too much and there isn’t an off-switch. I would like to encourage people to examine their life and their time.
When you take time to turn off your analytic brain, and work on your creative brain then the pathways will connect better.
Please save your money!
Lyme disease is spread through tick bites.
46:45 – Guest: My blog is Human Who Codes.
47:10 – Chuck: Anything people can do to help you? Check out his books you won’t regret it!
47:33 – Guest: Buying books is always helpful. I would say that if you can spend some time contributing to ESLint that is always a great help. Anything you can do to help them will help me. I want to make sure that those folks are happy, healthy and productive. For me, personally, I love when people Tweet at me and say HI! I love hearing other people’s stories of how they have overcome past diseases or illnesses. If you want to send monetary gifts – donate to a wonderful organization that helps children with Lyme disease. I would encourage you to support if you feel inclined.
51:11 – Advertisement – eBook: Get a coder job!
Links:
JavaScript
jQuery
React
Elixir
Elm
Vue
GitHub – Prettier
GitHub – Premier
Lyme Light Foundation
Inclusive Components
ESLint – Disallow Specific Imports
State of JS
Learn JavaScript
Book: Total Recall
Goodbye Redux
YouTube Channel – Sideways
Human Who Codes – Nicholas Zakas
Nicholas’ Books
Nicholas’ Twitter
Nicholas’ GitHub
Nicholas’ LinkedIn
Sponsors:
Kendo UI
Sentry
Cache Fly
Get a Coder Job
Picks:
Aimee
Technical debt
Professional JavaScript for Web Developers
Chris
Inclusive Components Blog
CSS Cascade
JS Jabber - code
Cory
No Restricted Imports
State of JS
Total Recall
Charles
My JavaScript Story
Joe
Thought bubbles...
Goodbye Redux
Sideways Channel
Nicholas
The Brain that Changes Its Self
Ghost Boy
Tip - Turn off your Wi-Fi before Bed

