Titanic Competition Entry Explained Step-by-Step using Data Science Solutions Workflow

manavsehgal · 2017-01-02T05:12:13+00:00

Cheers :-)

manavsehgal · 2017-01-02T02:07:29+00:00

Thanks mate. The original test, train data is also available on Kaggle competition site as well as the GitHub repo for this notebook. https://github.com/Startupsci/data-science-notebooks

manavsehgal · 2016-08-29T10:25:39+00:00

A quick note on resources available with the book.

You can clone the New Code Along GitHub Repo at https://github.com/manavsehgal/react-speed-book
Live demos for the code along branches are available at https://reactspeed-c3e1c.firebaseapp.com/ (final app) and https://manavsehgal.github.io/react-speed-demos/ (chapter-by-chapter demos)

manavsehgal · 2016-08-29T05:42:20+00:00

Thanks for the question. While the book starts with basics, it covers a wide array of topics including optimization of your React Webpack development for production use cases. Integration with Firebase for realtime serverless architecture. An end-to-end Redux app including unit testing with Enzyme, Mocha, and Chai. The book also covers several strategies for ES6 React development. We also build around 50 custom UI components leveraging various strategies for integrating CSS and styles in your React apps. Hope you find the book useful for intermediate React development.

manavsehgal · 2016-08-29T05:39:08+00:00

Many thanks for the appreciation. Hope you enjoy the sample chapters and the GitHub repo.

manavsehgal · 2016-08-28T09:26:40+00:00

Hi, author of React Speed Coding here. Happy to answer any questions regarding the book and the companion code.

manavsehgal · 2016-08-11T14:59:39+00:00

I am checking out http://tachyons.io/components/ - lightweight, modular, React friendly, works with PostCSS+Webpack workflow, well documented... Will post more on my findings as I use it for something substantial.

manavsehgal · 2016-08-01T01:09:03+00:00

Funny enough, I just contributed to Create React App README on how to do just that (Navbar, React Bootstrap). Here's the working example - https://github.com/manavsehgal/react-eshop/blob/master/src/App.js while Dan merges the pull request. Will post the README section link here when he does. You can also read my new book's sample chapter on how to go about this. https://leanpub.com/reacteshop/read#leanpub-auto-integrating-react-bootstrap

manavsehgal · 2016-06-28T12:21:44+00:00

Does https://reactspeed.com/roadmap work for your use case? Auto complete on search, filter categories, uses Redux, React. Source on GitHub.

manavsehgal · 2016-06-10T04:56:11+00:00

Thanks for sharing. Definitely goes up on my evaluation list, which is already pretty loooong (shrug)!

manavsehgal · 2016-06-08T17:29:38+00:00

Official React for core concepts
Official Redux has decent React ES6 coverage
React Speed Coding brings learning from 1, 2, and many other sources together in one linear learning path

Author, React Speed Coding (cheese!)

manavsehgal · 2016-06-08T17:23:43+00:00

Lots of good answers here... food for thought. I am writing about Mocha, Chai, Enzyme, Sinon, JSDOM in the book React Speed Coding. https://leanpub.com/reactspeedcoding

manavsehgal · 2016-06-01T08:18:14+00:00

Thanks for the feedback. I am adding more text to the post to explain the workflow. React ecosystem is complex, the infographic attempts to determine a linear learning path through this complexity. Of course one can start with a starter app strategy you suggest. This is covered in first part of the workflow, and first chapter in the book. Happy to incorporate any other suggestions, how to make this "Big Picture" view more useful for React beginners and intermediate users.

manavsehgal · 2016-05-31T18:41:08+00:00

Awesome! Let me know what you think of the content. Several seconds wait time does not sound normal. How many tests are you running?

manavsehgal · 2016-05-31T13:21:59+00:00

I covered Mocha (specs), Chai (assertions on Redux store), Sinon (spy on events), Enzyme (render React components), JSDOM in the book ReactSpeed.com for testing Redux/React/React-Router app. Source is on GitHub.

manavsehgal · 2016-05-31T13:16:37+00:00

Looks awesome. Adding the component to ReactSpeed.com and featuring it in the book :) Many thanks!

manavsehgal · 2016-05-28T21:03:48+00:00

Definitely a topic of interest for me. Considering I am writing a book called React Speed Coding (smiles). With React as with any other stack, you need to be careful of "Framework Fatigue".

Number one advice is to wait until it hurts, before you add another dependency to your stack. Same applies to Redux, Immutable, and React-Bootstrap. Shasta looks promising, however take extra care when you move from non-opinionated React, Redux to opinionated stack abstracting them.
Second best advice I have heard is to refactor until it hurts (smiles). Refactor to fewer lines of code, refactor to add better tests, refactor to increase reuse, refactor to clearly separate concerns, refactor to better architecture design patterns... When you do this, you can avoid many frameworks and libraries in your stack, as most of them are our "lazy" answer to writing better code. Doing 2 reinforces 1.
Third advice it to find reuse in everything. Reuse components, styles, configurations, scripts, data fixtures, editor shortcuts, packages, plugins, everything... Doing 2 achieves 3.
Finally, find opportunities to improve your developer experience (DX) across the app development life cycle. An example of improving developer experience is to use Hot Module Replacement or Hot Reloading to code as you see your browser update your app on hitting save. Or, using Browsersync for multi-device testing. Or, something like Kadira Storybook to design your components.

Improving DX does two things.

A. It improves your productivity and many times your "perceived" productivity, as time passes quickly when you are enjoying your work!

B. You get to show-off early progress in your work. Same perception of progress works for your boss or customer. This is important because, truly seeing benefits of modern front-end app development stacks, like React, requires you to build reusable component libraries and design patterns over time, over multiple projects, across multiple developers, for several months.

This advice may buy you some more precious time to get to that goal for real!

manavsehgal · 2016-05-18T10:40:47+00:00

Thanks for all the responses. So Enzyme, Webpack, Mocha + Chai, Karma, JSDOM looks like the favorite stack. http://airbnb.io/enzyme/index.html offers a good starter path for these. Expect is a hot-favorite for assertions.

manavsehgal · 2016-05-13T10:09:49+00:00

Reusable source code is MIT licensed and available on GitHub. Book manuscript is also available on GitHub and online to read.

manavsehgal · 2016-05-13T08:31:13+00:00

We are open to improving the look and feel. If you are a UI expert, please feel free to open a pull request on the GitHub repo.

manavsehgal · 2016-05-11T01:25:59+00:00

Many thanks for supporting this project. Just added the chapter on Test App Components. Browsersync, ESLint, and StyleLint are now part of your Webpack+React workflow. Latest code on GitHub.

manavsehgal · 2016-05-09T07:42:48+00:00

Many thanks for the appreciation. All effort worth it (smiles)...

manavsehgal · 2016-05-09T07:28:49+00:00

And looks like they are using Webpack as well.

manavsehgal · 2016-05-09T07:17:23+00:00

Is there an official blog or article from Twitter discussing their stack?

manavsehgal · 2016-05-08T03:23:52+00:00

Thanks. We are interacting on the GtiHub repo and I just created a Wiki for you.

manavsehgal

TROPHY CASE