Poll: How often do you 'ship' code?

2 points by famousactress ↗ HN
A discussion with some ex-coworkers at lunch today made me realize that I really do believe that the most important idea to me when it comes to building quality software is that you ought to release more often... Whatever that means for you.. but really, that approaching the limit of releasing as close to commit-time as possible is the general vector we ought to strive for.

I think I'd vote for that ideal before I'd vote for any particular programming language, tool, operating system, or hiring practice. Dunno. Maybe I'm nuts.

At any rate, I'm gonna have some time this weekend to write up a blog post on exactly why I think it's so important, what effects I think it has on the product and the team that's working on it, and perhaps most importantly.. why your product/space/team is almost certainly not exempt from the deploying a lot more often.

Meanwhile, I wanted to gather some numbers. So how often do you release? I guess if we're getting specific here I'm not talking about patch-fixes to serious bugs, or wildly experimental branches. I'm basically talking about the bread-n-butter feature development that happens on master. How often does it get shipped (on average)?

[Edit: It'd also be really interesting to hear why you don't ship more often than you do!]

0 comments

[ 2.8 ms ] story [ 12.1 ms ] thread

No comments yet.