11–20 of 96 posts
> But I ended up picking Mercurial for the distributed version control system, which we were definitely wrong on that one–should have picked Git. I'm curious to know: is this sentiment widely shared? Is git really that much better than hg?
Earlier quoted context omitted.
Dogfooding is quite important, yeah. Some products, hmm, maybe not. For example, if I work for a dating app, I may not feel comfortable actually using the app myself especially when I am committed to a relationship. I.e. I can't dogfood it because I have no use of the product. In the case of say Facebook, I believe employees use the site internally so dogfooding is possible, even if privately some employees don't act…
For low barrier to entry products like facebook, dating sites, etc, I think companies are smart enough to build internal facing development only environments - so as a developer you won't be "using" the dating site, just using/testing/dogfooding the internal "dev" dating site that has maybe a million robots and all the employees, contractors, partners of the company. If you haven't set down ground rules with a partne…
> We were all using the product so when there was funny stuff we tended to catch it. I love this. There have been so many times I've run into a bug that makes me wonder if anyone on the engineering team actually used the product.
> But I ended up picking Mercurial for the distributed version control system, which we were definitely wrong on that one–should have picked Git. I'm curious to know: is this sentiment widely shared? Is git really that much better than hg?
Never used mercurial. I suspect it's just as good, but the problem the author probably sees is, like me, most everyone is familiar with git and new hires need to be trained in something unfamiliar with less community around it.
It could be that I witnessed the popular adoption of all this via Linux going from tarballs/patches/mailing lists -> bitkeeper -> git, and have used and witnessed-the-evolution-of rcs, cvs, subversion, various DSCMs, and so my concepts of source control are stretched more broadly than people that are experiencing the dissonance between (e.g.) mercurial and git.
Edit: clarifying words
Does Drew come from a privileged family?
> We were all using the product so when there was funny stuff we tended to catch it. I love this. There have been so many times I've run into a bug that makes me wonder if anyone on the engineering team actually used the product.
Also known as 'dogfooding' or 'eating your own dog food' [0], and yes, not enough companies/software teams do this. Developers that build software aimed at or naturally used by other software developers kind of have an unfair advantage here. https://en.wikipedia.org/wiki/Eating_your_own_dog_food
Does Drew come from a privileged family?
Earlier quoted context omitted.
Also known as 'dogfooding' or 'eating your own dog food' [0], and yes, not enough companies/software teams do this. Developers that build software aimed at or naturally used by other software developers kind of have an unfair advantage here. https://en.wikipedia.org/wiki/Eating_your_own_dog_food
Back when I worked for a pre internet messaging company our terminals speed was slowed down to the same (1200 or 2400 baud) as a dial up user would see.
Does Drew come from a privileged family?
In the context of this article, does it matter?
Privilege is a fuzzy term. A lot of people are born into good families but achieve way less than what he has achieved. So his background would not matter much for his achievements but it might matter a bit in giving other people hope just the way whether Tim Cook is gay matters very little for him but it matters a lot to little gay kids who want to be like Tim Cook.