From 5aa383a8ec0883b95f8a129d0ba18c8b31f38cb6 Mon Sep 17 00:00:00 2001
From: my-gitty <72162392+my-gitty@users.noreply.github.com>
Date: Thu, 1 Oct 2020 06:41:19 +0530
Subject: [PATCH] Update README.md

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 133ae39..0453998 100644
--- a/README.md
+++ b/README.md
@@ -12,6 +12,7 @@ Tired of Googling around for programming interview practice problems? This is a
 
 1. **Code in a realistic fashion**. If you're doing a whiteboard interview, practice with a whiteboard. If you don't have a whiteboard, writing your solution on paper can be a good substitute. Phone interview? Try using the online code pad they will have you use.
 2. Always compile your code after writing it. You'll often find bugs in your solution. Think—how might you catch this problem in the future?
+3. You can a better IDE to auto-compile when you are a beginner.
 
 ## What makes a good practice problem?