shady_trails's comments

I am happy to see they pulled this magnitude of investment. Curious why? There are exactly two possibilities:

1. The product is developed and released in a few years, its amazing, and everyone is happy.

2. It sucks, investors lose their money.

#1 is a win for me, #2 is a who cares.

I've been using Quiver for the last year as a means of writing programming tutorials for beginners. Fantastic product.

I usually save the notebooks I create onto google drive, which gives me the ability to easily open each notebook on other machines. Poor man's sync.

As someone who makes heavy use of redux-rx[1], this looks fantastic. While using Redux, one of the greatest productivity gains I encountered was moving more parts of my application to frp. In particular, I've found that reflecting portions of my apps state in the URL was challenging with vanilla redux + redux-router, as I had many actions that relied upon componentWillMount and componentWillUpdate watching the url for changes.

Fastflux looks like a step in the right direction towards the promised land of of a functional-oriented UI written with javascript.

1: https://github.com/acdlite/redux-rx

That is hurtful to say. While the two products are in a similar space, neither can claim to have a monopoly on internet-based tech education. Project-based learning like this is a goldmine for anyone looking to get into web dev. It makes sense to have a wide range of providers of such training.

You have an interesting opinion. Coffeescript has, for several years now, encompassed nearly the entire API surface of ES2015.

  * Comprehensions (more flexible with Coffeescript).  Wait, that's ES7 now.
  * Template strings
  * For .. Of loops
  * Destructing
  * Classes. ES2015 has an awful implementation of this, without allowing an syntax for binding methods.  Also enforces the somewhat arbitrary requirement of function properties only, as opposed to any type I choose.  Don't forget, mixins with Coffeescript classes is a breeze, but no support with ES2015.
  * Arrow functions.  Unnecessary syntax with ES2015 (the parens even without arguments), not to mention confusing implicit return.
  * Generators with ES2105.  If you find a use for these in front end web dev I'll buy you a beer.

ES2015 does succeed in introducing an entire set of confusing ideas: we rolled for years with var's, but now I get my hand held with const and let, because figuring out how var works (or just relying on Coffeescript to handle it for you) is too challenging.

The point here is that it is frustrating to see people jump on the ES2015 bandwagon when Coffeescript has had the same feature set for years. It suffered adoption because of developers who didn't want to learn `another` language. I have met a tremendous quantity of developers - myself included - who initially rebelled against the use of Coffeescript, only to eventually fall in love with it.

Continuing work on an online course on React JS, found here: https://www.udemy.com/learn-and-understand-reactjs/?couponCo....

I had some challenges with the course at the started, but refocused my efforts in making sure I was creating a product that a beginning developer could work through and then feel confident to build their own apps. Once the quality content was in place, reviews, revenue, and engagement soared.

Revenue is up over the last two months, and I plan to write a blog post in the next few weeks regarding that topic. In addition, I plan to also release a new course covering React Native in the next week.

Its an easy question to deflect.

- "I don't feel comfortable sharing that" - "I'm still looking at a couple different options and don't want to pigeon hole myself" - "What salary is being offered with this position?"

If they take issue with your non-response, its a (small) sign that you might headed towards a non-ideal working environment.