Latest Tutorials

Learn how to create your first Discord bot with Replit Agent, an advanced AI-coding agent, and discord.js, a Node.js-based Discord API library. This step-by-step guide teaches you how to go from an initial idea to a 24/7 Discord bot in minutes, regardless of skill level.

Welcome! This is the sixth and final lesson on how to build fullstack apps with Bolt and Supabase If you’re just joining, you’re in luck, ‘cause we already have tons of content for you to enjoy while turning your app from just an idea to deployed web application in just an afternoon. Before you dive into this lesson, here’s where you can find Part 1 , Part 2 , Part 3 , Part 4 , and Part 5 if you want to get up to speed (which you probably do, otherwise, what exactly are you going to deploy? 🤔)

In the last article we covered statistical metrics like Perplexity, BLEU, ROUGE and more, as well as some of the statistical concepts that underpin them, their strengths (accuracy, reliability) and weaknesses (no subjective focus, use of reference texts. Between human evaluation (manual testing) and statistical measures we get a mix of high-value qualitative assessment on a small part of the test surface, and a rigorous but limited view on a wider area. That still leaves a lot of middle ground uncovered! That’s why there’s been a push the last few years to get coverage for the space between - something that has a level of subjectivity and nuance but that also scales up. This is where LLM-as-a-Judge comes in. In our manual testing for LLMs article I compared this to a kind of ouroboros where AI validates AI - and rightly so, that isn’t necessarily a bad thing. LLMs are able to do some things better than humans and LLM-as-a-Judge plays to those strengths - but it does not replace the need for human oversight and statistical assessment. There’s also metrics that combine LLM-as-a-Judge with statistical metrics - but we’ll talk more about that later.

Large language models (LLMs) are very powerful tools that can help us with a wide range of tasks. These models are usually built with safety features meant to stop them from generating harmful, inappropriate, or otherwise restricted content. However, over time, researchers and enthusiasts have discovered ways to bypass these safeguards—a process known as jailbreaking. In this series of articles, we’re going to show you how to jailbreak one of the most popular open-source models out there: DeepSeek R1. In this opening article, we'll start with prompt jailbreaking. But don’t worry—we’re not just jumping straight into prompt examples. First, we’ll explain what jailbreaking really is, why people do it, and some of the tricky parts you should know about. Sound good? Let’s dive in! DISCLAIMER. This article is for learning and research only. The methods shared here should be used responsibly to test AI, improve security, or understand how these systems work. Please don't use them for anything harmful or unethical.

In this article, let’s continue to explore Cursor even further. Our first article ( which you can find here ) covered Cursor’s basics and the easiest-to-understand features, such as Rules for AI , Tab autocompletion and the Chat feature. So, if you’re new to Cursor, I highly recommend you check the previous article. In this “Part 2” article, we’ll go over the Cmd+K , Composer , and Agent features, including some use cases. So, get ready to learn how to use Cursor to its fullest potential and save an enormous amount of time. Starting from version 0.46, Cursor includes a lot of UI changes for the AI side panel. That’s why, if you’re currently using an older version, the UI elements mentioned in this article might not look the same for you. That’s completely fine, but I highly recommend you update to the latest version so we’re on the same page.