Merge pull request #445 from codecrafters-io/TropicolX-patch-80

Add FAQ section to Redis challenge

Author: rohitpaulk

course-definition.yml

@@ -45,6 +45,56 @@ marketing:
   difficulty: medium
   sample_extension_idea_title: "Persistence"
   sample_extension_idea_description: "A Redis server that can read and write .rdb files"
+  frequently_asked_questions:
+    - question_markdown: "What exactly will I build?"
+      answer_markdown: |-
+        You'll start by implementing the core building blocks of every Redis server:
+        * Binding to a TCP port and listening for connections
+        * Responding to basic commands like `PING` and `ECHO`
+        * Parsing the Redis Protocol (RESP) from client requests
+        * Handling multiple clients concurrently
+        * Implementing the `SET` and `GET` commands to store and retrieve data.
+        
+        At this stage, your Redis will already feel real, and you'll be able to interact with the official `redis-cli`. 
+        
+        As you progress, you'll implement advanced features like:
+        * Redis replication
+        * RDB persistence
+        * Atomic transactions
+        * ... and more
+        
+        At the end, you'll have a GitHub repo to show off.
+        
+    - question_markdown: "What exactly will I learn?"
+      answer_markdown: |-
+        In the first 7 stages, you'll learn:
+        * How a TCP server binds to a port and accepts connections
+        * What the Redis Protocol (RESP) is, and how to parse/encode messages
+        * How to handle multiple clients concurrently
+        * How to implement commands like `PING`, `ECHO`, `SET`, and `GET`
+        * How to manage a key-value store with automatic key expiry
+        
+        In the advanced stages, you'll discover new programming ideas, such as master-replica synchronization, atomic transactions, and specialized data structures like sorted sets and geospatial indices.
+        
+        As your code gets complex, you'll be forced to structure and refactor it - to avoid regressions and to make adding new features easier.
+        
+    - question_markdown: "Why should I build such a project?"
+      answer_markdown: |-
+        Building your own Redis blends network programming, concurrent computing, and system design. If you've mostly built websites or apps, this project takes you a layer deeper to understand how caching and distributed systems work. 
+        
+        You’ll also be building a core piece of infrastructure that applications rely on, such as [Twitter's timeline](https://blog.x.com/engineering/en_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale#cache) and [Uber's integrated cache](https://www.uber.com/en-GB/blog/how-uber-serves-over-40-million-reads-per-second-using-an-integrated-cache/).
+        
+        Beyond technical depth, there's something uniquely satisfying about understanding a tool used by millions of developers every day. You'll come out of it as a more confident and interesting developer.
+        
+    - question_markdown: "What are the prerequisites for this challenge?"
+      answer_markdown: |-
+        You should be comfortable writing code in any one language and using Git. No prior experience with databases or network programming is required.
+        
+        Most learners pick up required concepts (e.g, TCP servers) as they go.
+        
+        What matters most is curiosity and persistence. You'll develop intuition by exploring, debugging, and discovering solutions yourself.
+        
+        While we will make it extremely simple to get started, don't expect this to be a follow-along tutorial.
   testimonials:
     - author_name: "Charles Guo"
       author_description: "Software Engineer, Stripe"