Now Playing Tracks

continuous delivery

I personally believe that the developer of a system/feature is the most qualified person to define how their code is configured and deployed.

in response to a stackexchange question, wrote a bit about how i think configuration management and deployment automation fit into a software team.

"BE AWARE: THE CHANGES OUTLINED IN THIS BLOG MAY SLIP TO EARLY NEXT YEAR IF THEY DON’T MEET THE NECESSARY SOFTWARE AND QA MILESTONES, IN THE SPIRIT OF DOING THINGS PROPERLY RATHER THAN QUICKLY. WE WILL LET YOU KNOW IF THIS HAPPENS"

Big and fat before an announcement about a new feature in eve online. nice to see the smarter-not-harder approach. CCP is probably a fun place to work. (yet then they mention deployment risk. Yikes, not automated?)

(Source: eveonline.com)

Marco.org: Developers don't rush to new platforms

marco:

A common fallacy is assuming that any new platform in an exciting market — recently, smartphones and tablet computers — will be flooded with developers as soon as it’s released, as if developers are just waiting outside the gates, hungrily waiting to storm in.

In two recent cases, that’s exactly…

good point about ease of purchasing in the app store.  what if buying everything only took two touches to confirm that you want it? sounds fun to me.

maybe it’s time for the shopping cart metaphor to die.

We make Tumblr themes