P4 Blog

  • June 02, 2015

    LIVE WEBINARS on Tuesday, June 16th - Get Best Practices for Secure DevOps from Forrester Analysts

    Posted In:
  • June 01, 2015

    In this age of industrial espionage, insider theft and advanced cyber threats, it is becoming increasingly difficult to secure intellectual property (IP). The stakes are high. In fact, the IP Commission Report estimates annual losses of $300B attributed to IP theft in the United States alone. A Kroll Advisory Systems white paper describes how industrial espionage and insider attacks were responsible for the loss of trade secrets valued at $300M at Dow Chemical; $225M in illicit proceeds of a DuPont competitor that obtained DuPont’s Kevlar trade secrets; theft of Space Shuttle, jet and rocket design trade secrets from Rockwell and Boeing and technical IP theft from Motorola.

    Posted In:
  • May 28, 2015

    As I said recently when offering advice for Git users, the new DVCS features of Perforce Helix are easy to use, but making the transition from another system always involves climbing a learning curve. The purpose of today’s post is to provide some guidance specifically for Mercurial (Hg) users.

    Posted In:
  • May 21, 2015

    With the recent 2015.1 release of the Perforce Helix Visual Studio (P4VS) plugin, we are very excited to introduce Lazy Load of file states. We call this “Lazy Load” because when this feature is on, file states will not be loaded until you are ready to load them from the server. This is a huge win from a performance point of view, especially if you have a lot of files or work remotely. It’s less work on your system resources, allowing the plugin to perform much faster. 

    Posted In:
  • May 21, 2015

    The new DVCS features of Perforce Helix are easy to use, but making the transition from another system always involves climbing a learning curve. Toward that end, it only makes sense to provide some guidance toward the summit. The purpose of this post is to do that specifically for Git users.

    Posted In:
  • May 20, 2015

    Python 2.5 gained the with statement in 2005, implementing PEP 343. The statement was designed to factor out the use of try-finally blocks and is often used to control the use of resources. A standard idiom, for example, is to use a with block when opening a file:

      with open(“somefile.txt”,”r”) as f:
    	  content = f.read()
    Posted In:

Pages