Explore top LinkedIn content from expert professionals.
Summary
Chat-Oriented Programming (CHOP) is an emerging field where users interact with software applications through natural language conversations instead of traditional buttons or menus. In 2025, CHOP trends highlight the shift towards smarter, more adaptive chat interfaces that let people ask questions, take actions, and reshape app experiences by simply chatting with AI-powered tools.
Rethink app interfaces: Design applications to support conversation-driven actions, allowing users to perform complex tasks or change settings just by asking.
Invest in upskilling: Encourage your team to learn prompt engineering and experiment with new agentic tools, so they’re comfortable working alongside AI-powered assistants.
Review security practices: Prepare for increased AI access by updating security, governance, and policy guidelines to safely integrate chat-based agents into your systems.
Enterprise VC-engineer-company builder. Early investor in @databricks, @tubi and 6 other unicorns - @cohesity, @eightfold, @turing, @anyscale, @alation, @amperity, | GP@Foundation Capital
By the end of 2025 AI chatboxes will feel as dated as the command line.
Foundation models are reaching parity faster than anyone expected. GPT-4, Claude, and Llama 3 now match on key benchmarks.
The challenge now is user experience.
Enterprises need more than a simple chatbox to work with AI effectively.
They need tools to:
→ Monitor models in production
→ Debug reasoning paths when things break
→ Work together to improve AI outputs
A basic chat interface can't handle these needs. Each use case requires its own specialized interface.
Anthropic and OpenAI treat AI outputs as drafts to refine, not final answers. NotebookLM is a great example of text and voice blending seamlessly in multimodal interactions.
But we're going to need more creative solutions: dashboards, visual tools, canvases - design choices based on a deeper understanding of how effectively humans can partner with AI.
We made AI work. Now let's focus on making it *work for humans.*
I find I now *expect* a half pane chat & agentic experience in every application - and get frustrated when it's not there. Static UI is dead! A new intelligent & adaptive paradigm is in.
I no longer want to click through dropdowns, hunt for filters or leave to ask a question, do analysis. I expect to ask complex questions, take actions, and even transform the UI—all through natural language. The best companies are creating this expectation for all e.g.,
❓ Ask complex questions (e.g, give me talking points for the slides in this presentation Perplexity)
🙋 Perform actions through chat (e.g., buy this baby gift for and address the gift card to <name>)
🔢 And of course reshape the UI itself (Vercel V0, Replit, Lovable)
Even established platforms need to adapt!
Concourse lets users “chat with NetSuite”—and that’s just the beginning.
Soon, users will expect all systems to not just respond… but also to act.
If you're building a product in 2025, it's worth asking:
How does your UI listen, and even evolve?
If you are an "incumbent" - how will you adapt?
I have been lucky enough to talk to a lot of smart folks in the codegen space recently. Startups, enterprises, VCs, etc. I was asked a thoughtful question today that I figured would be good to share: what three things should a development team be doing to prepare for assistive or agentic code generation tools?
Here are my three suggestions:
1. Invest in understanding the state of the art w/ assistive tools. Copilot is cool, but Cursor is fricken magic. You probably want to find a way to use Cursor if you can make it work for you. These capabilities get better the more integrated it is into your environment. This is a space you are going to need to invest in keeping abreast of, so carve off dedicated resources to get and stay smart.
2. Training is imperative. This isn't a 'build it and they will come' moment. As amazing as the capabilities are, curiosity isn't free, and especially not in an organization that is under execution strain.
i) Update your training resources and agenda to include content on how to not only use codegen tooling (e.g. being security aware) but to make them really shine and get the most out of them. Create incentives for use of the tools. Create space for people to play (genai hackathons, etc).
ii) The optimal skill profile of your engineering team is going to change. Everyone should have some familiarity w/ prompt engineering, understand the patterns of genai systems etc. You should also recognize that curious generalists w/ codegen tools (and general genai chops) are going to have an edge on traditional specialists (e.g. pure-play front end engineer) in this new world. Help your team become curious generalists that are powered by assistive and agentic tools.
3. Start paving the way for an agentic future. While assistive tools are incredibly powerful, the IDE is not going to be the right point of integration for value creation in the future. Agents are going to need to access code, docs, data and potentially production system control planes and will be well situation to operate asynchronously. CHOP (chat oriented programming) is going to become a thing. Start paying attention *now* to what operational, security, policy, governance and other concerns need to be worked through to start allowing agentic systems access to sensitive systems. There is tremendous power there, but there also be dragons. Starting thinking about this now because it is going to be a heavy lift but the value creation will be disproportionate and you will be out competed by your competitors if you are badly behind.
What are your three things?