Skip to content
View MiladShd's full-sized avatar
🐈
Shipping!
🐈
Shipping!
6 followers · 8 following

Block or report MiladShd

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
MiladShd/README.md
Animated experiment log showing repeated attempts and lessons

Featured work

Qalib

Private · Unfinished · Not live

OSS Radar

Open-source ecosystem intelligence

Lyn URL

URL shortening experiment

Proteus

Private browsing on public networks

Pinned Loading

  1. MiladShd MiladShd Public

    founder. data engineer. building AI dev infrastructure.

  2. validate.py — Run pytest + ruff + ba... validate.py — Run pytest + ruff + bandit on any Python project. AI can write code. This checks if the code is worth shipping.
    1 
    #!/usr/bin/env python3
    2 
    """
    3 
    validate.py — Run quality gates on any Python project directory.
    4
    5 
    AI can write code. This checks if the code is worth shipping.
  3. The Orchestration Gap — why AI codin... The Orchestration Gap — why AI coding tools create a productivity illusion, and what's actually missing
    1 
    # The Orchestration Gap
    2 
    
              
    
              
    
                3
                
    > AI can generate code. But generating code isn't shipping software.
    
              
    
              
    
                4
                
    
              
    
              
    
                5
                
    A Fortune 500 firm declared their engineers "ten times more productive" after adopting AI coding assistants. Code output tripled. PR volume shot up 60%. The CTO presented the numbers to the board. They revised headcount downward.
    
              
    
          
    
    
    
  
    

    4. 

      

  4. 
  
    
    
    
      
    
        
        Hands-on response to CVE-2025-1974 i...  Hands-on response to CVE-2025-1974 in ingress-nginx — secure upgrade from unmanaged to Helm-managed controller in a live Kubernetes cluster.      
    

          
    
              
    
                1
                
    # 🛡️ CVE-2025-1974 — Ingress-nginx Critical Vulnerability Remediation
    
              
    
              
    
                2
                
    
              
    
              
    
                3
                
    > This is a personal log of how I secured my Kubernetes cluster from one of the most critical ingress-nginx CVEs disclosed in 2025.
    
              
    
              
    
                4
                
    
              
    
              
    
                5
                
    ## 🧠 The Story
    
              
    
          
    
    
    
  
    

    5.