"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
Please don’t. Password management is one place I want as little stochastic parroting as possible. At the very least, stop fucking BRAGGING about how you’re using the plagiarism engine to make your tool less secure. Yours is just about the only tool I still trust even a little. -
And no, it's not magic, it's not 'intelligent', it's a predictive algorithm, trained with data built by actual creative and smart human beings.
Just another tool.
gfl with that
-
@TeflonTrout @1password AI is a tool. Ignore it at your peril.
pfff
-
If that is the kind of problem you enjoy working on, we are hiring.
abattoir with a sign outside saying "hiring professional farm animals".
@ret @1password
I know fedi well enough to know that'd get a looooot more interest !!!! -
"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 Well, thanks for feeding my blocklist with sloppy techbros I guess.
️ -
@1password there are a whole lot of responses to this that show me they didn’t read the article. Thanks for sharing your experiences!
They seem to require cookies in order to show their blog post, so it's not surprising that some folks didn't read the blog.
-
They seem to require cookies in order to show their blog post, so it's not surprising that some folks didn't read the blog.
@RandomOxen @1password those people probably didn’t need to comment then
️ -
@RandomOxen @1password those people probably didn’t need to comment then
️People rarely need to comment, but we do anyway.
It's not surprising that a 1Password customer -- who read the toot and then was blocked from reading the details -- would react negatively.
-
People rarely need to comment, but we do anyway.
It's not surprising that a 1Password customer -- who read the toot and then was blocked from reading the details -- would react negatively.
@RandomOxen @1password people are welcome to jump to conclusions. Doesn’t make them right
️ -
"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 cancelled my 1Password sub when you guys jumped on the crypto bandwagon a few years ago. Not doing a very good job at convincing me to come back.
-
"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. I see. Well you are definitely not a consideration for moving password managers. Go fuck yourselves.
-
@1password Bye. Dropping this service immediately. Good job giving me a reason to move my family plan away. Time to check on ChiPass progress.
@cararemixed @1password slowly but steadily we're progressing towards the first release
-
@RandomOxen @1password people are welcome to jump to conclusions. Doesn’t make them right
️I think you might be thinking naívely here. Or I might be. It's hard to say.
When information is being withheld, people -- rightly -- use their knowledge and experience to fill in the gaps.
They shouldn't be expected to be silent, even if they fill those gaps incorrectly.
People don't operate like that.
-
They seem to require cookies in order to show their blog post, so it's not surprising that some folks didn't read the blog.
You have the option to reject cookies and still read the blog as soon as you open the page.
-
I think you might be thinking naívely here. Or I might be. It's hard to say.
When information is being withheld, people -- rightly -- use their knowledge and experience to fill in the gaps.
They shouldn't be expected to be silent, even if they fill those gaps incorrectly.
People don't operate like that.
@RandomOxen @1password I’m not seeing a cookie block. And even if it’s blocked like that, everyone here seems to be claiming to be a customer, so I thought they might owe the company a little more grace than just reading the headline. But again, you’re right, people can and will jump to conclusions. That still doesn’t make them right.
-
@cararemixed @1password slowly but steadily we're progressing towards the first release
@whitequark @1password I've got a local clone already and have been following. This just triggered an earlier migration than I planned.
-
@whitequark @1password I've got a local clone already and have been following. This just triggered an earlier migration than I planned.
@cararemixed @1password probably the biggest challenge right now is delivering high-assurance release builds for multiple platforms. it's happening but it is taking quite a bit of effort to build that infrastructure (and associated things like signing with an HSM) on top of Codeberg
-
@RandomOxen @1password I’m not seeing a cookie block. And even if it’s blocked like that, everyone here seems to be claiming to be a customer, so I thought they might owe the company a little more grace than just reading the headline. But again, you’re right, people can and will jump to conclusions. That still doesn’t make them right.
I suspect now that it's my block on site data / local storage that prevents the page from loading.
-
"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 you’re on very shaky ground. This wouldn’t make me cancel yet, but it will make me start evaluating some pros and cons of other password managers as a “just in case”. I’ll want to know where to go when I hear of 1Password’s first major breach.
-
"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 WTH
