Ishant Agarwal

Senior Frontend Engineer. Ex-Agoda (Booking Holdings) · Makro Pro. Builds before the problem arrives. Real-time & AI-native UIs with React, TypeScript, Claude.

[Ishant Agarwal @ishantagarwal00]

I don't wait to be asked.

At Makro Pro, I integrated Claude Code into CI/CD before anyone asked, cutting PR cycle time by 30% and enforcing Core Web Vitals, design system, and accessibility checks on 100% of PRs before human review.

At Agoda, nobody had built multi-city flights. I owned the entire chain. Frontend, BFF, API contracts, release. It drove a 15% adoption lift across 68M+ annual tickets.

At Publicis Sapient, I kept Lloyds Banking Group's digital banking platform at 99.9% uptime for 8.1M users. Real money, no tolerance for downtime.

At WheelsEye, nobody asked me to bet on SEO. I took Lighthouse from 45 to 96 and scaled from 5,000 to 2M+ trucks.

Seven years. Same pattern.

Writing about real-time UI, AI-native engineering, and building before the problem arrives.

→ https://t.co/zcTvWKQ1ct
→ https://t.co/X7Va0cqu2t
→ https://t.co/fqt8sYHTxs
→ https://t.co/ZzMCuvd0gC

[Ishant Agarwal @ishantagarwal00]

@hackerrank failed in thier own test.

[Ishant Agarwal @ishantagarwal00]

@petarivanovv9 Weighted round robin is most popular among all. Isn’t it?

[Ishant Agarwal @ishantagarwal00]

Micro-frontends get blamed for problems that were already there.

The teams I've seen fail with them had coordination issues before they split anything. The architecture just made it visible faster.

The teams that succeeded had clear ownership and agreed boundaries first. The split came after, not before.

The architecture isn't the problem. Premature splitting is.

[Ishant Agarwal @ishantagarwal00]

@arpit_bhayani The read-only angle is the part worth sitting with. Most IDE features assume you're the one writing the code. Once agents are doing the writing, the tool you actually need is fast navigation and context, not another autocomplete layer.

[Ishant Agarwal @ishantagarwal00]

@CodeWithTamara Not stupid at all, most developers never touch a server directly. The moment it clicks is usually when something breaks in prod and you need to debug live. Then you never forget it.

[Ishant Agarwal @ishantagarwal00]

@NickpxJ They become the people who decide what gets built and why. Writing code was never the hard part. Knowing which problem is worth solving is.

[Ishant Agarwal @ishantagarwal00]

@lauraveyne The MCP and Agent Skills courses are the ones worth starting with. Most people go straight to the API and miss the architecture patterns that make agents actually reliable in production.

[Ishant Agarwal @ishantagarwal00]

@steipete The missing piece is that this works until it doesn't and you have no idea why it did. Agents fixing kernel-level issues via prompts are impressive until the next update silently breaks the same thing and the fix is different this time.

[Ishant Agarwal @ishantagarwal00]

@romxdev This is true for teams that adopt it before they have the team structure to justify it. At 3 squads shipping independently across different business verticals it's the only thing that kept us from blocking each other every sprint.

[Ishant Agarwal @ishantagarwal00]

@meetarno The architecture cleanup is worth it, but the pain usually comes from assuming the rewrite scope is fixed. Next.js migrations have a way of pulling in more than the UI layer once you start touching routing and data-fetching patterns.

[Ishant Agarwal @ishantagarwal00]

Vibe coding is great until it's in production.

The engineers defending it are building prototypes. The engineers criticizing it are cleaning up after someone else's prototype that became a product.

Both are right. Just talking about different stages.

[Ishant Agarwal @ishantagarwal00]

@Tech_p001 DELETE *

[Ishant Agarwal @ishantagarwal00]

@hijunedkhatri The ecosystem still needs good engineers though

[Ishant Agarwal @ishantagarwal00]

@capsraunak Frontend engineering has never been about designing though.

[Ishant Agarwal @ishantagarwal00]

@IamAroke The stack should be selected based on the problem to solve, not to create a new problem.

[Ishant Agarwal @ishantagarwal00]

Astra just made every "AI is just autocomplete" argument harder to make.

The gap between what engineers think AI can do and what it actually can do right now is getting embarrassing.

[Ishant Agarwal @ishantagarwal00]

And then people say frontend engineering isn’t complex 😂

[String @Stringcodes]

As a frontend engineer.

Please learn:

- JavaScript/TypeScript
- Responsive Design (CSS, Flexbox, Grid)
- Performance Optimization (lazy loading, code splitting, tree shaking, memoization)
- Web Security (CORS, XSS, CSRF,Content Security Policy, Secure Cookies)
- Testing (Jest, Cypress, Enzyme)
- Build Tools (Webpack, Vite, Babel)
- Version Control (Git)
- Browser DevTools & Debugging
-Accessibility (WCAG standards)
- Progressive Web Apps (PWA)
- Component Architecture (Atomic Design, Higher-Order Components)
- Micro Frontends
- API Integration (REST, GraphQL, WebSockets)
- Testing Strategies (Unit, Integration, End-to-End)
- CI/CD for Frontend (automated builds, deployments)
- Browser Rendering & DOM Optimisation
- WebAssembly (Wasm)
- UX/UI Design Collaboration
- Accessibility Audits (ARIA, screen readers)
- State Management (Redux, MobX)
- Frontend Framework Internals (eg: React Fiber for React, Angular Ivy for Angular)

[Ishant Agarwal @ishantagarwal00]

@merishabh_singh or by ONLYFANS

[Ishant Agarwal @ishantagarwal00]

@HaimantikaM @digitalocean What’s next?

[Ishant Agarwal @ishantagarwal00]

@danellisona AI’s hiring humans