Software Engineer | Forever Learning | Building Cool Stuff
Crafting efficient solutions with Go, Python, Django & AWS
type Developer struct {
Name string
Focus []string
CurrentBuild string
Learning []string
Passion string
}
me := Developer{
Name: "Milon Mahato",
Focus: []string{"Backend Engineering", "System Architecture", "Cloud Architecture"},
CurrentBuild: "jobber - Distributed job queue system in Go",
Learning: []string{"Advanced Go Patterns", "AWS Infrastructure", "DevOps"},
Passion: "Building tools that make developers' lives easier",
}
π¨ Currently Building: jobber
β A distributed job queue system in Go with retry logic
π± Always Learning: Advanced Go patterns, AWS IaC with Terraform, and CLI distribution
π― Mission: Creating efficient, scalable solutions that solve real problems
Languages & Frameworks
Go βββββββββββ 80% Python βββββββββββ 95%
Django βββββββββββ 90% JavaScript βββββββββββ 60%
π ezlang
CLI tool for Django (mainly) localization powered by AI
π§ Tech: Go, AWS Translate, Django
π¦ Features: Automated translation, CLI interface, Django integration
β Impact: Streamlines i18n workflow for developers
Distributed job queue system in Go
π§ Tech: Go, Redis, Docker
π¦ Features: Retry logic, distributed processing, monitoring dashboard
β Goal: High-performance job processing with fault tolerance
High-performance URL shortening service
π§ Tech: Go, Postgres, AWS, Redis
π¦ Features: Serverless architecture, analytics, custom domains and more
2025_Goals:
- Ship jobber v1.0 with production-ready features
- Evolve ezlang into a comprehensive i18n toolkit
- Contribute meaningfully to 5+ open source projects
- Achieve AWS/Cloud architecture proficiency
- Craft powerful developer tools using Go
Learning_Queue:
- Go concurrency mastery (channels, goroutines, patterns)
- AWS CDK & cloud-native infrastructure design
- Distributed systems & microservices architecture
- Performance profiling & optimization techniques
"Code is like humor. When you have to explain it, it's bad." β Clean, efficient solutions over clever tricks.
I believe in:
- π― Purpose-driven development β Every line should solve a real problem
- π§ Tool creation β Building CLIs and utilities that improve developer experience
- π± Continuous learning β Technology evolves, so should we
- π€ Community contribution β Sharing knowledge through open source