Smash Notes
How Did a Few Months Building a Knowledge Base Pull Dnsimple Back to Staying Focused?
On IndieRails, DNSimple made a conscious decision to do a set of things and do them well. A few months spent building a knowledge base then showed why DNSimple stays focused.
DNSimple strayed from the plan. Its CTO and the person telling the story decided knowledge bases were poor and spent a few months building a knowledge base. The side effort was a complete distraction and a very bad idea, and the experience quickly pulled DNSimple back to the reason for staying focused.
DNSimple still releases new products. Work from last year and the year before produced the domain control plane, a concept for connecting to other DNS providers and other domain providers and seeing all of them from within DNSimple.
IndieRails
·
Anthony Eden - Making Business Look Simple
·
at 1:02:12
·
·Transcript
People
On this episode
You might also like
- How Did Dnsimple Limit Automated Clearing House Payments to the Yearly Business Plan After Larger Customers Refused Credit Cards?
- How Did Anthony Eden Get Introduced on Geek at Sea as the Person Behind Dnsimple About 10 Years After He Started It?
- How Did Anthony Eden Turn a Perl Alias Script Into an Erlang Name Server So a Naked Domain Could Point at Heroku?
- How Did Dnsimple Replace a User-equals-account Login With a Many-to-many Relationship So One User Can Reach Many Accounts?
- How Did Dnsimple's Domain Control Plane Let Zones at Azure and at Dnsimple Sit Side by Side and Move Back and Forth?
- How Did the Last Couple of Years of Registrar Investment Make Dnsimple Split Almost Evenly Between Domain Registration and Operational Domain Name System Work?