campo

I discovered The Prophet by Kahlil Gibran around 2009 and it quickly became and has remained one of my favorites. I appreciate the descriptiveness and beauty of the language along with the continuing relevance of the advice. It's very easy reading and enjoyable to pick up for a short time and enjoy in small bits or read straight through.

https://en.wikipedia.org/wiki/The_Prophet_%28book%29

A couple favorites of mine are:

On Pain - http://www.katsandogz.com/onpain.html

On Reason & Passion - http://www.katsandogz.com/onreason.html

I saw this statement and was puzzled at first myself.

That would not be a 20% lift on number of visits by the customer, but it could be a 20% lift on revenue or margin from that customer.

I'm just not clear on how branching gets in the way of continuous integration here. What I've started doing is any time I change anything I do it in a branch. Once I've got my changes working, tested, and I'm ready to deploy, I merge that branch back to master. The idea here being that I could deploy from master at any time and be completely functional. That way I can just constantly deploy any time I merge something back to master.

Perhaps I misunderstood something here though. Does anybody have any thoughts on this idea?

That's great, reducing the barrier to entry for new projects allows for more experimentation. More experimentation increases the likelihood you'll stumble upon something you really like!

What I meant to say more clearly is that I probably iterated through the creation of that web application so quickly because in five days I committed to git 75 times. In my time at Microsoft I don't know that I would have made 75 commits in a year, and creating new branches was very costly.

I got numbers on my git repository by using GitStats: http://gitstats.sourceforge.net/

I absolutely agree with this. I recently started working on a small web app as a side project. I was dealing with a lot of elements that were new to me and was constantly pushing the limits of my knowledge and breaking things. I realized I wasn't using the power git provided me with branches.

Once I started branching things got quicker and more effective because I could bounce between tasks without affecting my deployment (master branch). In five days of frantic coding using git branching I now have a clean easy deployment of about 750 lines, which I iterated on through four different branches and, probably over 3000 lines of code.

It's not perfect, but it's eliminated any apprehension about aggressively changing my application, and made me far more ambitious. I feel great about it.

It would be very surprising to me if PaulG or anybody else at YC approved Dropbox's application without receiving what they believed to be a satisfactory answer to a question along the lines of "What happens when Amazon becomes your competition?"

Hal Abelson is a smart guy. He does a lot of work concerning law, privacy, and technology, including the internet and mobile devices. You may want to take a look at his book Blown to Bits http://www.bitsbook.com