This is very awesome and super useful! When you rely heavily on Stripe events it can get out of control. Stripe needs a doc with real world scenarios and what events get called. I'm definitely going to try and port this to Python.
I built http://remindeat.com a couple of months ago as an experiment with my girlfriend and seems like people really liked it. I might still build a mobile app for it. I also recently built http://feedleap.com which really launched off by itself with Kippt's popularity.
You can use either your password or your API Token. It only stores your API Token which you can revoke at any time. If a user enters their password, it'll just interchange it for an API Token. You can check this out here https://github.com/jpadilla/feedleap/blob/master/apps/auth/f...
We've been using HipChat at Blimp since the very first day, we've even integrated it as our Support Chat. We are only three at the moment but have paid for up to 4 users. One less thing we have to pay for, and still be able to use such a great product.
This is pretty awesome! Wonder how much time would it take to validate. Last thing I would want is to make that signup process even slower. I guess you could still let the user pass and then run an async task to check "if the domain name exists, ask for MX server list from DNS, and verify that SMPT server will receive a message to that address" and then maybe set a flag somewhere.
Do you use this process for all the client projects you take in? We use an Agile process for internal projects which usually don't have an ending date. When we take in freelance work from clients we end up with a certain ending date, for a certain amount of work and iterations stated before starting the project. Before using this kind of process, projects would end up being longer, we'd end up loosing money, and time for other projects.
Indeed, and that usually becomes a problem at any stage of the project, usually converting it into a longer project, and if you're not careful you will surely loose money and precious time.
The process shown on elweb is just to illustrated the 2-iteration process, not a concrete example on how to make a website, more like an example of using the 2-iteration process on various steps of a project.
They also have a very impressive Jobs page http://www.kickstarter.com/jobs, the last one in the list labeled "It's fun!" has a couple of cool things when you hover over the links.
Flask is so damn awesome! For all those other projects Django seems too big, I use Flask. The hardest thing for me was finding a project structure that worked for me. I still haven't landed one that was "perfect". What project structure/skeletons for Flask apps work for you?
This is something I talk all the time with students that are being taught all the programming classes in college. Most of them know how to program, or at least know the syntax of a language and know basics, but getting to that tipping point of having hacked something up is kinda hard for most people. After you've built that first thing, that isn't the obvious programming exercises found on textbooks, you've passed that tipping point and hacking will then come naturally to you.