© 2025 Praveen Puri
Sunday, March 8, 2026
Monday, February 16, 2026
Will Companies Use AI to Replace SaaS Subscriptions?
Like most decisions, it's not black or white. Bigger companies (especially in regulated industries like health care or finance) are not going to write their own versions of ERP or HR software because of complexity, regulatory, and compliance requirements.
But smaller companies that need a "lite" version of a SaaS, might write their own, unless they target this need.
Also, in this period of turbulent change, if SaaS companies don't keep up with the evolving needs of their customers, and large gaps open up between what they offer and what the clients need, they will be more tempted to create their own apps.
Friday, February 13, 2026
Using AI to Code: Context Engineering vs. Vibe Coding
The way software engineers are using AI to code now (context engineering) is very different from "vibe coding" by non-developers.
With vibe coding, someone might ask, "create a sales website," and it might work, but not have security, stability, etc. issues.
With context engineering, developers first think through the approach with AI (including security, stability, scaling, etc), get the agent to document what they discussed, then close the agent, and open a fresh one, to clear out the old memories.
This is the key. They manage the context (info in the agent's memory) to keep it from filling up and containing different ideas. This limits hallucinations and keeps them focused on one task.
Then, they ask the fresh one to use the design to come up with the plan. After the detailed plan, with check boxes, is developed, they have it written out, and then shut the agent.
Then, they run a loop where a new agent is spawned, works on one item, checks it off, creates notes for its successor, then shuts it down, and spawns a fresh one (with no memory) to read the notes and take off from where the previous one left off. It's thus a fully automated, but controlled process.
© 2025 Praveen Puri
With vibe coding, someone might ask, "create a sales website," and it might work, but not have security, stability, etc. issues.
With context engineering, developers first think through the approach with AI (including security, stability, scaling, etc), get the agent to document what they discussed, then close the agent, and open a fresh one, to clear out the old memories.
This is the key. They manage the context (info in the agent's memory) to keep it from filling up and containing different ideas. This limits hallucinations and keeps them focused on one task.
Then, they ask the fresh one to use the design to come up with the plan. After the detailed plan, with check boxes, is developed, they have it written out, and then shut the agent.
Then, they run a loop where a new agent is spawned, works on one item, checks it off, creates notes for its successor, then shuts it down, and spawns a fresh one (with no memory) to read the notes and take off from where the previous one left off. It's thus a fully automated, but controlled process.
© 2025 Praveen Puri
Monday, January 19, 2026
Strategic Simplicity® #34
Your PMO isn’t fixing chaos. It’s institutionalizing it.
© 2025 Praveen Puri
Sunday, January 18, 2026
Most Valuable Skill in 2026?
The most valuable skill in 2026 isn’t writing code; it’s the ability to articulate the problem clearly enough that an AI can solve it.
© 2025 Praveen Puri
© 2025 Praveen Puri
Subscribe to:
Comments (Atom)