"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints."
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password who needs a $5 wrench?
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password Please write a blog post on the feedback you got on this post. Was it universally negative? Did you learn anything?
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password Ah, so this deconstruction is why I have been getting to be almost daily system issue emails across the cloud stack which say they are for "scale issues" it's really you teasing out pieces then having to tape over the leaks?
There was an implicit trust when you dragged us from Dropbox/iCloud local sync to your cloud. You've expanded your product set outside your historical core business and now money and scale are meeting the monolith. I hope us customers survive.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password hint: the ideal "agent to human ratio" is 0. seeing a company jeopardise its reputation like this just to chase a trend is very disappointing.
-
@1password As a longtime 1Password user and software engineer, this article seriously undermines my confidence.
For security-critical software, AI should assist vulnerability discovery, with every finding rigorously validated by senior engineers, not drive development velocity.
I’d rather hear about how you are achieving reliability standards comparable to avionics or medical device software than excitement about AI-assisted coding.
@chadpod @1password So well said!
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password PLEASE could you GA Passkeys for logging into 1Password....
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password Alright, it was nice knowing you. Take care.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password Oh FUCK no.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password WTF? Just recently I decided to stay and accept your price increase, but THIS is definitely not acceptable.
Just canceled our family plan.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password In retrospect I'm so glad I didn't shell out for a 1Password account. The product looked solid, but clearly the company cannot be trusted with sensitive information.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
Actually, a good summary of the lessons. From the business and engineering perspectives, I have a few questions; How do you measure ROI? When is it advantageous for engineers to leverage LLMs, when would it be more beneficial to hire a new FTE?
Finally, how do you maintain engineer motivation, especially when LLMs can handle a significant portion of their work? And how do you ensure a consistent influx of junior engineers while also fostering their continued learning?
At the end of the day, LLMs are trained by data created by engineers. No engineers left == no data for LLMs to train.
Compared to others in the comments, I'm actually happy to see how you think about using LLMs within the organization.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password sounds to me like I need to re-evaluate storing sensitive information with 1Password… disappointing!
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password I'm sad that I can't trust you any more and need to find a new password manager.
At no point in this blog post did I see a serious justification for generating code with a system that you know makes mistakes.
Managerial FOMO isn't actually a good enough justification for your users to accept this.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password my subscription would be up to renew, but now i have six days to find another password manager. thsnks for that, i guess.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password I was a loyal customer who recommended you to everyone. I read about you in the physical Macworld magazine. But I guess I have to rescind that recommendation and cancel my subscription
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password I'm pretty sure that you're talking nonsense, because not only do I not understand what this means, but my partner, who is a software developer, also doesn't understand what this means. Telling agents to produce code using fixed seed values in the LLM, I suppose.
Using LLMs to produce code is just a bad idea. But using LLMs to produce code that people trust to be secure is a TERRIBLE idea.
A human CANNOT own all key decisions in the process unless the human is a developer who is free to develop the code independently, and however they see fit. When a developer's LLM use is mandated from the top down, the dev is forced to become 'responsible' for the LLM's mistakes. The dev is 'replaceable' after all, right?
My partner, who is a developer, is cancelling your service. I've never used your service myself, but I'll be warning everyone against you.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password Pfuh… lucky me that I recently switched to @protonprivacy Pass. However, this now forces me to also cancel my subscription for my family. Yayy now I can move all my family members to something else, that means many hours of explaining and work.
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password I'm so glad I don't depend on your software
-
Unfortunately, they too are doing this:
GitHub - bitwarden/ai-plugins: AI plugin marketplace.
AI plugin marketplace. Contribute to bitwarden/ai-plugins development by creating an account on GitHub.
GitHub (github.com)
-
"The pattern that works is using agents to produce deterministic artifacts, then forcing execution through those constraints." Tido Carriero, VP of Engineering at Cursor.
At 1Password, we applied agentic tooling to B5, our multi-million-line Go monolith, to help plan and execute a production refactor. Here's what we learned: https://1password.com/blog/what-we-learned-using-ai-agents-to-refactor-a-monolith
@1password
Please don't.As a 10+ year customer, I'm asking you: please don't use genAI / LLMs / "AI" in your product.
