<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Javascript developer framework and code maintenance in ArcGIS JavaScript Maps SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169591#M15727</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are all three people working on the same file? Ideally, someone should own that widget and they maintain and update it. Maybe break out some functionality into helper modules and others could own those.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as working in a team environment, git all the way. Learn the basics of git, then look at something like git flow.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow" title="https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow"&gt;Centralized Workflow | Atlassian Git Tutorial&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Basically, add new features/fix bugs via a feature branch so others can keep working on their part. Make a pull-request, maybe have someone review it before it's merged, stuff like that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Git is invaluable in a team environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Jun 2016 15:40:34 GMT</pubDate>
    <dc:creator>ReneRubalcava</dc:creator>
    <dc:date>2016-06-21T15:40:34Z</dc:date>
    <item>
      <title>Javascript developer framework and code maintenance</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169588#M15724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/3101"&gt;Robert Scheitlin, GISP&lt;/A&gt;​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a single Javascript file for a widget we are currently building and there are 3 developers working on the same project. Using AMD and loader classes what would be the best practice to split and reference the widget.js file so that its easy to write and maintain code by all the developers at the same time without having to step on each others foot? Is there any existing framework or sample that you would suggest?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 00:02:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169588#M15724</guid>
      <dc:creator>ImranMohammad</dc:creator>
      <dc:date>2016-06-21T00:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: Javascript developer framework and code maintenance</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169589#M15725</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Imran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I do not work in a multi developer environment so I don't have any advice for you here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 12:02:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169589#M15725</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2016-06-21T12:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Javascript developer framework and code maintenance</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169590#M15726</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would imagine that &lt;A href="https://community.esri.com/migrated-users/6443"&gt;Rene Rubalcava&lt;/A&gt;​ would have some pertinent thoughts about since, especially since joining the JS API team at ESRI..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 15:30:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169590#M15726</guid>
      <dc:creator>SteveCole</dc:creator>
      <dc:date>2016-06-21T15:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: Javascript developer framework and code maintenance</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169591#M15727</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are all three people working on the same file? Ideally, someone should own that widget and they maintain and update it. Maybe break out some functionality into helper modules and others could own those.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as working in a team environment, git all the way. Learn the basics of git, then look at something like git flow.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow" title="https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow"&gt;Centralized Workflow | Atlassian Git Tutorial&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Basically, add new features/fix bugs via a feature branch so others can keep working on their part. Make a pull-request, maybe have someone review it before it's merged, stuff like that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Git is invaluable in a team environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 15:40:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-developer-framework-and-code/m-p/169591#M15727</guid>
      <dc:creator>ReneRubalcava</dc:creator>
      <dc:date>2016-06-21T15:40:34Z</dc:date>
    </item>
  </channel>
</rss>

