February 12, 2014by Sven Erik Knop, Technical Marketing Engineer at Perforce Software
Perforce sponsors an event called “Monki Gras”, a two-day long software development conference run by analyst firm RedMonk (www.redmonk.com) in London. The event this year was held in the Village Hall in Shoreditch under the topic “Sharing Craft” - and I was lucky enough to be able to attend and represent Perforce.Posted In:
February 11, 2014by Don Marti, Technical Marketing Manager at Perforce Software
Git is awesome for the type of problem it's good for. Relatively small groups of people, working on human-scale projects made up of text, code, and other small, easily-mergeable files, with no fine-grained read access control. If you want to start an open-source project, or a company internal "two-pizza team" that works like an open-source project, then git is a good choice.Posted In:
February 10, 2014
by Matt Attaway, Open Source Community Manager (@p4mataway)Posted In:
February 06, 2014by Zig Zichterman, Technical Lead at Perforce Software
Swarm, Perforce's social coding tool, has always been a great tool for reviewing changes. I use it all the time when reviewing changes after someone pushes to our Git Fusion project. New for 2014, Swarm lets me review changes from Git before those changes are committed to the project.
February 05, 2014by Furkan Khan, Director of Product ManagementPosted In:
January 31, 2014by Dhruv Gupta, Director of Product Marketing at Perforce
An interesting article came out recently, “Why Continuous Deployment may mean Continuous Disappointment for your Customers.” It correctly identifies the human need for a shiny, new thing every so often. And it argues that the practice of continuous deployment could lead to disenchantment with incremental updates.
The article cites examples of companies whose customers were left disillusioned by incremental additions or subtractions to existing capability.Posted In: