Software Developer || Devops Engineer
I am a passionate and results-driven Software Developer & DevOps Engineer with a strong interest in building a clean and maintainable codebase. With hands-on experience across the full development lifecycle, from planning and design to implementation and deployment, I specialize in developing clean performant code and automating robust infrastructure workflows. I thrive at the intersection of software engineering and DevOps practices, where I can streamline processes, improve reliability, and accelerate delivery cycles. I’m always seeking new opportunities to impact meaningful projects, work with talented teams, and continue growing at the forefront of technology.
Markdown supported · ⌘↵ to post
Velocity gains from AI vanish when review debt piles up. I cap open AI pull requests so the team finishes one batch before the next wave lands.
Kartik N V J K
The N x M integration problem framing is exactly why MCP took off, but the security side deserves equal space. I evaluate every MCP server my agents touch against a short checklist, tool descriptions that overstate scope, missing rate limits, and endpoints that accept arbitrary paths, because a malicious server can steer the agent through its own tool descriptions. I wrote my full checklist here: kartiknvjk.hashnode.dev/how-i-evaluate-mcp-server… . How do you sandbox servers you did not write yourself?