cnagele

5 ms·

1.
Blood, sweat, and tears. How we built a Mac app and threw it away(medium.com)
11 points by cnagele 8y ago|0 comments
2.
by cnagele 9y ago
This is a big reason for sure. As you can see in this post, those IP addresses can be hit or miss depending on the provider. At Postmark, we don't really believe in dedicated IPs for all customers. We think that our customer base shoul
3.
by cnagele 10y ago
Hey everyone, Chris Nagele here from Wildbit. For some background, I wrote about our reasons for moving to a private office plan. In short, it's more than putting on some headphones. http://wildbit.com/blog/2015&#x
4.
by cnagele 11y ago
SparkPost's claims are misleading here. LinkedIn, Facebook, Twitter, etc do not use Sparkpost, they use their on-premise installable software that many ESPs use and pay tens or hundreds of thousands for, which indeed is a dumb pipe MTA
5.
by cnagele 11y ago
Three things to add here: 1. Our pricing reflects the quality of delivery due to being transactional only. With much higher engagement rates, our speed and delivery is superior. Customers never have to wait behind a bulk campaign. 2. Dedica
6.
by cnagele 11y ago
Thinking of "email delivery as a commodity" is the first mistake people make - all ESPs are not created equal. If this were the case, there would not be such a huge variance in not only getting to the Inbox, but how fast you get t
7.
by cnagele 12y ago
When we were searching for space this was our preferred choice. We wanted a large single floor space with offices on the perimeter. Each office would have a glass wall to see the open space. This way, as you said, people can see what is goi
8.
by cnagele 12y ago
These are great questions. I'll be sure to do a follow up post in a year and see where we are. I know that the biggest reward when we went from 100% remote to having an office was the feeling of being in touch with what was going on. I
9.
by cnagele 12y ago
Your first point reinforces our decision on private offices. We encourage only working 8 hours a day. This way you don't have a chance to stay late or work long hours to find that "quiet time" when everyone is gone. It's
10.
by cnagele 12y ago
Chris from Wildbit here (author of the post). Half of our team is remote. Using physical space for controlling productivity (or lack of) is not a solution. You and the rest of your team should keep each other accountable through performance
11.
by cnagele 12y ago
That's the best part, we are not funded at all and are building this office after eight years of profits from our products: Beanstalk, Postmark and dploy.io. We count every dollar that goes into the space and it is purely an investment
12.
by cnagele 12y ago
That's a great point. It reminds me of the "Library Rules" at the 37 Signals office: https://signalvnoise.com/posts/3357-an-office-with-ldquolibr... At the same time, I think visual distractions also nee
13.
by cnagele 13y ago
Agree. We'll make some updates to explain it better. Our hope was that the more simplistic overview would be enough. For now, you can read the blog post about it: http://wildbit.com/blog/2013/09/17/d
14.
by cnagele 13y ago
Hi Paul. About a year ago we migrated from Rackspace to Server Central, a colo facility in Chicago. Since then performance and uptime have been incredible. You can read more about the move and hardware here: http://blog.beanstalk
15.
by cnagele 14y ago
Capitalism works how you want it to work, that is the beauty of it. It's the business principles that lead the decisions that are made, either big or small. The point of the post is deciding what principles you set, and how they will shape
16.
by cnagele 14y ago
Hi Ben, the ES connector was part of it. At a certain point we had our custom oplog follower working well. After so many years working with MongoDB, we just lost trust in it, to be honest. We ran into so many bugs, replication issues (two s
17.
by cnagele 14y ago
Sorry, I need to correct that. I meant that shards are basically still primary / secondary with an arbiter for failover. We prefer horizontal nodes instead, like Cloudant, Elastic Search or Cassandra offers.
18.
by cnagele 14y ago
Chris from Postmark here. We definitely had some trouble over the last few weeks. I am hoping we are beyond that in terms of architecture. So far everything looks great. Regarding lock-in, this was pretty important to us when we decided to
19.
by cnagele 14y ago
Hi everyone. Chris here from Postmark. I would say that MongoDB durability used to be an issue, but now with journaling and replica sets it's not as much of a concern. There were two reasons why the secondary was less capable than the prima
20.
by cnagele 15y ago
Hi there. Chris here from Wildbit. I want to make sure I clarify some points. A big reason we waited so long to shut it down was leaving our customers stranded. Even at such low revenue, we owed everything to them for allowing us to get our
21.
by cnagele 15y ago
Hey everyone. Chris here from Postmark. This topic means a lot to me, so if you have any questions just post a comment and I'll try to respond quickly.
22.
by cnagele 16y ago
Note: I run Postmark ( http://postmarkapp.com ) where we handle delivery and bounce processing for a huge volume of email. It depends on how the emails are being sent. The typical approach is to set a "Return-Path:" header in your outbound
23.
by cnagele 16y ago
I think you miss the point here. It's not about betting on one or the other, it's about having options depending on your team or project.