+44 44 0
Published 8 years ago by everlost with 3 Comments

Join the Discussion

  • Auto Tier
  • All
  • 1
  • 2
  • 3
Post Comment
  • jmcs
    +4

    One important thing to note is that while Google has everything in one repository they aren't a single project. They aren't "one thing" like the article claims. From what I heard from Googlers, Google actually uses lots of independent microservices, the single repository is just so the developers always have the latest versions of dependencies available.

    • idlethreat
      +2

      I think my biggest take-away is this comment

      “When you start a new project,” Potvin tells WIRED, “you have a wealth of libraries already available to you. Almost everything has already been done.”

      I like the idea of a centralized library of functions already written that can be repurposed for other tasks easily. We have a gitlab server at my job where we've been squirreling away code projects. I can see creating one 'main' project containing subfolders for php, python, powershell, etc with discrete libraries that can be included in new projects with the minimum of fuss.

      If you find yourself writing new functions in your new project, put them into the main library where everyone can use them for their projects.

      Anyway, nice idea.

      • jmcs
        +2

        The biggest take away I got from talking with several people at Google is that they always build against the latest changes of other projects the depend on, so they catch incompatible changes early (they have special build machines that builds everything on demand). Having a library of functions could be solved with common packages in a package repository, for example, but this approach takes continuous integration to the next level.

Here are some other snaps you may like...