Replace profile README with requested bio, specialties, OSS contributions, and featured writing

[Copilot]

This updates the profile README.md from the default template to the exact requested content: a personal intro, satirical “Specialties,” Ray contribution highlights, and featured technical articles. The goal is to publish the provided profile narrative and links verbatim.

• Scope

  • Replaced the existing placeholder/profile-template content in README.md with the provided markdown block.
  • Preserved the requested structure and formatting (section dividers, headings, bullets, emojis, and inline code formatting).

• Content added

  • Intro paragraph and personal background.
  • ## 🛠️ My "Specialties" section.
  • ## 📦 Open-Source Work: Ray Contributor section with 4 PR links.
  • ## 📝 Technical Articles & Data Science section with 3 Medium links.

• Representative excerpt

  # Hi, I'm Adel Nour
  
  I am an aspiring PhD student who just graduated from **NYU Tandon** (with a Math minor)...

Original prompt

Put this in the README.md
"# Hi, I'm Adel Nour

I am an aspiring PhD student who just graduated from NYU Tandon (with a Math minor), specializing in Computational Neuroscience. Because reading neural time-series data isn't painful enough, I do heavy software engineering and distributed systems work on the side to scratch the itch.

When I have free time, I actively contribute to ray-project/ray or read big books that are hard to understand.

---

🛠️ My "Specialties"

• Scalability over usability: If it doesn't require a distributed cluster to compute a linear regression, I don't want it.
• 103% CPU usage: Maximizing process efficiency by making my local cooling fans sound like a jet engine.
• Running large jobs on login nodes: The ultimate life hack. Keeps my cluster fair-share (sshare) metric low while ruining the day for everyone else SSH'd into the cluster.
• AI force push and pray: Letting my AI fix my colleagues AI slop code.
• Fudging ML accuracy at all costs: Tuning is expensive, so I optimize performance by seamlessly leaking my training data directly into my test validation loop.
• Never doing PRs on local fixes: If it works on my local machine's specific path layout, it's ready for production.
• Stating "STEM is dead": Threatening to give up and switch to poetry, but still finishing my math problems and manually debugging dependency issues until 3:00 AM.

---

📦 Open-Source Work: Ray Contributor

When I am practicing real, disciplined engineering, I target the Ray ML tuning and dependency layers:

• [In Review] #63547 Docs: Python Dependency Guide: Added a developer guide mapping Ray's 3-layer dependency graph, uv conflict resolution workflows, and cross-platform architecture edge cases.
• [Merged] #60522 Modernize AxSearch API to 1.x: Upgraded core tuning infrastructure for ax-platform 1.0+ compatibility and strict error handling.
• [Closed] #62596 Split ci_docgpu CPU/GPU depsets: Restructured dependency lockfiles to isolate and resolve complex pip-compile version clashes (+pt27cpu vs +pt27cu128).
• [Closed] #62471 Fix Conda PermissionError on Windows: Isolated container-build race conditions caused by in-place conda update behavior during runtime cleanup.

---

📝 Technical Articles & Data Science

Featured Writing

• 🌍 2 Ways of Analyzing Geographic Culture Through X API v2 + British LLM [Award Winner]: An award-winning architectural blueprint on scraping, filtering, and passing regional social telemetry for culture mapping.
• 🐳 How You Can Make PySpark Work Across Docker, Singularity, and HPC: A deployment manual on bridging heavy enterprise JVM ETL layers across containers and environments (especially for high-performance computing clusters).
• 💻 Fastest Guide to macOS Terminal Setup: Autocomplete, Aliases & Colors: A no-nonsense guide for optimizing Zsh workflows, setting robust aliases, and establishing terminal visual structure.