I have been using Redux Auth Wrapper as of late, which lets you wrap a route in a function that will allow you to check for an authenticated state. Below is an example and you can dig through the repo. In my store.js file, I have the following, which looks for a user object on the authReducer. export const userIsAuthenticated = userAuthWrapper({ authSelector: state => state.authReducer.user, redirectAction: routerActions.replace, failureRedirectPath: '/login', wrapperDisplayName: 'userIsAuthenticated', }); I use this along with react router to protect certain routes: Non authenticated route: <Route path="/events/:eventId" component={Pages.EventPage} /> Authenticated route: <Route path="/create-event" component={userIsAuthenticated(Pages.CreateEventPage)} />

Awesome, template strings ftw. Thanks so much for sharing this.

Occasionally, I get a really good question. Usually this involves creating a sample application, or UI. I generally like these. Now, there are about a thousand questions that have been super silly and a waste of time. I find that most of the time, these questions take you so far out of your element that they are useless. The best interviews I have ever had went something like this: Interviewer: "Hey, you don't need to do a technical interview because I reviewed your code and it rocks" Me: "Cool!"

Oh yeah! Great question! I am using Elm, Elixir and Haskell currently on the weekends, plus a bit of Python for a Machine learning project. I think it's super important to go outside of your comfort zone; that's how you grow!

While I am wholeheartedly on board with React, Redux and GraphQL, I think the most important thing to learn is JavaScript, which is no easy task, especially with ES2015 being such an enormous update. Once you know the language inside and out, learning nearly any framework or library is very easy. Beyond that, like I said, React, Redux and GraphQL are all amazing cutting edge technologies that are a blast to work with.

I would add that there is a fantastic video series and book by Kyle Simpson that goes over the then vs. now of asynchronous abstractions in JavaScript. Beyond Promises, we have actually two more asynchronous constructs that have been introduced in the newer releases of JavaScript: Generator Functions and Async Await. Note: Generator functions have already been finalized in the ECMA standard while Async Await will be in the next release, but both can be used right now with Babel, Traceur, or any other transpiler.

Hi @misterhtmlcss I want to ask for clarification? I am not sure I totally understand the reasoning why you won't be using hashnode? Honestly, when I first came here I noticed something was missing that I couldn't put my fingers on. since then, I have started to come here every once in a while and I hope that the site will continue to improve because in theory it's a great idea and the UI is really nice.

I do not and never really did use jQuery. I am, however, joyfully using React. Beyond frameworks / libraries, I see ES2015 onwards as being a complete game changer! I can definitely see why jQuery was needed, but I no longer see much need for it. If React ceased to exist, I would replicate something similar to it myself.

I really like using the Hindley Millner Function Signature pattern, which is a byproduct of the functional programming culture. Your comments end up succinctly representing the flow of data through the functional units of your app. Take for example the below function that takes an array of functions and returns a single function: // compose :: [Func] -> Func const compose = (funcs) => { // Code here return megaFunction; }; You can read more about it here: https://en.wikipedia.org/wiki/Hindley%E2%80%93Milner_type_system and here http://dev.stephendiehl.com/fun/006_hindley_milner.html Beyond the above mentioned strategy, I tend to follow the pattern of whatever documentation generator I use. It depends on the language, for example, you can use YardDoc to self-document Ruby code that can be automatically parsed into a static documentation website. You can try searching on google for "Generate documentation from comments in (Insert language here)". You should be able to find a guide that you can follow to create self-documenting code.

Hi Marcus, It's quite easy. Just add three back ticks before and after your code. You can read more about markdown here: https://guides.github.com/features/mastering-markdown/