Sridhar Sambangi

I'm incredibly excited for this talk. Top K queries are the backbone of search engines, which have historically been NoSQL databases unable to execute JOINs. We're fixing this with ParadeDB. Highly recommend attending, I promise you'll learn something!

36

AI agents are task‑oriented tools built to execute predefined workflows, while agentic AI represents a deeper intelligence layer that reasons, plans, and adapts autonomously. In cloud environments, we already rely on agents through monitoring systems, autoscaling, and CI/CD pipelines. Agentic AI takes this further by enabling predictive, self‑optimizing, and collaborative systems that evolve with real‑time conditions. This shift moves us from reactive automation to truly adaptive cloud infrastructure. Credit: Dr. Anil Lamba

1

Stop exposing your Doctrine Entities to GraphQL. 🛑 If you are building Enterprise GraphQL systems with Symfony, tightly coupling your API to your database is the #1 architectural mistake I see. It kills flexibility and leaks implementation details. In my article, I break down how to architect a fully decoupled, type-safe system using Symfony 7.4 and PHP 8.4. We dive deep into:  ✅ The Decoupling Rule: Why you need DTOs (Data Transfer Objects) and how to map them efficiently.  ✅ Solving N+1: Practical strategies using Data Loaders and eager loading.  ✅ CQRS Mutations: Keeping your processors thin by dispatching Messenger messages.  ✅ Modern PHP: Leveraging PHP 8.4 Property Hooks for cleaner logic. This isn't just a "hello world" tutorial. It’s a blueprint for scalable logistics systems. Read the full guide here: 👉 [https://lnkd.in/dXmmVBsJ] 👉 [https://lnkd.in/d_3Y-hQp] #Symfony #PHP #GraphQL #SoftwareArchitecture #APIPlatform #WebDevelopment #EnterpriseSoftware

5

You didn’t become a CTO to manage HIPAA. But here you are. You signed up to build product. Ship features. Help the business scale. Solve the hard technical problems. Not interpret HIPAA. Not draft policies. Not respond to 100 question security reviews. But in growth-stage health tech companies, it lands with you. Because you understand the system. Because you care about doing it right. Because there isn’t a CISO to help. But here is how it starts to backfire. When compliance sits with the CTO by default: Engineering's time gets diverted into policy writing Security answers get written between deploys Regulatory interpretation becomes assumptions None of that is leverage. Compliance in healthcare can’t be treated as side task. It’s a critical operating function. It requires: Clear ownership. Executive visibility. Documented process. Confident communication with buyers. That doesn’t mean you step away from security. It means you stop being the bottleneck for it. Strong technical leaders don’t carry compliance alone. They invest in someone to structure it properly. So engineering can build. And leadership can answer with confidence. Let us help. We compiled our enterprise governance framework into a Strategic Compliance Guide. Access it here: https://lnkd.in/eDzziDwd

12

3 Comments

GPT Image 2.5 is live on ApexApi: Sunburst and Flare, five quality levels, one key OpenAI released GPT Image 2.5 on September 8, and both API models are now live on ApexApi: openai/gpt-image-2.5-flare openai/gpt-image-2.5-sunburst Same key, same endpoint as GPT Image 2. If you already generate images through us, switching is a one-string change. Both models are also in the model picker on the dashboard's Images page, with the new quality levels and the price of each one shown before you click generate. https://lnkd.in/eQiGN8pM

3

Read the new 300 plus page survey on code LLMs and agents so you do not have to. It is about how tools like Copilot, Cursor, Claude Code and others turn natural language into working code and reach over 95 percent success on standard benchmarks. Here is what actually matters for your team. 1. Make AI assistance the default, not the bonus The paper is clear. We already moved from manual coding to AI assisted and now to AI driven and even AI autonomous in the roadmap. If your engineers use Copilot only when they feel lazy, you lose. Set one standard workflow for everyone. Examples. Pair programming with a code model on every feature. Using natural language for small refactors. Let the model write the first draft and the human polish it. You get less boring work, fewer context switches and faster feature cycles. The good teams already treat code LLMs as part of the IDE, not as a toy. 2. Give the model full context of your system The survey keeps repeating one pain point. Real world projects fail when the model does not see enough of the codebase and the docs around it. So you need a proper code intelligence layer for the team. Search over the monorepo. Embeddings for services and APIs. Links to tickets, design docs, logs. Retrieval on top of that. Then the assistant can answer things like What is the real entry point for payments Where do we validate KYC How do we deprecate this feature safely Your people stop guessing and stop breaking hidden contracts between services. 3. Standard prompts plus serious evaluation The paper goes deep into prompting patterns like chain of thought and multi step planning, and then into new ways to evaluate code besides simple pass or fail. For a company this turns into two moves. First, create a small library of prompts for your stack. Example. Write unit tests in our usual style Refactor this into small functions and keep names stable Explain this file to a junior engineer Second, judge the output for more than correctness. Check clarity, performance, security, and how easy it is to maintain, just like the survey suggests for modern benchmarks. You get consistent output and you can finally trust what the tool gives your team. 4. Use agents for the boring multi step work One of the strong parts of the survey is agents. Systems that decompose tasks, call tools, fetch docs and move through several steps without a human holding their hand. This is where teams win big. Documentation generation. API client updates across many services. Mass refactors with tests. Project setup and scaffolding for new microservices. You do not want your best engineers to click through thirty files for the same pattern. You want one agent to do it and a human to review the final merge request.

3

3 Comments

This release includes our first phone integration. It is very cool. You get info popups on incoming calls with context, etc. 3CX is our first integration, and Yealink is coming next.

5

1 Comment