updated the docs

Author: shadil-rayyan

docs/Desktop/launchers/ulancher.md

@@ -41,10 +41,3 @@ Students will primarily use Ulauncher to navigate their daily development enviro
 *   **Quick Calculations:** Perform math directly in the search bar (e.g., `2^10` or `150 * 1.05`) to avoid opening a separate calculator application.
 *   **File and Folder Search:** Find specific project directories or configuration files instantly without browsing through a file manager.
 *   **Web Search Shortcuts:** Use predefined keywords to search the web. For example, typing `g react hooks` will immediately open a Google search in your browser, saving you the steps of opening the browser and navigating to the search bar.
-
-### Professional Insight (Top 1% Knowledge)
-
-The true power of Ulauncher lies in its community-driven extensions. While beginners use it as a simple search bar, experienced engineers use it to bridge disparate workflows. You should explore extensions that allow you to search your clipboard history, manage Docker containers, or open specific VS Code projects directly from the launcher.
-
-A professional habit is the rigorous minimization of keystrokes. You can customize keyword triggers for your most frequent tasks—for example, reducing the StackOverflow search trigger to a single letter `s`. This creates a personalized, high-speed command center where any developer task is only two or three keystrokes away. Reaching this level of muscle memory separates senior engineers who can navigate systems effortlessly from those who are slowed down by their interface.
-

docs/Desktop/learning/codecompass.md …cs/Desktop/learning/codecompass/index.mddocs/Desktop/learning/codecompass.md renamed to docs/Desktop/learning/codecompass/index.md docs/Desktop/learning/codecompass.md renamed to docs/Desktop/learning/codecompass/index.md

@@ -28,14 +28,3 @@ Students will use DistroSea as a safe playground for system exploration:
 *   **Desktop Environment Evaluation:** Launching different versions of the same distro to see whether they prefer the workflow of GNOME, the customization of KDE, or the minimalism of XFCE.
 *   **Safe Command Practice:** Using the browser terminal to practice high-risk commands (like modifying filesystem tables or system configurations) without any risk to their host machine.
 *   **Quick Troubleshooting:** Verifying if a specific software package or configuration behaves differently on a clean, remote distribution compared to their local setup.
-
-### Professional Insight (Top 1% Knowledge)
-
-Experienced engineers treat DistroSea as a **pre-flight verification tool**. While it is not a substitute for a local development environment, a professional uses it to quickly verify the layout or default behavior of a system they might soon be deploying to a server or a client's machine.
-
-A professional habit is to use tools like this to **audit default environments**. For example, an engineer might launch a DistroSea session simply to check which version of a library or kernel a specific distro ships with by default. This saves the time of downloading a multi-gigabyte ISO and setting up a local virtual machine just for a five-minute check. 
-
-The "Top 1%" insight here is understanding the **limitations of the abstraction**. A senior engineer knows that a browser-based session will never reflect the true latency, hardware compatibility, or performance of a bare-metal installation. They use DistroSea to judge "logic and layout," while reserving "performance and stability" judgements for a local, dedicated environment. Use DistroSea to narrow your choices, but always perform your final benchmarks on your actual hardware.
-
-
-

docs/Desktop/learning/distrosea.md

@@ -34,9 +34,3 @@ Students will use these resources to build a comprehensive and practical enginee
 *   **Project-Based Learning:** Following "The Odin Project" or "freeCodeCamp" to build real-world applications (like a terminal-based game or a web server) for their portfolio.
 *   **Deep Theory:** Watching MIT OCW lectures on "Introduction to Algorithms" or "Operating Systems" to build the theoretical foundation necessary for senior-level systems design.
 *   **Community Mentorship:** Participating in Exercism's mentorship program to learn how experienced developers think about code structure and performance.
-
-### Professional Insight (Top 1% Knowledge)
-
-The "Top 1%" of engineers don't stop using these resources once they get a job. They treat their education as a **perpetual engineering project**. A senior developer might return to Exercism to learn a functional language (like Haskell) just to expand their mental models of data flow, or revisit an MIT OCW course on distributed systems when their team is scaling an application.
-
-A professional habit is to **curate your own curriculum**. Don't just follow a platform blindly; analyze your weaknesses and find the world-class resource that addresses them. Furthermore, understand the value of **mentorship and code review**. The fastest way to grow is to have your code torn apart by someone better than you. By actively seeking feedback on platforms like Exercism, you develop the thick skin and analytical eye necessary to succeed in high-stakes professional environments. Treat these resources not as "homework," but as your personal research and development department.

