The pricing is Stripe-like if only handling domestic transactions. If a customer wants to sell internationally too then there is
* 5k setup fee
* 5k annual fee (excluding service tax). Approx $90/yr.
* 2% per transaction
Instamojo provides a nice payment experience too and with a fee of 1.9% per transaction (if you don't use the hosting feature).
Wonder why the more expensive pricing. A simplified per-transaction pricing would be nice to sell internationally. Maybe increase the per-transaction charge for international transactions or add a fee like $0.5 extra.
P.S: I'm not affiliated with Instamojo in anyway. I've been on the hunt for a payment solution recently and settled with Gumroad actually.
Hi, You are right, we want to make the pricing more uniform as we go. But there are some limitations around that we need to solve.
As for instamojo, they have a good product but they are not a payment gateway in the stripe sense, they are more of gumroad. They support specific type of products whose amounts needs to be pre-decided on their platform. While, we support all kinds of online transactions which you can integrate directly on your site.
Ah yes, I was only comparing from a seller's PoV. Most non-ecommerce startups have fixed plans/pricing I guess.
B/w you might want to link to the http://docs.razorpay.com site in the "documentation" link on your homepage. And maybe rename that /documentation url to /faq instead.
In all the excitement, I did forget: Congrats on launching ~!
For people who have negative opinions about this, hold on. There's more to the DigitalLocker than you think. I tried using this the day it launched (a few weeks ago). Here are a few things for people who haven't tried it.
1.) Apart from storing documents, the other important feature is to share documents with entities (seems like both govt and private). Right now in India, for anything new you want to signup for in the offline world, you are usually asked for multiple ID and address proofs. This site has a feature to share stored documents when entities request for it. So you get document requests from entities (just like Facebook friend requests) and you approve them to share the documents required. Way better than having to carry xerox copies to the office of the entity.
2.) It also looks like entities can issue you documents. If implemented, then we wouldn't have to about carrying and safe-guarding physical copies of documents. I have about 20-30 physical documents I need to safe-guard and more than a dozen marks cards from college. Imagine just receiving a notification that the document for your new insurance policy has been received in your digital locker? Ah such minimalistic life.
3.) Love the simple Aadhaar-based login process. That is so layman-friendly. Entered my Aadhaar card number to get an OTP to login. Most Indian govt sites have ridiculous rules about setting passwords - all of which I cannot remember at all. Even worse changing your account email or password on those sites is a nightmare. To change the email address on the Service Tax website, I have to write a paper-based request to the authority.
4.) You can store any document you want to. This isn't limited to government issued IDs. There's an "other" category when uploading.
5.) I've been using Dropbox to store scanned copies of my family's important documents. It has come handy many times. It is the govt offering to digitally store govt-issued documents. Why would I bother about privacy? I'm glad they made this.
6.) About the SSL cert: AFAIK they seem to have broken the site during a recent update. SSL was fine during the launch day. Oh, and when the Indian govt website specifies "beta" version - they literally mean it. And this site isn't as bad as booking a Railway tatkal ticket on IRCTC, for which there are tutorials and videos on how to use the site. I've forgotten my IRCTC username/password again and I've exhausted all mobile numbers in the house to signup for new account. I'll have to get a new sim just to book a railway ticket next time.
Mailed the DigitalLocker team my concerns about the 10mb limit and also offered to send code contributions if it was opensource. I got back a very quick reply:
It is not a open source project, but you can contribute by your valuable suggestions as it is still running in beta Version.
Regarding Storage space we have noted the issue. Inconvenience regretted.
We shall review and resolve the same as soon as possible.
I backed Jeff's A.I book campaigns. But I haven't touched the books yet. I've had the feeling that the very little math I know won't help me through this book.
Can anyone's who has read the books suggest what Math topics are pre-requisites to read the books? (and if possible, the best sources to learn them from)
The best thing about this article is how he breaks down the math. The main idea: slightly tweak an argument to a function to get the output slightly closer to your desired output. He then presents a couple of ways to achieve this...
The thing I like about this series is how accessible it is. Jeff's stated goal is to make the concepts clear for actual humans rather than academics (hence the name of the series).
I've been working my way through the first volume and knowing a bit of algebra has helped immensely. I recommend checking out volume 1 and see where it takes you!
I've been in the same situation as you just 6 months ago. Was switching from freelance-to-fulltime. And blanked out at nearly every interview.
I did get hired in the end. When that was done, I also helped a few friends tweak the interview process at their startups/companies.
Over time, during my job hunt, I had to tweak stuff in order to get results. Basically try and observe what worked. Here's what worked.
* Find places that use your work (apps/libraries/articles)
If you have been writing software for a few years, there's a probability that you've written a few libraries or handy apps or really good blog posts. You can find people who are sharing links to these on Twitter. Checkout their workplace. If they seem interesting, apply. The tech interview will matter less to them because they've seen the value you provide.
* Write good cover letters/mails
Your application is your first point of contact. It has to be short, crisp and make them want to know more about you. My application email is usually just one or two sentences and then 4 links (github, resume, and a couple interesting projects). If you have interesting projects in multiple languages, change them to suit the company you apply to.
* Try to avoid any automated forms to apply to a job
They most likely end up in a blackhole at popular or larger companies. Find a person who works there and send him/her an email.
* Don't panic and take it slow
It took me a couple months to find a place I'll be comfortable at. Offers will come and go. Pick the one you'll be comfortable with.
All the best. There are jobs waiting for you to find them :)
When away from a power socket, I use Safari instead of Chrome. Saves battery a LOT. Was able to run 11" Air with 19 tabs on Safari and with vim (on iTerm). 2hrs later still had 95% battery left.
> When away from a power socket, I use Safari instead of Chrome. Saves battery a LOT.
Were you comparing Safari with 0 extensions vs. Chrome with 0 extensions? Or does each have a different extension load?
I will often fall back to Safari if a page doesn't render properly in Chrome, but that's because I installed a bunch of extensions on Chrome and have consciously left Safari pure as the driven snow. It's a different problem domain, but I know certain extensions can use resources in surprising ways.
It's not just that. I see nearly 2x better battery life using Safari over Chrome on a 15" rMBP, and I have plugins turned off (click to play). It just uses a lot less CPU, full stop. I don't know what the real difference is, but I suspect Safari just does a better job of idling than Chrome does.
My semi-verified guess is that a lot of the difference is CPU usage when two-finger scrolling on large pages. I just tried it on this page with OSX 10.9 and a 15" Mac Pro, monitoring with Activity Monitor and Coconut Battery while bouncing rapidly up and down.
Chrome burns 90% of a CPU on one thread, and another 40% on another. Coconut reports about 32 Watts used. Safari maxes at about 12% plus 8%, and tops at about 15 Watts. Base usage on this machine with the current screen brightness and applications that happen to be open is 10-12 Watts. I get approximately the same results with Incognito mode, which suggests the problem is core Chrome rather than add-ons.
When you click the battery dropdown on the top right, Chrome is consistently listed as an "Apps Using Significant Energy". On previous releases of OS X I also noticed that by default it would use my dedicated GPU at all times, whereas Safari would not (not sure if this is still true).
I found a simple solution to opensource burnout: when someone contacts me about a project and wants to improve it, I give them access to the repo.
I do this when:
* I don't have the time/interest on the project
* The person seems genuinely interested in maintaining it
Most people I've come across in the opensource world are polite. So I just assume that the ones I grant access to repos are nice enough for other people to interact with.
Same here, but I don't even care if the person is interested maintaining it. I have observed twice now that the interest of somebody submitting an almost trivial patch flamed up after I granted push access. The project suddenly got a burst of life again, and commits started to become more and more ambitious.
I am going to try that from now on. Giving people access to repos and then letting them pass on the baton when they are done. That is a very novel idea.
P.S: Yes I upvoted you and I wish I could do it once more :)
Going by my experience, if you are using Websockets, choosing Phoenix would be a really good choice. There's a lot of work that's gone into transport adapters in Phoenix (websockets and recently polling support was also added). @peregrine and @chris_mccord did a lot of work as far as I can recall. I've been noticing that @JoseValim has joined in too.
That said, I would love some websockets stuff refactored out of Phoenix into a Plug so that it can be used even without Phoenix. I'm not sure about the amount of work that would require.
Being able to use all of erlang's inbuilt modules and functions are an advantage. But there's way more to Elixir that just syntax.
1.) Elixir ships with a build tool called Mix. Falls back to use rebar for erlang projects. Mix is awesome and IMHO way more stable that rebar (Had problems with erlang libs shipping diff versions of rebar binaries in the git repo itself).
2.) There's a really good package manager - Hex.pm (developed and maintained by Elixir's co-author Eric)
3.) OTP compliant config.
4.) Pipes ~! This for me has been a very useful feature to decongest my code. I'm not sure what project had pipes first (should we credit F# or Unix shell itself?). Having that feature in Elixir is a boon for me.
Finally about Phoenix:
* More mature that most people think. It has a few features that even rails doesn't have (or even cannot handle in real world scenarios). There's support for "transports", which allows people to use polling or websockets and such if your apps need it.
* Phoenix not having an ORM doesn't make a diff. Elixir's core-team develops and maintains Ecto, which is easy to drop it and start using. Ecto still has a long way to go, but for most apps, it is sufficient.
* Authentication? Very simple to write a plug for that and share it across all Elixir frameworks. AFAIK someone wrote plug for OAuth.
>I'm not sure what project had pipes first (should we credit F# or Unix shell itself?)
You'd have to go with unix out of those options, F#'s pipe operator is just flipped function application, and is primarily to make up for the poor type inference F# has. Every functional language has or can easily have a function application operator.
Extendable version manager with plugins for Ruby, Elixir & Erlang. Node.js plugin coming soon.