joe-stanton

Heads up, your DNS is still broken! Will try emailing you a little later...

Red Badger | London, UK | Full Stack Engineer Mid&Senior | Onsite | Full Time

Independent digital consultancy known for delivery and digital transformation working on enterprise scale web applications.

We love: React/Native, Javascript, Node, Java, Ruby (more tech here: https://red-badger.com/technology)

We are on the hunt for a friendly new badger who enjoys complex problems, talking to clients and a working on a tight knit team.

X Functional teams including, Delivery and Tech Lead, Engineers, Product & UX Design and Test.

For more details please visit... https://red-badger.com/jobs?hn

Please email Laura Hasting, Community Manager if you have questions: laura.hasting@red-badger.com We also organise React London, We Love_Tech and UXD Exchange

Beforehand I built something very similar to what you described for Flow (https://hackernoon.com/runtime-introspection-of-flow-types-d...).

Many others superseded this implementation, the above being one example.

You might be interested in this: https://github.com/gcanti/io-ts and many related projects by Giulio.

This is a really useful article. It's a shame that so much development time is wasted on large numbers of fruitless optimisations just because they are "easy" (eg. tweaking the colour of a CTA).

That being said, I'm surprised many of the results are so negative. It would be great to also see the max uplift achieved for each category. A number of retailers I've worked with have been able to beat these uplifts by quite a bit. I wonder if it might be significantly skewed by the kind of clients Qubit has?

Visa/Mastercard may well be forced to try something like this in order to survive. Banks are opening up their own API's for P2P payments (at least within the EU due to legislation). This could completely negate the need for intermediate "payment networks" (except the following).

However - I don't think you'll see a proliferation of new payment methods. The biggest problem here would be fraud mitigation, so it'd need to be a payment provider the merchant deems trustworthy enough.

Interesting times ahead. Amex are just doing the bare minimum to keep up here.

This looks good, and is sorely needed.

It seems one of Stripe's biggest risks is the impending PSD2/XS2A changes within the EU/UK. This means banks/merchants/retailers will ditch traditional card networks (and their fees) to instruct P2P payments directly. This probably opens up a host of very effective anti-fraud measures too (eg. 2FA with mobile devices).

I wonder how Stripe will react to this major change in the market?

For example: https://developer.americanexpress.com/products/accept-amex

You're too kind! If I pursue this, I will definitely be in touch.

I've learned a huge amount from screencasts such as destroyallsoftware.com, so I think we can agree to disagree on this point. Additionally, I think the success of Codeschool, Code Academy, Pluralsight etc. show that I'm not really in the minority here.

A number of points you mention are possible topics. Although I can't think of a single situation where "understanding several compilers" would have helped me design/maintain/troubleshoot infrastructure I'm responsible for.

But hey, looks like you're not in my target market, and that's ok!

Wow, thanks for the response Justin. Very useful to get your perspective on this. I have some teaching experience (Code Schools etc.) but this would be my first attempt at screencasting. Very useful to hear some of these issues first hand!

Couldn't this have built upon https://github.com/facebook/css-layout ?

An enormous improvement over the old dev tools! Good work FB team.

Just to throw something useful I found out there, the app 'Dash' for OS X is really great for offline documentation.

http://kapeli.com/dash