Here’s how Parse.ly’s original 2009 logo looked: Parse.ly has some fun startup lore from its early days about how we “acquired” this logo. I wrote about this in a post entitled, “Parse.ly: brand hacking”: Our first Parse.ly logo was designed as a trade for another domain I happened to own. It was the dormant domain … Continue reading Parse.ly’s brand refresh
After initial product-market fit and during a period of rapid customer adoption, the Parse.ly team embarked upon the task of re-envisioning its entire backend technology stack. The goal was to build upon the learnings of more than 2 years delivering real-time web content analytics, and use that knowledge to create the foundation for a scalable … Continue reading Shipping the Second System
Engineers hate estimating things. One of the most-often quoted lines about estimation is “Hofstadter’s Law”, which goes: Hofstadter’s Law: It always takes longer than you expect, even when you take into account Hofstadter’s Law. If you want to deliver inaccurate information to your team on a regular basis, give them a 3-month-out product development timeline … Continue reading Software planning for skeptics
Note: This post was written on August 17, 2017. I was living in Charlottesville, Virginia at the time; I had been based there since 2011 and would end up living there until 2019. Unfortunately, 5 days before this post was written, a tragedy happened in my town. This was my attempt to provide an alternative … Continue reading Charlottesville tech: a community that won’t be stopped by tragedy
Note: This post was authored by Sachin Kamdar, my co-founder at Parse.ly, in 2017. It was written as CEO of the company we started together, but reflects our joint attitude, at least at that moment in time, toward fundraising. It is hosted on my blog as an archival project for the MuckHacker group blog we … Continue reading A Different Way — Thoughtful Financing, Or Why We Said “No” to a Lot of Money
I wrote a letter in support of net neutrality and Title II classification of Internet Service Providers to the FCC. For background on this FCC vote, you can read this Arstechnica explainer. You can add your own comment in support of net neutrality to the FCC at the URL gofccyourself.org. To clarify some terms: “net … Continue reading In support of net neutrality
In September 2013, my startup, Parse.ly, had just raised Series A capital, and had just begun growing its team rapidly, from a small group of fewer than 10 to over 40 employees now. In the past several years, I have run Parse.ly’s fully remote engineering, product & design team. Back in 2013, we had achieved … Continue reading Parse.ly Culture: Ethics & Identity
Michael O. Church wrote an essay awhile back called “Why programmers can’t make any money.” The post is no longer on his website — for some strange reason — but you can have a look at the archived version here. If you don’t wish to read his post, this quote will give you the summary. … Continue reading The value of money in a technology career
Can pair programming be done in a way that is compatible with async communication? Pair programming is described by the original c2 wiki as a process in which “two engineers participate in one development effort at one workstation”. It would seem the process is inherently synchronous, at least as originally described and practiced. I experimented … Continue reading An async kind of pair programming
Python was the core programming language used at Parse.ly. It is a widely-used language with huge adoption among open source projects. It’s no wonder it’s one of the leading languages for software teams. I’ve written a couple of blog posts with original material for learning Python, including “import this: learning the Zen of Python with … Continue reading The 3 Best Python Books for Your Team
