Building a Developer Cult

Post by fomine3 » Wed, Jul 22, 2020, 12:14 AM UTC

dmitriid wrote: post #106

fogetti wrote: post #104

Earlier quoted context omitted.

This is seriously lacking in terms of what's available on the market in Japan now. No support for point payments (like RakutenEdy payment), neither Linepay, Rakupay, Merpay, Paypay and other QR payment providers, nor Suica or Pasmo pay, and this is still just the tip of the iceberg what's available in Japan and missing in Adyen (Nanaco, Waon, dPay, auPay, etc). Just saying, before you drink too much of that kool-aid.…

Yeah, and how many payment providers provide all that and all the rest that Adyen provides? I'm drinking Adyen kool-aid because I worked for a company that needed payment methods in Japan, and in India, and in Korea, and in Latin America, and in Europe. Adyen provides all that. Yes, they will not have 100% of local providers, but it's still 100% better than any competition.

GMO PG is famous option for EC but more enterprisey. https://www.gmo-pg.com/en/service/mulpay/

Post by SifJar » Wed, Jul 22, 2020, 6:28 AM UTC

AlexMoffat wrote: post #108

SifJar wrote: post #100

Earlier quoted context omitted.

Additionally, think about why they're asking for a certain thing, and whether their request is really the best way to solve the underlying problem they want solved

“Treat your users as you would a class of pre-school children. If they’re all screaming for a snack you don’t necessarily give them one, perhaps a healthy lunch would be better for the underlying need.”

I don't think pre-school children are the only people who are poor at recognising or expressing what they really want, I think that's a fairly universal thing. It's very easy to get an idea about what the solution should be & make a request based on that rather than basing the request on the problem you're facing.

A good analogy I heard recently (more to do with planning your own projects than requesting stuff in other people's, but I think it still works): imagine you have a large patch of grass and it is taking too long to cut. There are a couple of ways to define that problem:

* I need a better lawnmower

* I need a better way to cut grass

The first locks you in to a particular solution (lawnmower), but there may be a better possible solution out there, and the second statement opens it up a bit. So bringing that back to the user request thing, if your user requests a better lawnmower, make sure there isn't some better way to have the grass cut instead.

Re: Building a Developer Cult

Re: Building a Developer Cult