---------------Under Construction ----------------
public class Voodles {
private final String role = "Backend Engineer";
private final String[] focus = {"Distributed Systems", "System Design", "Clean Architecture"};
private final String philosophy = "Understand how things work internally, not just how to use them.";
public void currentlyExploring() {
System.out.println("Java β’ Spring Boot β’ GraphQL β’ PostgreSQL β’ Redis β’ Docker β’ Linux");
}
}I'm an engineering student obsessed with backend engineering and production systems. I don't just want to write code that works β I want to understand why it works, how it scales, and where it breaks.
| Area | What I'm Deep Into |
|---|---|
| Backend Development | RESTful APIs, GraphQL, Microservices |
| Production Engineering | Monitoring, Observability, SRE Practices |
| System Design | Scalable architectures, CAP theorem, consensus |
| Performance | JVM tuning, caching strategies, query optimization |
| Clean Architecture | Domain-driven design, hexagonal architecture, SOLID |
"Coming soon β building things worth showing."
| Project | Description | Stack | Status |
|---|---|---|---|
| π In Progress | Distributed task queue system | Java, Redis, Docker | dev |
| π Planning | GraphQL API with Spring Boot | Spring Boot, GraphQL, PostgreSQL | design |
I document everything I learn. My notes cover:
- ποΈ Backend Architecture β Microservices, event-driven design, API patterns
- β Java Internals β JVM, garbage collection, concurrency, memory model
- π GraphQL β Schema design, resolvers, performance optimization
- π± Spring Ecosystem β Spring Boot, Spring Data, Spring Security
- ποΈ Databases β PostgreSQL internals, indexing, query optimization, Redis patterns
- ποΈ System Design β Load balancing, caching, rate limiting, distributed consensus
Platform: Codeforces / LeetCode / AtCoder
Focus: Data Structures, Algorithms, Graph Theory
Goal: Consistent problem solving to sharpen analytical thinking
"The best engineers are the ones who understand the systems they build β not just the frameworks they use."



