{
    "componentChunkName": "component---src-templates-tags-tsx",
    "path": "/tags/best-practices/",
    "result": {"data":{"site":{"siteMetadata":{"title":"Frontside Software"}},"allBlogPost":{"totalCount":3,"edges":[{"node":{"id":"9bfaed99-9840-55bd-ad3d-012465e61bae","slug":"/blog/2020-12-11-default-branch-names/","title":"Renaming `main` with purpose ","authorNodes":[{"name":"Jorge Lainfiesta","slug":"/people/jorge-lainfiesta/"}],"markdown":{"excerpt":"At Frontside  (or any similar name) has never seemed like a great branch name. Like many developers, we navigate through different kinds of repositories all the time, from user-facing apps to Open…","frontmatter":{"description":"As generic default branch names like `master` for Git repos have gone out of fashion, possibilities emerge for more effective and informative naming conventions. Learn about the branch naming strategy Frontside uses for our Open Source libraries and how we name app project branches.","date":"December 11, 2020","img":{"childImageSharp":{"fixed":{"src":"/static/e84e2f02df3737e96cd1588e7578a6f2/2a4de/2020-12-11-default-branch-names.png"}}}}}}},{"node":{"id":"64d55be4-363c-54c9-84a6-7ccbdf23b805","slug":"/blog/2020-07-29-decoupling-teams-through-simulation/","title":"Beyond Mocking: Decoupling teams through Simulation","authorNodes":[{"name":"Charles Lowell","slug":"/people/charles-lowell/"},{"name":"Jorge Lainfiesta","slug":"/people/jorge-lainfiesta/"}],"markdown":{"excerpt":"Working across teams is challenging. It gets especially tricky when one team depends on another to make progress on their own tasks. For instance, take an all-time classic: the front-end team needs…","frontmatter":{"description":"Decoupling front-end and mobile teams from the back-end makes organizations more effective. In this article we explain why using simulation is an ideal strategy for this purpose, and present important considerations for adopting such practices.","date":"July 29, 2020","img":{"childImageSharp":{"fixed":{"src":"/static/2c1fe6c214acbe17dd3db9dfd6237dd3/2a4de/2020-07-29-simulator-social.png"}}}}}}},{"node":{"id":"b79d667f-b15c-5a23-8ea6-56b98c59daba","slug":"/blog/2020-04-15-7-reasons-for-good-pull-request-descriptions/","title":"7 reasons to write good Pull Request descriptions","authorNodes":[{"name":"Taras Mankovski","slug":"/people/taras-mankovski/"}],"markdown":{"excerpt":"In large open-source projects writing a good description in a Pull Request (PR) can be the difference between your changes being merged or ignored. These projects essentially necessitate the creation…","frontmatter":{"description":"A good Pull Request description can lead to better reviews, improved solutions, better documentation, and more. In this article, Taras surveys seven big wins of PR descriptions.","date":"April 15, 2020","img":{"childImageSharp":{"fixed":{"src":"/static/0bab407c201b2dec75d66de622ff5789/2a4de/2020-7-reasons-for-good-pull-request-descriptions-social.png"}}}}}}}]}},"pageContext":{"tag":"best-practices"}},
    "staticQueryHashes": ["1241260443"]}