As of today we have native support for SVN, Git, and Hg.
We've also open sourced the Ruby API we wrote for Mercuiral: https://github.com/isabanin/mercurial-ruby
Enjoy!
1,563 karma · joined August 15, 2009
We've also open sourced the Ruby API we wrote for Mercuiral: https://github.com/isabanin/mercurial-ruby
Enjoy!
>> It’s not like we were going to put a For Sale sign up. We had active clients who we didn’t want to scare off. We were still actively supporting the product and we also wanted to sell a profitable service, and for that you needed customers.
I've followed the workshop since it's been redesigned, read all of the materials, and am an active reader of the workshop's listserv. I can say with honesty - the experience is transformative and I'm not paid to say that.
I've watched so many "oh, shit, I get it now" moments on that it's inspiring.
Even better, I know this stuff and the students are well versed enough to teach me stuff.
I have lots of biases for Amy since we're friends and collaborators but I can say with confidence: this course is worth 10x what she charges for it.
Keep me posted on progress please - alex@indyhall.org
Thanks!
* $8 themeforest theme + some elbow grease
* Mailchimp
* My existing knowledge of the industry
* Some copywriting coaching from Amy Hoy's 30x500 workshop
Inspired by @peterc's excellent work on Javascript Weekly, and my fast-growing personal archive of news stories on how the coworking industry is exploding around the world, I decided to launch a simple weekly industry newsletter focused on sharing the best news, stories, announcements, etc.
If you work at or run a coworking space, there will be stuff in this newsletter for you.
Disclosure: I founded one of the earliest coworking spaces in the country, Indy Hall, in Philadelphia.
37S is doing a great job with all of their techniques. Of course, they also have an incredible sending volume on their side that helps improve the impact of any of these techniques.
One of the biggest benefits of our approach at Postmark is that you get those same benefits regardless of your send volume: http://blog.postmarkapp.com/post/14127210172/the-false-promi...
I didn't personally speak to every customer, but many of the customers were understanding and in some cases, very supportive of the decision. The produce hadn't gotten new features or much more than maintenance in over a year. They appreciated our honesty and perhaps more importantly, our empathy for the situation we ultimately created for them.
"Thanks for commenting. You are spot on, we weren't profitable in many other ways. The time we were spending on Newsberry could, and does, bring more profitability on our other products. In our opinion at Wildbit, half of an anything is not worth something. We don't build half-projects, and we don't put interns to work on them. But for many, it's hard to turn away $75/year."
As I mention in another comment, the important part is the transition from inbox to to-do list having a level of intelligence to it that considers context, the relationship with the person, current workload and priorities, etc. Right now a human does that. I'd pay for a product that did it, if it didn't feel to the sender like a robot was working for me.
I've collaborated with Amy, yes, but we're not nor have we ever been business partners. Good friends and co-conspirators for sure, like many of you on here. Her husband Thomas is her only business partner.
But this application proposal - and many peoples' workflows for everything from day-to-day email to customer support treat their inboxes as to-do lists. It's a bad habit, one I had myself and had to work HARD to break. An email interface that trains people out of that habit, or keeps people from forming it, would improve productivity for a lot of people without them even realizing it.
Sometimes, but not always. As your inbox volume increases, the % of things that come in that you don't want to become work for you also increases.
Note: I don't consider myself "famous". That said, I've gotten some good mainstream press related to my projects and I've also gone out of my way to make myself available to people by sharing my time, experiences, and lessons learned. This has paid off MASSIVELY and I wouldn't change that. What it's lead to, though, is the impact of a lot of people who don't think about the work they're creating for someone before they hit send. They're not forming complete thoughts, really asking for what they want/need, and in some cases, even asking anything at all.
I wouldn't give up the 20% of high quality email I get for the 80% of difficult to process email I get, but the 80% is still there.
That means that a pretty significant % of the non-spam emails I get are emails that need more work done to them before they're complete enough for me to do anything with them.
If I think of my inbox and assistant as a worker queue, it's their job is to keep incoming messages from being lost and disorganized, and in many cases, preparing the information/requests in the email for being worked on by me.
Maybe the issue is that the person adding things to my to-do list knows my workload, my priorities. The person emailing me doesn't have that context, and rarely has the consideration of it in the first place.
This is exactly the OPPOSITE of what I want. I consider myself a reasonably high-volume email recipient (>400 actionable emails a day on average).
The problem with "email as todo", which is a habit I had to work very hard to train myself out of, is that it turns your inbox into a to-do list that others can put things on.
This becomes the WORST to-do list ever.
With credit to Amy Hoy (Freckle, 30x500, etc): I believe that the problem is that every email that comes into your inbox is painful because it is associated with an unknown amount of work, and you don't know the amount of work until you open and read it.
Amy's newest product, Charm, is a help desk tool built to solve THAT problem - fundamentally decoupling the processing of email from the work that those emails contain.
My workflow right now includes:
1) first line of defense assistant does triage, cleaning out things that I don't ever need to see and either need deleting, or don't need my input. This includes anything from FAQ to scheduling meetings, etc. 2) second line of defense is answering emails that only need an answer - usually nothing more than a sentence or two. 3) everything else that's left in my inbox requires work. turning emails that do need my attention into todo's means that I can work from a to-do list, or ideally the current day's to-do list with items prioritized onto it with the help of an assistant.
I'm pretty sure that @sivers has a similar workflow that I've read about here on HN, he may be able to comment more.
This makes email 10000000x less painful, and makes my to-do list less like playing whack-a-mole. End of story: it's easier to get more work done. Email is working for me instead of against me. That is email nirvana, or as close as I'm willing to accept today :)
Of course - the problem with this workflow is that it requires another human. I don't know if that's avoidable. Truthfully, the people who I've hired who work with my inbox I trust deeply. My inbox is a strange dichotomy of a place that is private, but that anybody can send something into. He needs a lot of context for making smart calls, and for me, I need to trust him to make those calls.
Email clients need work - a lot of work - but this is more than renaming the statuses of an email and showing me who I've emailed most recently with.
Take the work out of email, and put it where it belongs.