This cheatsheet covers how to control and troubleshoot the working directory in R, RStudio Desktop, and RStudio Cloud. A correct working directory makes data import, script sourcing, and project management much smoother.
Windows check whether your system supports UEFI by following these steps:
- Press Win + R, type
msinfo32
, and hit Enter. - In the System Information window, look for BIOS Mode.
- If it says UEFI, your laptop supports it! If it says Legacy, it does not.
For UEFI supported system, we can opt to GPT
for partition scheme. Otherwise, choose MBR
.
I have exported my bookmarks from Pocket into a CSV file and I will attach it now. Please help me convert it into a format that Raindrop.io can import:
- For each link, determine a Collection (high-level category) and assign appropriate Tags (subtopics). Collections are broad groups (e.g., Technology, Cooking, Health), while tags are specific keywords (e.g., Python, recipe, wellness).
- Include any original description or notes from Pocket in the note field if they add useful context.
- If a link has no clear topic or tags, put it in a generic Collection like Uncategorized or create a new one as needed.
- You can create new Collections or tags whenever necessary to organize the links logically.
- The final output should be a CSV file with columns: url, folder, title, note, tags (and optionally created). Use folder for the Collection name. Put multiple tags in quotes (for example,
"tag1, tag2"
). - Provide example groupings such as:
- Technology (Collection) with tags "programming, Python, AI"
- R
Tip: Passwords and keyboard layout It is recommended to only use US ASCII characters. In case of a system error or when you need to start your system in rescue mode, the keyboard may not be localized.
Here are the US ASCII characters:
! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~
Windows has a plethora of useful hotkeys that can significantly enhance your productivity. Here are some of the most practical ones, categorized for ease of reference:
- Win + D: Show Desktop. "Win + D - show desktop. Press again to go back to showing windows."
- Win + E: Open File Explorer. "Windows + E to open File Explorer"
- Win + Shift + Arrows: Move window between monitors. "Win-Shift-Arrows: moves window from one monitor to the next"
- Win + Arrow Keys: Snap window to the left, right, up, or down. "Win +(arrow key) to auto fit your window to one side of the display"
- Alt + Tab: Switch between open windows. ["Alt + Tab to access another app
Indicating the project status in your README is a great way to communicate the current state of your project to potential collaborators, recruiters, or users. You can use a "Project Status" section near the top of your README to make this clear. Here’s how you can do it:
Including a badge is a common way to display project status. You can generate badges using services like shields.io. Here’s an example:

-
providers.tf
Description: Theproviders.tf
file is used to configure and declare provider settings in Terraform. Providers enable Terraform to interact with cloud platforms (e.g., AWS, Azure, GCP) or other services. This file specifies provider versions, regions, and authentication methods. -
variables.tf
Description: Thevariables.tf
file defines input variables for Terraform configurations. These variables allow parameterization of values like resource names, regions, or instance types, making configurations more reusable and dynamic. -
outputs.tf
Description: Theoutputs.tf
file is used to expose the results of a Terraform run. It outputs values, such as IP addresses, URLs, or resource attributes, for use by other configurations, tools, or workflows.
Both .gitkeep
and .keep
can be used to keep an empty directory in version control. However, the difference lies in how Git handles them.
.gitkeep
is a file that tells Git to keep the directory it's in as a versioned entity. When you commit a .gitkeep
file to a Git repository, Git will keep the directory it's in, even if it's empty.
.keep
is a file that tells Git to keep the directory it's in as a versioned entity, but it's not as widely supported as .gitkeep
. While both files achieve the same purpose, some Git versions may not recognize .keep
as a valid file for keeping directories.
In general, it's recommended to use .gitkeep
instead of .keep
to ensure that your empty directories are kept in version control across different Git versions and platforms.