Amrutesh Naregal DragonEmperor9480

Amrutesh Naregal

DragonEmperor9480

backend • cloud • android • open source
building Go backends, AWS-heavy tools, and politely asking production not to explode

Go, AWS, Docker, Kubernetes, Flutter, Linux, REST APIs, and a healthy disrespect for flaky deployments.

Writing Go backends with REST APIs and concurrency so systems can fail in a more organized way
Doing suspicious amounts of AWS work with S3, IAM, Lambda, and DynamoDB
Building Android and Flutter stuff and learning new ways mobile can be personally disrespectful
Spending an unreasonable amount of time with Linux, infra, containers, and configs that looked harmless
Messing with custom ROM and low-level Android things because one layer of chaos was apparently not enough
Trying very hard to keep production boring while letting side projects make terrible life choices

Backend things I willingly do: Go, Node.js, Python, REST APIs
AWS things I keep summoning: EC2, S3, IAM, Lambda, DynamoDB
Infra things that occasionally test my character: Docker, Kubernetes, Linux, Git, Shell
Mobile and frontend things I argue with professionally: Flutter, React, Android, HTML, CSS, Tailwind
Other languages I can work with without causing a national incident: Dart, JavaScript, Java, Kotlin, C++

I could pretend this README is the museum and everything is carefully curated.

It is not.

The actual chaos, experiments, working stuff, broken stuff, and "why did I build this at 2 AM" energy lives in the repositories.

Because apparently "trust me bro" is not an industry standard.

If you want to talk backend, infra, Android, Linux, or the emotional consequences of one bad config change, I am around.