From c16c7fcf4720fddd35fa3184695a69ddbbc81d01 Mon Sep 17 00:00:00 2001
From: Brandon <3676319+sibeitokgong@users.noreply.github.com>
Date: Sat, 21 Oct 2017 01:42:29 +0800
Subject: [PATCH] Remove broken link in front-end/design (#69)

---
 front-end/design.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/front-end/design.md b/front-end/design.md
index 38b58ef2..cef9c972 100644
--- a/front-end/design.md
+++ b/front-end/design.md
@@ -12,7 +12,3 @@ Talk me through a full stack implementation of an autocomplete widget. A user ca
 - What does the backend API look like?
 - What perf considerations are there for complete-as-you-type behavior? Are there any edge cases (for example, if the user types fast and the network is slow)?
 - How would you design the network stack and backend in support of fast performance: how do your client/server communicate? How is your data stored on the backend? How do these approaches scale to lots of data and lots of clients?
-
-###### References
-
-- https://performancejs.com/post/hde6d32/The-Best-Frontend-JavaScript-Interview-Questions-%28written-by-a-Frontend-Engineer%29