docs/Desktop/learning/education.md docs/Desktop/learning/education/index.mddocs/Desktop/learning/education.md renamed to docs/Desktop/learning/education/index.md

@@ -34,13 +34,3 @@ Students will use gamified platforms to supplement their formal education and pr
 *   **Database Practice:** Solving mysteries in SQL Noir or Knight Lab Mystery to build complex queries and understand relational data logic.
 *   **Competitive Programming:** Participating in platforms like Bitburner or BattleSnake to test their algorithm design against other students or AI.
 *   **Iterative Debugging:** Refitting a solution multiple times to achieve a "perfect score" or "most efficient code" in a game level.
-
-### Professional Insight (Top 1% Knowledge)
-
-Experienced engineers use gamification not just for initial learning, but for **cognitive flexibility and prototyping**. Many "coding games" are actually sophisticated simulations of real-world problems. For example, the challenges in "Elevator Saga" or "Screeps" mirror the complexities of asynchronous programming, resource management, and pathfinding that senior engineers solve in production systems.
-
-A professional habit is to use these tools to **"warm up" or explore new paradigms**. A senior backend engineer might play a CSS game to quickly regain spatial intuition before helping a frontend team, or a developer might use an AI-based game to experiment with heuristic logic. 
-
-The key insight for the "Top 1%" is that **learning should be continuous and playful**. By treating complex technical challenges as games, you develop a problem-solving mindset that is resilient to frustration. A senior engineer doesn't see a difficult bug as a disaster, but as a "hard level" that requires a more creative approach. Adopting this gamified attitude toward your entire career is what allows for long-term growth without burnout.
-
-

docs/Desktop/learning/game.md docs/Desktop/learning/game/index.mddocs/Desktop/learning/game.md renamed to docs/Desktop/learning/game/index.md

@@ -34,13 +34,3 @@ Students will use interview preparation resources to systematically sharpen thei
 *   **Architectural Study:** Reviewing the System Design Primer to understand how large-scale applications (like Uber or WhatsApp) are structured for reliability and scale.
 *   **Template Mastery:** Learning and implementing "standard library" versions of algorithms (like BFS/DFS or Binary Search) until they are part of muscle memory.
 *   **Behavioral Prep:** Using the Tech Interview Handbook to structure their project experiences using the STAR method (Situation, Task, Action, Result).
-
-### Professional Insight (Top 1% Knowledge)
-
-The "Top 1%" of engineers view interview preparation not as a "hoop to jump through," but as a **re-hardening of their technical foundation**. A senior engineer knows that while they may not use a complex Dynamic Programming solution every day, the discipline required to solve one translates to better performance analysis and optimization in their production code.
-
-A professional habit is to focus on **patterns, not problems**. Instead of memorizing 500 individual LeetCode solutions, an expert masters the 15-20 underlying patterns. When they see a new problem, they don't look for a match; they look for the pattern.
-
-Another high-level tip is to **narrate your trade-offs**. During a mock interview or a real one, the "Top 1%" developer doesn't just provide a working solution; they proactively discuss why they chose a Hash Map over a Sorted Array, or what the memory implications of their recursion are. Understanding the why is what separates a "coder" from an "engineer." Finally, treat your interview preparation as a continuous baseline. Keeping your DSA skills sharp makes you a more versatile problem solver, regardless of whether you are actively job hunting.
-
-

docs/Desktop/learning/interview.md docs/Desktop/learning/interview/index.mddocs/Desktop/learning/interview.md renamed to docs/Desktop/learning/interview/index.md

@@ -46,9 +46,3 @@ Students will use Tipp10 to systematically build and maintain their typing speed
 *   **Custom Lesson Importing:** Pasting code snippets or technical documentation into Tipp10 to practice the specific symbols (brackets, braces, semicolons) that are common in programming but rare in standard prose.
 *   **Progress Tracking:** Analyzing accuracy and WPM trends to ensure they are making consistent improvements before moving to more advanced coding tasks.
 *   **Ergonomic Discipline:** Using the visual keyboard on-screen to ensure they never look at their physical keyboard, thereby building true muscle memory.
-
-### Professional Insight (Top 1% Knowledge)
-
-The "Top 1%" of productive engineers don't just type fast; they type **accurately**. In software development, a single character error (like a `:` vs a `;`) can lead to a bug that takes hours to find. A senior engineer knows that speed is useless if it necessitates constant backspacing. Use Tipp10 to focus on a 98% accuracy rate first; the speed will naturally follow as your muscle memory hardens.
-
-Another professional secret is the importance of **special characters**. Most typing tutors focus on the alphabet, but developers live in the symbols. A professional tip is to curate custom lessons containing heavy usage of `{}`, `[]`, `()`, `=>`, `&&`, and `||`. Mastering these symbols allows you to write complex logic smoothly without your hands ever leaving the home row. Finally, understand that typing is a perishable skill. Even senior engineers occasionally return to a tutor like Tipp10 when they switch to a different keyboard layout (like Dvorak or Colemak) or a specialized ergonomic keyboard, demonstrating that mastery requires continuous investment.

