<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coding on Handbook</title>
    <link>https://handbook.gradientmetrics.com/product-team/coding/</link>
    <description>Recent content in Coding on Handbook</description>
    <generator>Hugo -- gohugo.io</generator><atom:link href="https://handbook.gradientmetrics.com/product-team/coding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Coding in R at Gradient</title>
      <link>https://handbook.gradientmetrics.com/product-team/coding/coding-at-gradient/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/product-team/coding/coding-at-gradient/</guid>
      <description>Introduction The Gradient monorepo Setting up your Environment  Logging in to RStudio Workbench Updating your .Renviron   Using Git in our monorepo  Git credentials Branches Pull Requests       Introduction At Gradient we live and breathe R. We work with R every single day, and so it only makes sense to develop tools and workflows that help us code as easily and efficiently as possible.</description>
    </item>
    
    <item>
      <title>Working on code projects</title>
      <link>https://handbook.gradientmetrics.com/product-team/coding/working-on-projects/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/product-team/coding/working-on-projects/</guid>
      <description>g6tr package Starting a new session Project structure Setting up and working on projects Sharing projects Reading and writing files to the cloud (GDrive and S3) Ending a project     Please refer to the video below to accompany the written tutorial on this page.
  g6tr package First of all, if you are about to work on a project locally on your computer, make sure you have the latest version of the g6tr package, because it contains all our helper functions for managing projects.</description>
    </item>
    
    <item>
      <title>renv Issues</title>
      <link>https://handbook.gradientmetrics.com/product-team/coding/renv-issues/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/product-team/coding/renv-issues/</guid>
      <description>Before renv::restore()  Installing packages from GitHub   Troubleshooting renv::restore()  Suggested troubleshooting process Specific package installation issues  Biobase Package cannot be loaded There&amp;rsquo;s no package called &amp;hellip; Problematic GitHub installation record     Other issues  File access issue       Before renv::restore() So far there’s just one thing worth calling out:
Installing packages from GitHub When installing packages from GitHub, prefer using a commit SHA (not a PR ref such as e.</description>
    </item>
    
    <item>
      <title>Positron Setup</title>
      <link>https://handbook.gradientmetrics.com/product-team/coding/positron_setup/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/product-team/coding/positron_setup/</guid>
      <description>This page is not meant to be an exhaustive guide to setting up Positron, but rather a collection of setup hints that are easy to miss if you do not already know them.
Quarto extension At the time of writing, the most recent Quarto extension version, 1.131.0, introduces a noticeable delay when executing code from an .Rmd document with Cmd/Ctrl + Enter while the cursor is inside a code chunk: it can take around a second before the code is actually sent to the console.</description>
    </item>
    
  </channel>
</rss>
