Update prompts.txt

prompts.txt

@@ -1,14 +1,33 @@
-input_texts = [ 
-    "Site Reliability Engineering is a concept born at Google. Ben Trainor's team of seven people started it in 2003 to keep Google.com running reliably.",
-    "Reliability is critical for any system. Without reliability, even the best features are useless as users can't access them.",
-    "SRE teams at Google handle large-scale systems with efficiency, working closely with developers to ensure scalability, reliability, and cost-effectiveness.",
-    "Site Reliability Engineering treats operations as a software engineering problem, making it distinct from traditional operations teams."]
-target_texts = [ 
-    "SRE was introduced at Google in 2003 by Ben Trainor's team to ensure the reliability of Google.com.",
-    "Reliability is essential for a system to be usable; without it, features lose value.",
-    "Google's SRE teams collaborate with developers to manage large-scale systems efficiently and reliably.",
-    "SRE approaches operations as a software engineering task, revolutionizing traditional operational methods."]
-
-# Veriyi temizleme
-input_texts_cleaned = [clean_text(text) for text in input_texts]
-target_texts_cleaned = [clean_text(text) for text in target_texts]
+Purpose and Relevance Prompt
+"Describe why Site Reliability Engineering (SRE) is a crucial discipline in today's technology landscape. Explain how it aligns with business objectives such as system uptime, scalability, and user satisfaction. Use analogies or examples to clarify its purpose."
+
+Historical Context Prompt
+"Outline the historical development of SRE, beginning with its inception at Google in 2003. Discuss the challenges that prompted its creation and how these challenges shaped its principles. Compare its evolution to similar fields like DevOps and explain their overlaps and differences."
+
+Core Practices Prompt
+"List and explain the core practices of SRE, such as Service Level Objectives (SLOs), incident management, and capacity planning. For each practice, provide examples of how it is implemented and its benefits in ensuring system reliability."
+
+Team Dynamics Prompt
+"Explain the role of an SRE team within an organization. Discuss how they collaborate with developers and operations teams to maintain balance between rapid feature deployment and system stability. Include an example of how an SRE team intervenes during a critical incident."
+
+Philosophical Principles Prompt
+"Discuss the philosophical principles behind SRE, such as 'embracing risk' and 'monitoring as a feature.' Explain how these principles differ from traditional IT practices and why they are necessary in large-scale systems."
+
+Scaling Challenges Prompt
+"Describe the unique challenges of scaling systems from thousands to billions of users. Include examples of how Google tackled these challenges using automation, resource optimization, and innovative monitoring practices."
+
+Real-World Case Studies Prompt
+"Provide real-world case studies where SRE practices prevented system failures or resolved critical issues. Include specific examples, such as Gmail's reliability strategies, and discuss the lessons learned from these scenarios."
+
+SRE Tools and Automation Prompt
+"Describe the tools and automation techniques commonly used in SRE. Discuss how these tools, such as monitoring systems, alerting platforms, and chaos engineering practices, contribute to maintaining system reliability."
+
+Educational Techniques Prompt
+"Suggest ways to make SRE concepts more accessible to students. Include tips for using diagrams, real-world analogies, or hands-on labs to explain complex topics like error budgets or capacity planning."
+
+Future of SRE Prompt
+"Predict the future of Site Reliability Engineering. Discuss trends such as the integration of AI for predictive monitoring, serverless architecture challenges, and how SRE principles might evolve in a cloud-native environment."
+
+Engagement and Retention Prompt
+"Provide suggestions for keeping students engaged during a lecture on SRE. For instance, suggest interactive activities, thought experiments, or group discussions to explore topics like trade-offs between reliability and feature velocity."
+