I started out writing PHP back in 2012 and never really stopped building for the web. These days I'm mostly in Node.js, Java and React/Next.js, and I spend a lot of time on the part before the code: figuring out how a system should be put together.
const ragib = {
role: "Full-Stack Engineer & Team Lead",
dailyStack: ["Node.js", "Java", "Spring Boot", "React", "Next.js", "TypeScript"],
architecture: ["system design (HLD & LLD)", "microservices", "micro-frontends"],
certified: "AWS Certified Generative AI Developer",
askMeAbout: ["system design", "scaling backends", "moving to Next.js", "Laravel"],
coffee: true,
};| Give me a whiteboard and a vague problem. I'll work out the services, data model, caching and queues, then go down to the classes and patterns so the code stays easy to change later. | Pulling big apps apart into pieces that can be built and deployed on their own, without freezing feature work while it happens. |
| Slow API? Heavy query? I like digging in with a profiler until it's fast and boring. | AWS Certified Generative AI Developer. I build LLM features on Bedrock and run things with Docker and Kubernetes. |
- Taking a messy requirement and turning it into a clean design and small PRs
- That one production bug nobody else wants to touch
- Designing APIs that other devs don't complain about
- Code reviews where both sides learn something
- Automating boring stuff. Lately that means a lot of pairing with AI agents
| Backend | |
| Frontend | |
| Data | |
| Cloud & DevOps | |
| Tools |
Most of my work lives in private repos, so this is more of a learning-in-public corner.
Always up for a good tech chat. Say hi on LinkedIn.