Daniel Tenner

I've made a timeline with the video of the original world-shattering announcement and demo of Wave at Google IO, and some of the Google Wave related submissions to HN. How pretentious and audacious it seems in retrospect! It’s hard to appreciate all the snarky jokes in the Pissed Off Wave Tutorial, if you don’t remember how, um, over-confident they were when they announced Wave.

Google Wave Developer Preview at Google I/O 2009 (May 28, 2009)

https://www.youtube.com/watch?v=v_UyVmITiYQ

Google Wave Drips With Ambition. A New Communication Platform For A New Web. (May 28, 2009)

https://news.ycombinator.com/item?id=630427

https://techcrunch.com/2009/05/28/google-wave-drips-with-ambition-can-it-fulfill-googles-grand-web-vision/

Google Wave: What Might Email Look Like If It Were Invented Today (May 29, 2009)

https://news.ycombinator.com/item?id=630470

http://radar.oreilly.com/2009/05/google-wave-what-might-email-l.html

What problems does Google Wave solve? (Oct 15, 2009)

https://news.ycombinator.com/item?id=883116

https://danieltenner.com/2009/10/15/0012-google-wave-html/

Google Kills Wave (Aug 4, 2010)

https://news.ycombinator.com/item?id=1575892

https://googleblog.blogspot.com/2010/08/update-on-google-wave.html

What makes Slack so successful whereas Google Wave wasn't? (Oct 10, 2015)

https://www.quora.com/What-makes-Slack-so-successful-whereas-Google-Wave-wasnt?share=1

What in the Hell Was Google Wave Trying to Be Anyway? – Gizmodo UK (May 27,…

It's easier for you. For me the reverse is true.

One reason to avoid hiring people who don't fit the culture is to avoid entryism. If a group allows just anyone to enter, the newcomers may gain power and destroy the original culture. This is particularly true if a culture is significantly outside the norm.

For example, witness Github's transformation from flat hierarchy and meritocracy to traditional corporate hierarchical politics: http://danieltenner.com/2016/02/06/github-the-quiet-death-of-one-mans-dream/

The thing is, I don't feel like I need to actively think about people's feelings to not say "this sucks". I just do it naturally in response to different social contexts.

I don't need to actively suppress negative feelings when people give me factual feedback. It just happens naturally. People are different.

If I'm interpreting your posts right, it sounds like you feel your personality profile should be privileged over others and that all organizations should adapt to suit you (leaving me unable to find a place that suits me). Perhaps I'm wildly misreading you and interpreting differences in mood affiliation for differences in beliefs? Could you clarify what you are advocating for?

Both Chargify and Spreedly require a payment gateway of some sort, no idea about the others.

I believe Chargify only supports Authorize.net currently, and it looks like Spreedly supports a few more.

Authorize.net is only the payment gateway, so you'll need a merchant account as well. A merchant account with a bank is where you have the transaction fee (flat fee per transaction) and discount rate (percentage per transaction). The payment gateway is a monthly fee on top of that ($10 p/month or so), and then you have the fees for the recurring billing service as well (and any special services they require, for instance Chargify requires the customer management part of the Authorize.net API which is another $20 a month or so).

As far as the merchant account goes, start with this blog post: http://danieltenner.com/posts/0006-how-to-get-a-merchant-account.html

This is exactly what I use for http://danieltenner.com (well, almost - I use Webby, not Jekyll). In fact, I've made the source code for that available here, if anyone's interested:

http://github.com/swombat/danieltenner.com

Deploying like this has another advantage: you can deploy to a subdirectory of an existing app. The benefit of that is simple: pagerank transfers better from mysite.com/blog to mysite.com (since they are considered to be the same site) than from blog.mysite.com to mysite.com (since they are considered to be two different sites).

Edit: I should add that there is one disadvantage to this approach. If you have non-technical members on your team, and you want to encourage them to blog as well, making them learn to use Textile formatting and command line tools is not a great encouragement.

They actually were upset. I wrote a comment describing the points of issue, but there is already a concise description here: http://danieltenner.com/posts/0014-learning-from-wakemate.html

They were willing to give a refund for the $5 down-payment, but there was still an overall bitterness. This was a wise move for wakemate, even if there is nothing wrong with providing more than what was promised/planned for an additional fee.

The customers they have now are very early adopters who will be spreading the word and writing reviews. It's essential that they do whatever they can to make positive first impressions.

I recommend that you find an ISO (Independent Sales Organization) [pdf list from visa: http://usa.visa.com/download/merchants/list-of-registered-independent-sales-organizations.pdf] their success (commission) is tied to you - so they're motivated to get you a merchant account.

A while back one of the people on this site wrote a pretty decent guide to getting a merchant account: http://danieltenner.com/posts/0006-how-to-get-a-merchant-account.html

Other than that, MAKE SURE YOU NEGOTIATE or you will more than likely get raped.