Probably start off with a base of nextjs. Server side rendering No need to write server files (unless you need to) No webpack setup (unless you want too) Routing out of the box Speedy start to the dev cycle

Maybe don't add them too your skillset but add them as a challenge in your individual project overview.

Developers are in such high demand in Amsterdam and having skills in react and node there are very few hoops I would jump thought to get a job as a developer.

Single Responsibility Principle After writing some spaghetti javascript a colleague of mine with waaaay more experience than me explained the idea that each function should have a single simple job.

@Matt Storm a good indication is stars on github (community interest) angular is about half of what vue and react are at even with its 1-2 year head start

IMO you can't beat a good morning stand-up with your team and a cup of coffee, or help a Jr out with a small problem, or team up for some pair programming, or read the physical kanban board if you are remote. Of course remote a couple of days a week might be fine if you don't need to meet clients for meetings. But full time remote is not practical if you have a team bigger than 3.

Long and descriptive. Eg toggleMainProfileMenu () This makes sure everyone on the team knows what an action is supposed to do.

Velocity js for animations Immutable js to work with redux Helmet js to change header meta tags in react Thats all I can think of right now.

A react app without state seems feesable if you map state with something else like redux. Currently working on a site and haven't used this.state at all. Redux maps everything and if i have to change it i disbatch an action. If i need its values I mapStateToProps.

Get a t-shirt with WiFi and connect it to the stack overflow api to show your score. That would be sick.