# recipe Published articles for recipe. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## OWASP Top 10 Agents & AI Vulnerabilities (2026 Cheat Sheet) DevFeed: [OWASP Top 10 Agents & AI Vulnerabilities (2026 Cheat Sheet)]() Original publisher: [Read original article]() Author: Alex Ewerlöf Published: 2026-03-10T18:18:04Z Content type: tutorial Language: en Sources: [Alex Ewerlof Notes]() Topics: [Vulnerabilities](), [Large Language Model](), [Artificial Intelligence](), [prompt injection](), [Security & Privacy]() Tags: [ai](), [llm](), [prompt-injection](), [recipe](), [security](), [security-privacy](), [techniques](), [vulnerabilities]() ### AI overview A pragmatic engineering guide examines the OWASP Top 10 for LLMs and the OWASP Top 10 for Agents. It explains how mixed instructions and data, unpredictability, agentic attack surfaces, reliability failures, cascading failures, and high LLM costs create security and operational risks, with examples and mitigations. ### Source excerpt A pragmatic engineering guide and cheat sheet for the OWASP Top 10 AI, OWASP Top 10 LLM, and OWASP Top 10 Agents vulnerabilities ## Using Provocations to Shake the Status Quo DevFeed: [Using Provocations to Shake the Status Quo]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2025-07-22T16:23:11Z Content type: opinion Language: en Sources: [New York Times]() Topics: [Users](), [format](), [context]() Tags: [approach](), [design](), [engineering](), [figma](), [photography](), [process](), [recipe](), [ux-design](), [visual-hierarchy](), [visualization]() ### AI overview A case study of how NYT Cooking used high-fidelity design provocations to rethink recipe cards. The approach prioritized photography, flexible recipe information, a modernized format, and a more streamlined evaluation process while keeping the project scope controlled. ### Source excerpt The bold approach NYT Cooking used to define a strategy for recipe cards.Illustration by Ben Denzer By Jayne Lee In The New York Times Cooking, "cards," or the containers that represent our content, are the first impression of our brand. They're the window into our recipes and users rely on them to evaluate and choose what to cook. NYT Cooking users are particularly attracted to our appetizing food photos. In every research session, participants get distracted by a delicious-looking dish while answering the moderator's questions. People tend to browse with their stomachs first and then see if the recipe specifications meet their personal criteria (For example, do I have enough time to cook this?). A problem we encountered: our beautiful photography was muddied by the page's gray background. The white card containers sitting on top of the gray page forced your eyes to focus on the container instead of the photo. The visual hierarchy was at odds with the preferred reading and browsing order of our audience: photo first, then recipe information. Recipe information varies, so the card needs to afford that variability. Using containers forced us to keep our cards the same height, resulting in unnecessary whitespace. Since the cards were so tall, this limited the amount of recipes a user could see at once, increasing the time users scanned for recipes. We needed to highlight our photography, modernize the format and streamline the recipe evaluation process. While designing solutions, I realized that I had more questions than answers. Answering each question would have significantly bloated the project scope. Some examples were: What order of recipe information is most helpful when deciding between recipes? Are recipe bylines important? Which presentation of ratings is more effective? Because the priority was to update the format rather than improve comprehension, and to avoid bloating the scope of the project, I started with design provocations over design specs. Because