Remove featured work section from README

Removed featured work section detailing cloud-native e-commerce and DevSecOps platforms.

Author: vishalgunjalSWE

README.md

@@ -131,83 +131,6 @@ I architect and implement complete cloud-native systems, not just tutorials or t
 
 ---
 
-## 📚 Featured Work
-
-### 1️⃣ [Cloud-Native E-Commerce Platform](https://github.com/vishalgunjalSWE/cloud-native-retail-platform)
-**Production-grade microservices on AWS EKS**
-
-**What makes this different:**
-- 8 independent microservices with proper domain boundaries (DDD principles)
-- Event-driven architecture preventing cascading failures
-- Multi-AZ infrastructure with automated failover
-- Distributed caching reducing database load
-- Full observability with correlation IDs for request tracing
-
-**Architecture Decisions:**
-```
-Why RabbitMQ over Kafka?
-→ Simpler ops for project scale, better routing patterns, DLQ support
-
-Why Redis cache-aside pattern?
-→ Handles cache misses gracefully, prevents stampede on cache clear
-
-Why IRSA over hardcoded credentials?
-→ Temporary credentials, automatic rotation, AWS IAM integration
-
-Why GitOps with ArgoCD?
-→ Git as audit trail, automated drift correction, declarative state
-```
-
-**Tech:** Go, Java, Node.js | Kubernetes (EKS) | Terraform | ArgoCD | RabbitMQ | Redis | Prometheus | Grafana | Jaeger
-
-**Skills Demonstrated:**
-- Microservices decomposition
-- Event-driven architecture
-- Distributed caching strategies
-- Kubernetes security (RBAC, Network Policies, Pod Security)
-- Infrastructure as Code (Terraform modules, remote state)
-- GitOps automation
-- SRE observability (RED metrics, SLOs, distributed tracing)
-
----
-
-### 2️⃣ [Enterprise DevSecOps Platform](https://github.com/vishalgunjalSWE/wanderlust-devsecops-gitops)
-**Shift-left security with automated CI/CD and observability**
-
-**What makes this different:**
-- Reusable pipeline logic (Groovy shared libraries)
-- Security scanning at multiple stages (SAST, container, IaC)
-- Centralized logging with request correlation
-- Infrastructure drift detection and remediation
-- DORA metrics tracking for continuous improvement
-
-**Architecture Decisions:**
-```
-Why Jenkins shared libraries?
-→ DRY principle, standardized pipelines, easier maintenance
-
-Why ELK over CloudWatch?
-→ Better aggregation, custom dashboards, correlation IDs, cost control
-
-Why scheduled drift detection?
-→ Catch manual changes, enforce GitOps, prevent config drift
-
-Why Infracost integration?
-→ Cost awareness before apply, prevent bill shock, FinOps culture
-```
-
-**Tech:** Jenkins (Groovy) | Terraform | SonarQube | Trivy | ELK Stack | ArgoCD | Prometheus | Grafana
-
-**Skills Demonstrated:**
-- CI/CD pipeline engineering
-- Shift-left security (DevSecOps)
-- Centralized logging and correlation
-- Infrastructure automation
-- Cost optimization awareness
-- Platform observability
-
----
-
 <!-- ## 📝 Technical Writing
 
 I write in-depth technical articles explaining the "why" behind infrastructure decisions: