It was a pleasure to be part of the Laravel Ahmedabad Community meetup! 🙌
I had a great time sharing my thoughts on how we can debug issues faster across different layers of an application, using the right tools and techniques for each layer with tools like Promotheses, SlqWatch and OwlTrace (https://t.co/XUwIZ6uGGU). 🚀
Special thanks to everyone who made this event possible! Looking forward to more opportunities to learn, share knowledge, and grow together as a developer community. 🙌
#Laravel #Debugging #AI #WebDevelopment #DeveloperCommunity
Festive season, Sunday morning, and a packed house! 🐘✨
Thanks to everyone who joined, and to our speakers @ankit_builds (all the way from Chandigarh!), @BarochiaVa7670, and @sudolaravel.
Thank you @ZealouSys for hosting & Ravi bhai for the venue! 🙌
Tomorrow morning! Three talks, one community. 🐘
- @ankit_builds on modern debugging
- @BarochiaVa7670 on Laravel performance tuning
- @sudolaravel on AI decision models
📅 Sunday, Oct 25 | 10:00 AM (Check-in: 09:45 AM)
📍 @ZealouSys, Prahlad Nagar Ahmedabad.
Final passes 👇
Sunday plans for the local Laravel crowd: tech talks first, chai and banter after. ☕💻
Catch @ankit_builds in town from Chandigarh and @BarochiaVa7670 at @ZealouSys, Prahlad Nagar Ahmedabad!
Grab your seat:
https://t.co/mmKzIlmF2S
Sort your Sunday morning tech catch-up before the weekend chai run! ☕🐘
Two solid sessions at @ZealouSys:
• Real-world Laravel debugging with @ankit_builds (Chandigadh)
• App profiling and query tuning with @BarochiaVa7670
📅 Oct 25, 10 AM
Passes 👇
https://t.co/nnqeuMpjIq
Excited to be joining everyone in Ahmedabad this Sunday! 🚆🙌
Looking forward to sharing my insights on debugging, tracing queries and using AI responsibly.
Can’t wait to connect with the community and learn together. See you all there! 🚀
#Laravel#PHP#Ahmedabad
Big welcome to @ankit_builds joining us from Chandigarh this Sunday! 🚆
He will talk about debugging Laravel apps, tracing queries, investigating queue failures, and working with AI responsibly.
Register here:
https://t.co/mmKzIlmF2S
🦉 Athene is getting a Dashboard!
Notes, todos, meetings, and activity - all in one place.
I’m building Athene to reduce app switching and make everyday work feel effortless.
The dashboard is the next step. More visibility, less friction.
Still building. More soon. 🚀
#BuildInPublic #IndieHacker #Productivity
An LLM isn't an AI agent. It's one component of the system.
Building reliable Agentic AI requires more than prompts:
🧠 LLM = Brain
🛠️ Tools = Actions
⚙️ Harness = Orchestration
🔄 Loops = Feedback
🔗 Graphs = Coordination
🔍 Tracing = Observability
🛡️ Guardrails = Safety
The real challenge? Turning probabilistic outputs into reliable software.
#AgenticAI
Working on AI agents has changed how I think about building AI systems.
After working on AI agent systems, these are 5 things that stand out:
1️⃣ Better models ≠ Better agents
Poor context, weak tool design, and missing validation can make even the best models unreliable.
2️⃣ Context is everything
Memory, RAG, conversation history, and tool outputs directly influence an agent's decisions.
3️⃣ Tool execution needs guardrails
Sandboxing, permission boundaries, and human approval aren't optional when agents can execute commands or modify data.
4️⃣ Failure handling is part of the architecture
Tool execution → Validation → Retry → Recovery.
An agent that can't recover from failure isn't production-ready.
5️⃣ More agents ≠ Better results
A single agent with a well-designed workflow can be cheaper, easier to debug, and more predictable than a multi-agent system.
My biggest takeaway?
Building AI agents isn't just about connecting an LLM to tools.
It's about engineering a system that can reason, act, validate, and recover safely.
The model is only one component. The real engineering happens around it.
What has been your biggest challenge while building AI agents?
#AIAgents #AIEngineering #LLM #SoftwareArchitecture
Your AI agent might be wasting money without you realizing it.
Every new message can resend the same context.
Prompt caching lets the model reuse that context instead of charging full price every time.
The catch?
Change the cached prefix → cache miss → full input cost.
AI cost optimization isn't only about choosing a cheaper model.
It's also about designing your context correctly.
@PovilasKorop Now I’m building a quick meeting, todo and notes tool, so we can easily chat, take notes, and come back to the conversation later.
https://t.co/AutFjX7R3E
@PovilasKorop Started https://t.co/F8SpD8bdOz Months ago, I built a feedback tool for myself.
Now, a few QA teams and small businesses are using it too, especially those tired of going back and forth with clients asking:
“Where did the issue happen?”
“Which url were you on?” and on on...
After 4–5 hours of discussion, it’s genuinely perplexing when someone still asks:
“Any updates?”
Bro… the discussion was the update. 😅
Sometimes the real progress is thinking, debating, clarifying, and figuring out what actually needs to be done.
One thing that often confuses developers in Next.js:
'use client' doesn’t mean “browser only.”
Server Components → fetch data and handle server-side logic.
Client Components → handle interactions, state, and browser APIs.
The important part: Client Components can still be rendered on the server first.
Server → HTML → Hydration → Interaction
Once you understand this flow, Next.js becomes much easier to reason about.
#NextJS #React #WebDevelopment #JavaScript
@enunomaduro@tavus This reminds me of a tool I built about 2 years ago for Socratic learning for kids, using HeyGen and Gemini STT. Feels like it was way ahead of its time 😄
Has anyone else experimented with building something similar?
🦉 Athene 1.0.8 now on macOS
• Links review in the widget
• Notifications: daily todo summary
• Better phone/email parsing (fewer false positives)
• Composer drafts persist across crashes & restarts
Work smarter from the edge of your screen.
https://t.co/AutFjX7R3E