docs/Desktop/learning/tipp10.md

@@ -44,13 +44,3 @@ Students will use these tools to coordinate their learning and project work:
 *   **Infrastructure Integration:** Connecting Slack/Discord to GitHub or CI/CD pipelines to receive automated notifications when a build succeeds or a pull request is opened.
 *   **Local File Sharing (LocalSend):** Quickly moving a compiled binary or a large database dump from a development laptop to a testing machine or a mobile device.
 *   **Knowledge Sharing:** Using "Huddles" or voice channels for pair programming sessions and real-time debugging.
-
-### Professional Insight (Top 1% Knowledge)
-
-The "Top 1%" of developers use communication tools to **reduce their own cognitive load**. A senior engineer doesn't stay "online" and reactive all day. They use "Do Not Disturb" (DND) modes and scheduled notifications to protect their deep-work time. They understand that every "ping" is a context switch that breaks their flow.
-
-A professional habit is the rigorous use of **Threads and Mark-as-Unread**. Instead of cluttering a main channel with a long technical debate, an expert starts a thread to keep the history contained. Furthermore, they use communication tools as a **searchable archive**. When they solve a hard problem, they often post the solution in a public channel specifically so that "future themselves" or a teammate can find it months later using the search function.
-
-Finally, treat tools like LocalSend as a security utility. Using the cloud to move a sensitive `.env` file or an SSH key is a major security risk. A professional uses local, peer-to-peer encrypted tools to move sensitive credentials between their devices, ensuring that their secrets never leave their local network.
-
-

docs/Desktop/media/communication.md

@@ -50,10 +50,3 @@ Students will use VLC for more than just entertainment; it will serve as a techn
 *   **Frame-by-Frame Analysis:** Using the 'E' key to step through a video frame-by-frame, which is useful for debugging animations or analyzing visual timing.
 *   **Subtitle Synchronization:** Learning to manage and sync subtitle tracks, a common task in localization and accessible software design.
 *   **Network Protocol Testing:** Opening network streams to test the availability and performance of remote media servers.
-
-### Professional Insight (Top 1% Knowledge)
-
-Experienced engineers treat VLC as a **headless media processor**. One of the most powerful and underutilized features of VLC is its ability to be controlled entirely via the command line or through an HTTP/Telnet interface. A professional use case involves running VLC in "dummy interface" mode (`cvlc`) to automate media tasks or provide background audio/video services on a server.
-
-Another high-level skill is using VLC's **Stream Output (sout)** functionality. You can command VLC to transcode a file and stream it simultaneously to multiple destinations across a network. This allows an engineer to simulate a live broadcasting environment for testing real-time video processing applications. Understanding that VLC is a graphical wrapper around the powerful `libVLC` engine allows you to eventually integrate its capabilities directly into your own software, moving from a user of the tool to a developer who leverages its architecture.
-

docs/Desktop/media/vlc.md

@@ -41,10 +41,3 @@ Students will use Fluent Reader to build a disciplined habit of technical stayin
 *   **Following Industry News:** Monitoring sites like Hacker News or specialized technical newsletters that provide RSS feeds.
 *   **Tracking Security Vulnerabilities:** Subscribing to vulnerability feeds relevant to their development environment to stay informed about critical patches.
 *   **Categorizing Knowledge:** Grouping feeds into "Daily Reading," "Language Updates," and "Project Inspiration" to manage reading time effectively.
-
-### Professional Insight (Top 1% Knowledge)
-
-Experienced engineers treat their RSS feed as a **professional radar system**. They don't try to read every article; instead, they become experts at "scanning and filtering." The goal is not to consume everything but to develop a mental map of what is happening in the industry so that when a specific problem arises, they know where the solution was recently discussed.
-
-A professional tip is to integrate your RSS reader with your "read-it-later" or note-taking tools. If an article in Fluent Reader is exceptionally valuable, don't leave it there; move it to Readest for deep reading or Obsidian for permanent documentation. This creates a "knowledge pipeline" where information flows from discovery (Fluent Reader) to digestion (Readest) and finally to storage (Obsidian). Mastering this pipeline is what allows senior engineers to maintain a broad understanding of the tech landscape without feeling overwhelmed.
-