CEO at Graftcode, Creator of Javonet, Co-founder/CTO at SdNcenter, Software Engineer, Software Architect

San Francisco, CA
Joined May 2011
Guys is Graftcode better version of gRPC?
1
71
Przemysław Ładyński retweeted
😂 Frontend & Backend are in couples therapy! Therapist: “How many layers are between you?” Frontend: “DTOs, mappers, API gateways…” Backend: “And don’t forget versioned endpoints!” 💀 Then comes Graftcode: What if your frontend could call backend methods like local functions? 👀 Less boilerplate. Less drama. More shipping. 🚀 🎥 Watch the therapy session 👇 youtube.com/watch?v=oKApRA_s… #WebDev #Frontend #Backend #Graftcode #API #SoftwareEngineering #DeveloperHumor
1
2
1
9
909
Przemysław Ładyński retweeted
AI made code cheaper. So companies are building more of it. Cost per feature ↓ Total software spend ↑ The Jevons paradox, applied to AI-assisted dev 👇
2
1
10
1,752
Przemysław Ładyński retweeted
What a great day at THE MOAT by Hard2beat! 🚀 Our founders @pladynski and Łukasz had the opportunity to showcase Graftcode with a live demo on stage and connect with investors and founders from across the ecosystem. #Graftcode #THEMOAT #Startups #EnterpriseAI #DeveloperTools
2
1
10
900
Any simpler way to get MCP?
Your next AI tool might already be in your backend. Graftcode turns exposed public methods into MCP tools—without hand-written tool wrappers. What would you let an AI agent call first? See how: graftcode.com/use-cases/mcp
12
That is really easy!
The Graftcode YouTube channel is live! Explore hands-on demos of strongly typed communication, cross-language execution, microservices, and AI agents through MCP. Less integration plumbing. More building⚡ ▶️ youtube.com/@Graftcode #DeveloperTools #AIEngineering #AIAgents
22
Przemysław Ładyński retweeted
The Graftcode YouTube channel is live! Explore hands-on demos of strongly typed communication, cross-language execution, microservices, and AI agents through MCP. Less integration plumbing. More building⚡ ▶️ youtube.com/@Graftcode #DeveloperTools #AIEngineering #AIAgents
2
2
10
2,011
Przemysław Ładyński retweeted
this is one of those things that makes you realize how far dev tools have come. ❌ before: hours of AI integration glue code ✅ now: expose the methods already living in your codebase @Graftcode turns ordinary public class methods into MCP tools through its gateway. slick.
🤝 Paid partnership
With Graftcode, you can expose your methods to LLMs without writing any additional layer. MCP works out of the box, with support for JavaScript, C#, Java, and Python. Less code. Faster integrations. More time building. Link in comments 👇
2
15
25
5,540
Przemysław Ładyński retweeted
Test it, and here is the result
1
1
5
406
🚀 graftcode CLI just got even better! Our CLI now supports downloading plugins! Windows iwr grft.dev/get | iex Linux / macOS curl -fsSL grft.dev/get | sh Easily add Service Bus or RabbitMQ plugins, reference them in your Graft & Graftcode Gateway config. Route all communication through queues, scale out your solution, while keeping remote service calls as simple local functions! 🔥 By removing integration-specific code from your codebase, you can adopt AI-assisted dev workflows in distributed systems — dropping token consumption by 50% and simplifying diffs in AI-created pull requests, as presented at WeAreDevelopers 2026. graftcode.com #Graftcode #DevTools #Microservices #WeAreDevelopers
2
7
118
Guys! What’s the best way to gather early adopters to evaluate new dev tool that literally just killed REST, gRPC, Thrift, SignalR, DAPR and GraalVM in one shot?
1
48
🚨 AI Coding has a HUGE problem… and nobody’s talking about it! 🔥 Microsoft gave thousands of engineers the most powerful tool (Claude Code) — and quietly canceled the licenses a few months later. Uber burned through its entire yearly AI budget by April. Even Nvidia (the ones making the AI chips) revealed their team’s compute costs now exceed what they pay employees! Why? Because AI works too well. It generates code at lightning speed, but context, tokens, and integrations eat millions. Context windows get bloated, and you’re paying every time the AI has to re-learn your entire stack. In this video, RoadsideCoder breaks it down with a real SaaS example (Next.js + Supabase + AI APIs): • Why model selection is everything (not always Opus!) • How context reconstruction eats 40-60% of your tokens • Tools like Graftcode that actually help If you’re building with AI agents — you NEED to watch this. Link in comments / below. This isn’t FUD. This is 2026 reality. AI speeds up development 10x… but the bills do too. 💸 Who’s already feeling these “hidden costs” in their projects? Drop a comment 👇 #AICoding #AIagents #HiddenCosts #DeveloperLife #TechTwitter
1
2
3
51
Przemysław Ładyński retweeted
That’s why Graftcode is interesting for AI-assisted development. The hard part is not only generating code. It’s keeping the service context intact while frontend, backend, and cloud services talk to each other. Graftcode is built for that integration layer: less manual wiring, fewer tokens burned, and backend logic available directly where you need it. Beta quick-start: academy.graftcode.com/quick-…
3
8
414