正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Introducing: Sazabi (Sazabi). The AI-native observability platform for fast moving engineering teams. Backed by engineering leaders from the world's top AI and dev tool companies: Graphite, Vercel, Browserbase, LangChain, Browserbase, and more. Sazabi is taking a radically different approach to observability, centered on three core principles: 1. LESS IS... MORE Product engineers don't need more observability bells and whistles. They need clear, actionable answers. The best UX for observability is chat. 2. LOGS ARE ALL YOU NEED The "Three Pillars of Observability" is an outdated idea. Logs can do everything traces can do, and more. 3. MONITORING IS DEAD Creating static monitors for fast-evolving systems is a fool's errand. The future is something different entirely: agentic anomaly detection. I started Sazabi out of desperation. After years of working on observability systems at Crunchbase, Brex, and 11x, I was all too familiar with the toil and complexity. Dashboards. Monitors. Session recordings. Error tracking. APM. RUM. Instrumentation. OpenTelemetry. Endless screens and configuration. It was too much. And despite everything, my teams still struggled to find and fix production issues. I was fed up. I dreamed about a better way. AI makes it possible. Today, I'm proud to introduce Sazabi to the world and announce our closed alpha program. We're selecting 10 startups to participate. Learn more:show more

Sherwood

5,674 subscribers

117,900 次观看 • 8 个月前 •via X (Twitter)

教育科学技术

Anya Rossi• Live Now

Private livecam show

61 条评论

AJ Stuyvenberg 的头像

AJ Stuyvenberg8 个月前

@sazabi Congrats on the launch, and welcome to the arena!

Sherwood 的头像

Sherwood8 个月前

@sazabi We’re coming for ya :)

matt palmer 的头像

matt palmer8 个月前

@sazabi let’s go! 🔥

verrsane 的头像

verrsane8 个月前

@sazabi LFGGGGG BRO IS LOCKED IN

Sherwood 的头像

Sherwood8 个月前

@sazabi I'm solo leveling like my name is Jinwoo

verrsane 的头像

verrsane8 个月前

@sazabi bro gonna be observability final boss

Brace 的头像

Brace8 个月前

@sazabi

Sherwood 的头像

Sherwood8 个月前

@sazabi LFG!!!

Luke Harries 的头像

Luke Harries8 个月前

@sazabi Congrats Sherwood!

eric provencher 的头像

eric provencher8 个月前

@sazabi Wish you luck! Though I will say, as a native app builder, stack traces to spot hangs and pinpoint crashes, are essential. Logs alone don’t cut it for that.

Sherwood 的头像

Sherwood8 个月前

@sazabi Do you catch your exceptions and log the stack traces?

eric provencher 的头像

eric provencher8 个月前

@sazabi That's not always possible with swift. Sometimes it hard crashes. Also some issues involve performance tuning. If the app hang hangs, sentry can log that and I can see where the code got stuck.

Sherwood 的头像

Sherwood8 个月前

@sazabi > If the app hang hangs, sentry can log that and I can see where the code got stuck. Then Sazabi can do the same, right?

Nick Khami 的头像

Nick Khami8 个月前

@sazabi let's goooooo!!! congrats on the launch

Shrey Pandya 的头像

Shrey Pandya8 个月前

@sazabi double 🅱️ed up

Sherwood 的头像

Sherwood8 个月前

@sazabi 🅱️ang 🅱️ang

Utsav 的头像

Utsav8 个月前

@sazabi Let's gooo!!!! 🔥

arush 的头像

arush8 个月前

@sazabi i read sabzi

Sherwood 的头像

Sherwood8 个月前

@sazabi Say it with me: "Sa-za-bee"

J_N 的头像

J_N8 个月前

@arcinston @sazabi Gundam reference intended

Sherwood 的头像

Sherwood8 个月前

@arcinston @sazabi 👀

annie xue 的头像

annie xue8 个月前

@sazabi Sick!! Excited for this. It’s a monster of a problem 🫡

Matt Slotnick 的头像

Matt Slotnick8 个月前

@sazabi lfg!!!!

Justin Torre 的头像

Justin Torre8 个月前

@sazabi Goated edits

Sherwood 的头像

Sherwood8 个月前

@sazabi I've got a guy 😎

Edward 的头像

Edward8 个月前

@sazabi yall hired a model for this video?

Sherwood 的头像

Sherwood8 个月前

@sazabi Do you mean an AI model

Ethan Lim 的头像

Ethan Lim8 个月前

@sazabi huge

Josh 的头像

Josh8 个月前

@sazabi So excited for this one

Sherwood 的头像

Sherwood8 个月前

@sazabi We are long GEPA!

Sherwood 的头像

Sherwood8 个月前

@browserbase x2. Whoops! 🤡

Henry Ventura 的头像

Henry Ventura8 个月前

@sazabi looking at logs ("log-looking") is a way for a couple of like-minded local individuals to get together, have fun, and frankly? have a good time.

Paul Klein IV 的头像

Paul Klein IV8 个月前

@sazabi Congrats on launching Sherwood!

Sherwood 的头像

Sherwood8 个月前

@sazabi Thank you!

anita 的头像

anita8 个月前

@sazabi let's gooo - congrats man!

Sherwood 的头像

Sherwood8 个月前

@sazabi Glad to be out in the open! :)

darren 的头像

darren8 个月前

@sazabi let’s goo

Shannon Code 的头像

Shannon Code8 个月前

@sazabi Seems like this and sentry would play quite nicely with this Ai Debugger I built

Sherwood 的头像

Sherwood8 个月前

@sazabi Seems super cool. Our team is really interested in debuggers. They have a lot of potential in the post-AI world!

Shannon Code 的头像

Shannon Code8 个月前

@sazabi How can I help? I have shown this to a handful of people and I get blank stares, then I realized that there multiple generations of developers that have never used a breakpoint.

Ali Basharat 🇵🇰🇪🇸 的头像

Ali Basharat 🇵🇰🇪🇸8 个月前

@sazabi You have been cooking for a long time. Finally a great idea and best of luck to you

Alp 的头像

Alp8 个月前

@sazabi Lfgg

Adi Singh 的头像

Adi Singh8 个月前

@sazabi congrats sherwood!

Jack Needham 的头像

Jack Needham8 个月前

@sazabi generational company

Sherwood 的头像

Sherwood8 个月前

@sazabi Generational friendship

Kaz Tamai 的头像

Kaz Tamai8 个月前

@sazabi Congrats Sherwood🔥

Lindsay 的头像

Lindsay8 个月前

@sazabi lfg!

Robert 的头像

Robert8 个月前

@sazabi how in the world would you build latency stats from logs alone?

Sherwood 的头像

Sherwood8 个月前

@sazabi It's a secret

Linda Chen 的头像

Linda Chen8 个月前

@sazabi Browserbase mentioned twice wow we must be special

Sherwood 的头像

Sherwood8 个月前

@sazabi Just a big fan of @pk_iv

GEAUX.eth ✝️📺🟩 的头像

GEAUX.eth ✝️📺🟩8 个月前

@sazabi @0xSinaver - helpful?

Mark Attar 的头像

Mark Attar8 个月前

@sazabi your website is gorgeous

Sherwood 的头像

Sherwood8 个月前

@sazabi YOU are gorgeous

Mark Attar 的头像

Mark Attar8 个月前

@sazabi lmao thank you

Sherwood 的头像

Sherwood8 个月前

@sazabi 🤣 Thank you for the support my man!

pskai 的头像

pskai8 个月前

@sazabi @shcallaway looks very promising. Being a dev for 15+ years this exciting to see. Congratulations :)

Sarbjeet Johal 的头像

Sarbjeet Johal8 个月前

@sazabi Good idea. Execution and focus will matter the most!

Sherwood 的头像

Sherwood8 个月前

@sazabi We have both in spades!

Sarbjeet Johal 的头像

Sarbjeet Johal8 个月前

@sazabi Then you folks will be unstoppable! ALL THE BEST!

Saïd Aitmbarek 的头像

Saïd Aitmbarek8 个月前

@sazabi based platform guys! we need more observability than ever agentic products & platforms poppin' every day. let's launch/spotlight you guys on anytime helpful btw

相关视频

Most underrated skill today: Observability. I feel you can build a career just on this and have 2 decades of guaranteed money if you learn the skill well, and I'll tell you how below. Reality: Most teams I help look at me with dead eyes when I ask them about observability. That's sad, but it's the current state of the industry: • No tracing • No structured data • No way to understand what's happening when things break Outside of the most sophisticated companies, that's still where most teams are. AI is now writing a ton of code, and people are shipping this code to production. However important observability was before, it is 10x more important today. Believe me, you don't want to be the one pushing slop into production and then guessing how it works, with no way to understand what happens. Here is your first step: Honeycomb is running a FREE, 3-day virtual event focused entirely on observability. The event is running May 12-14. Did I mention it's completely free? Everything will revolve around observability for the agent era. Register here: Thanks to the Honeycomb.io System Status Updates team for partnering with me on this post.

Most underrated skill today: Observability. I feel you can build a career just on this and have 2 decades of guaranteed money if you learn the skill well, and I'll tell you how below. Reality: Most teams I help look at me with dead eyes when I ask them about observability. That's sad, but it's the current state of the industry: • No tracing • No structured data • No way to understand what's happening when things break Outside of the most sophisticated companies, that's still where most teams are. AI is now writing a ton of code, and people are shipping this code to production. However important observability was before, it is 10x more important today. Believe me, you don't want to be the one pushing slop into production and then guessing how it works, with no way to understand what happens. Here is your first step: Honeycomb is running a FREE, 3-day virtual event focused entirely on observability. The event is running May 12-14. Did I mention it's completely free? Everything will revolve around observability for the agent era. Register here: Thanks to the Honeycomb.io System Status Updates team for partnering with me on this post.

Santiago

20,041 次观看 • 5 个月前

I miss building simple, working software. At some point, we decided to complicate everything for no reason. Today, people can't build anything without using three frameworks, 17 libraries, and a swarm of microservices. And here is a funny paradox: To understand how these complex systems work, we've had to build systems and tools that generate data we can later analyze. But the more data we produce, the harder it is to process and make sense of it. We are in the middle of an observability crisis. The tools we have are inefficient, and we don't have enough people to keep systems running. A few weeks ago, I met the team Resolve AI, and they have built a fundamentally new approach to observability and incident management: Instead of depending on humans to run a system, Resolve built a Production Software Engineer who runs the system using AI while letting people supervise. And it's not only crazy, but I think this will fundamentally change how we monitor and maintain systems in production for years to come. I recorded a quick video to showcase a simple example of how Resolve works behind the scenes. There are two main things I'd like you to notice: 1. The tool can correlate data across logs, metrics, and traces coming from different systems. You don't have to do any work to get the information that matters right in front of you. 2. (This is the big one!) The tool can diagnose what's happening and give you instructions on how to solve it. It can produce causal relationships across the entire system stack. Resolve is backed by investors like Replit's founder Amjad Masad, Reid Hoffman, Jeff Dean, Fei Fei Li, Andy Price, among others. They are currently working with a select number of companies and want to onboard a few more. If you are interested in trying them out, go to this link: Honestly, this is one of the most impressive uses of AI I've seen.

I miss building simple, working software. At some point, we decided to complicate everything for no reason. Today, people can't build anything without using three frameworks, 17 libraries, and a swarm of microservices. And here is a funny paradox: To understand how these complex systems work, we've had to build systems and tools that generate data we can later analyze. But the more data we produce, the harder it is to process and make sense of it. We are in the middle of an observability crisis. The tools we have are inefficient, and we don't have enough people to keep systems running. A few weeks ago, I met the team Resolve AI, and they have built a fundamentally new approach to observability and incident management: Instead of depending on humans to run a system, Resolve built a Production Software Engineer who runs the system using AI while letting people supervise. And it's not only crazy, but I think this will fundamentally change how we monitor and maintain systems in production for years to come. I recorded a quick video to showcase a simple example of how Resolve works behind the scenes. There are two main things I'd like you to notice: 1. The tool can correlate data across logs, metrics, and traces coming from different systems. You don't have to do any work to get the information that matters right in front of you. 2. (This is the big one!) The tool can diagnose what's happening and give you instructions on how to solve it. It can produce causal relationships across the entire system stack. Resolve is backed by investors like Replit's founder Amjad Masad, Reid Hoffman, Jeff Dean, Fei Fei Li, Andy Price, among others. They are currently working with a select number of companies and want to onboard a few more. If you are interested in trying them out, go to this link: Honestly, this is one of the most impressive uses of AI I've seen.

Santiago

82,074 次观看 • 2 年前

Today, we're making Error Tracking by Better Stack generally available. Sentry-compatible. AI-native. At 1/6th the price. Here's why we built it, and how to get the most out of it. What's wrong with error tracking today? Most teams use Sentry. It's solid! But at scale, the bills get brutal. Just 100M exceptions with 90 day lookback? ~$30,000 on Sentry. We charge ~$5,000 for the exact same thing. The math isn't subtle. And so most teams still end up sampling. Which means missing the exact exception that caused the outage. The bigger problem: errors are orphaned data. Your exception lands in Sentry. Your logs are in Datadog. Your traces are somewhere else. Root cause analysis becomes a multi-tab archaeology project at 3 am. We built error tracking natively inside Better Stack: the same platform where your logs, traces, metrics, uptime checks, and on-call schedules already live. Errors are just another signal. They belong together. The part that changes how your team works: Our AI SRE doesn't just surface errors. It fixes them. See a new exception? One click. The AI SRE analyzes the full context, from stack traces, environment variables, browser sessions, related logs and recent deploys, and opens a pull request. Not a ticket. Not a summary. A pull request with the fix. This is what happens when error tracking is fully integrated with the rest of your observability stack instead of bolted on separately. The AI has everything it needs to actually act. The migration is trivial: 1. Keep your existing Sentry SDK. Don't touch a single line of instrumentation code. 2. Point the DSN at Better Stack. 3. Done. Errors flow in. Your dashboards work. Your alerts work. 4. New exception appears. Click "Fix with AI SRE." Pull request lands in your repo. 5. Review, merge, close. That's the whole workflow. The AI angle is real, not a marketing badge. LLMs are genuinely good at fixing bugs if they have full context. The reason AI coding assistants sometimes frustrate engineers is incomplete information, not the model. We solve that by giving the AI SRE your entire telemetry stack as context. Stack traces, logs, traces, service maps, previous incidents and much more. All of it, in one place, at the moment it matters. Observability tools are only useful if you actually ingest all your data. At current prices of other tools, most teams can't afford to. Now you can, and your AI SRE can actually do something about it.

Today, we're making Error Tracking by Better Stack generally available. Sentry-compatible. AI-native. At 1/6th the price. Here's why we built it, and how to get the most out of it. What's wrong with error tracking today? Most teams use Sentry. It's solid! But at scale, the bills get brutal. Just 100M exceptions with 90 day lookback? ~$30,000 on Sentry. We charge ~$5,000 for the exact same thing. The math isn't subtle. And so most teams still end up sampling. Which means missing the exact exception that caused the outage. The bigger problem: errors are orphaned data. Your exception lands in Sentry. Your logs are in Datadog. Your traces are somewhere else. Root cause analysis becomes a multi-tab archaeology project at 3 am. We built error tracking natively inside Better Stack: the same platform where your logs, traces, metrics, uptime checks, and on-call schedules already live. Errors are just another signal. They belong together. The part that changes how your team works: Our AI SRE doesn't just surface errors. It fixes them. See a new exception? One click. The AI SRE analyzes the full context, from stack traces, environment variables, browser sessions, related logs and recent deploys, and opens a pull request. Not a ticket. Not a summary. A pull request with the fix. This is what happens when error tracking is fully integrated with the rest of your observability stack instead of bolted on separately. The AI has everything it needs to actually act. The migration is trivial: 1. Keep your existing Sentry SDK. Don't touch a single line of instrumentation code. 2. Point the DSN at Better Stack. 3. Done. Errors flow in. Your dashboards work. Your alerts work. 4. New exception appears. Click "Fix with AI SRE." Pull request lands in your repo. 5. Review, merge, close. That's the whole workflow. The AI angle is real, not a marketing badge. LLMs are genuinely good at fixing bugs if they have full context. The reason AI coding assistants sometimes frustrate engineers is incomplete information, not the model. We solve that by giving the AI SRE your entire telemetry stack as context. Stack traces, logs, traces, service maps, previous incidents and much more. All of it, in one place, at the moment it matters. Observability tools are only useful if you actually ingest all your data. At current prices of other tools, most teams can't afford to. Now you can, and your AI SRE can actually do something about it.

Juraj Masar

15,134 次观看 • 6 个月前

Gokul explains why outcome-based software companies like Zendesk are more exposed to AI than systems of record like NetSuite, and why public markets are not distinguishing between the two. He argues that the only way AI-native startups can disrupt systems of record is by spending 1-2 years building migration tools to get data off of incumbent platforms. "The software companies that should be the most worried right now is where they are pricing the product based on utility. Zendesk is a good example. Instead of paying for 50 Zendesk seats, you can pay for 20 and I can have 30 AI agents sitting next to Zendesk. For these companies you need to change your pricing model to be based on outcome. It's going to be hard for them to stay public. The companies that are less exposed are ones based on data that has been collected and captured over a period of time. ERP is a great example. There is no compelling reason for someone to put their career at stake by ripping out NetSuite. NetSuite has more time to build AI agents on top of it because they have the data, they can train the AI agent on top of it and bundle it. I think the public markets do not distinguish between these two types of companies."

Gokul explains why outcome-based software companies like Zendesk are more exposed to AI than systems of record like NetSuite, and why public markets are not distinguishing between the two. He argues that the only way AI-native startups can disrupt systems of record is by spending 1-2 years building migration tools to get data off of incumbent platforms. "The software companies that should be the most worried right now is where they are pricing the product based on utility. Zendesk is a good example. Instead of paying for 50 Zendesk seats, you can pay for 20 and I can have 30 AI agents sitting next to Zendesk. For these companies you need to change your pricing model to be based on outcome. It's going to be hard for them to stay public. The companies that are less exposed are ones based on data that has been collected and captured over a period of time. ERP is a great example. There is no compelling reason for someone to put their career at stake by ripping out NetSuite. NetSuite has more time to build AI agents on top of it because they have the data, they can train the AI agent on top of it and bundle it. I think the public markets do not distinguish between these two types of companies."

Patrick OShaughnessy

394,361 次观看 • 8 个月前

Do Trainers Take Too Much Credit?? The older I get, the more I understand that training is a piece of the puzzle for players or teams. Early on in my career I thought it was everything, and that a players success was my success. A players success is their success, and all the different people in their lives are there to hopefully help guide them. When I realized that, I became a better trainer because I realized I was serving them and not my own ego.

Do Trainers Take Too Much Credit?? The older I get, the more I understand that training is a piece of the puzzle for players or teams. Early on in my career I thought it was everything, and that a players success was my success. A players success is their success, and all the different people in their lives are there to hopefully help guide them. When I realized that, I became a better trainer because I realized I was serving them and not my own ego.

Steve Dagostino

36,675 次观看 • 2 年前

AI is rapidly evolving, and it’s reshaping how and where computing happens. From data center infrastructure to AI systems in the physical world, to the future of personal AI devices, intelligence is being distributed across a new compute landscape. At the edge, more agentic experiences are starting to show up, expanding what devices need to do. Tomorrow in New York, we’ll share what Qualcomm is building across it and how it will drive our next phase of growth. Stay tuned for #QCOMInvestorDay.

AI is rapidly evolving, and it’s reshaping how and where computing happens. From data center infrastructure to AI systems in the physical world, to the future of personal AI devices, intelligence is being distributed across a new compute landscape. At the edge, more agentic experiences are starting to show up, expanding what devices need to do. Tomorrow in New York, we’ll share what Qualcomm is building across it and how it will drive our next phase of growth. Stay tuned for #QCOMInvestorDay.

Cristiano R. Amon

15,783 次观看 • 3 个月前

MyKeep is officially live 💙 MyKeep is a private and a safe visual space for everything you save - literally everything that usually end up scattered across different apps and folders 🤌 The idea was simple: save everything in one place, organize it smartly (that you don't even have to organize) in your way, and actually find it again when you need it. Today, My Keep is now open as Beta V1 to everyone 💙 It's now available to everyone with an awesome stable version with more and more crazy features, and there is a lot more coming (you would never think of), but it is ready for people to start using and shaping with their feedback. The trailer will show you : What MyKeep is, Why I built it, and the kind of experience I want it to become. Start saving at: 🚀

MyKeep is officially live 💙 MyKeep is a private and a safe visual space for everything you save - literally everything that usually end up scattered across different apps and folders 🤌 The idea was simple: save everything in one place, organize it smartly (that you don't even have to organize) in your way, and actually find it again when you need it. Today, My Keep is now open as Beta V1 to everyone 💙 It's now available to everyone with an awesome stable version with more and more crazy features, and there is a lot more coming (you would never think of), but it is ready for people to start using and shaping with their feedback. The trailer will show you : What MyKeep is, Why I built it, and the kind of experience I want it to become. Start saving at: 🚀

Vinay Juneja

10,940 次观看 • 2 个月前

AI Mocap tools are evolving at breakneck speed... and I could find more than 10 all compiled and compared in a list you can get by subscribing to the XR AI Spotlight newsletter (link on top of my profile). This is Cartwheel and the stepping on that box was one of the most solid I saw. There is a bit of floatiness in the feet and they are not perfectly grounded, but since I tested the tool, the team has pushed massive improvement. What AI mocap tool do you use in your workflow? Let me know in the comments

Gabriele Romagnoli

34,994 次观看 • 10 个月前

Multi-agent systems offer incredible potential and unprecedented risks. How do you solve for observability, failure mode analysis, and guardrailing in the era of agents? Today, we’re announcing our Agent Reliability platform to observe, evaluate, guardrail, and improve agents at scale. You can get started with the complete platform for trustworthy agentic AI today for free, and here’s how we’re solving some of the biggest challenges in agent reliability: - Observability redesigned for agents Trace views collapse under complex workflows, so we created the Graph View, Timeline View, and Conversation View to offer rich, intuitive visualizations of agent decisions, tool calls, and conversation flows. This multi-dimensional approach enables teams to pinpoint exactly where and why agents deviate or fail. - Automated Failure Mode Analysis with our new Insights Engine Our Insights Engine ingests your logs, metrics, and agent code to automatically surface nuanced failure modes and their root causes. But knowing the problem is not enough; you need to know how to fix it. Insights Engine delivers actionable fixes and can even apply them automatically. With adaptive learning, your insights become smarter and more relevant as your agents evolve. - Evaluating Agents Across Multiple Dimensions Agentic systems interact across complex pathways, and evaluating their performance requires new metrics that reflect this increasing complexity. To deliver comprehensive agentic measurements, we’ve added more out-of-the-box agent metrics like flow adherence, agent flow, agent efficiency, and more. For specialized domains and unique workflows, custom metrics powered by our new Luna-2 small language models can be rapidly designed and fine-tuned for your specific use case. - Real-Time Guardrails Powered by Luna-2 As AI agents become more autonomous and complex, failures like hallucinations or unsafe actions increase dramatically. Without real-time guardrails, these errors will hurt your user experience and brand reputation. Our Luna-2 family of small language models is purpose-built to provide low-latency, cost-effective guardrails that actively stop agent errors before they happen. With support for out-of-the-box and custom metrics, Luna-2 enables enterprises to enforce safety, compliance, and reliability at scale. Enterprises running hundreds of agents and processing hundreds of millions of queries daily already rely on Galileo’s Agent Reliability platform to protect their users, safeguard brand trust, and accelerate innovation. Agent Reliability is available starting today. Try it for free and experience the new standard in AI reliability. Learn more below 👇

Galileo

1,276,298 次观看 • 1 年前

This might be the best "AI Engineer" I've tried so far. I'm an old school developer who started 30 years ago. I feel very uncomfortable letting AI take control of my code, but for the sake of science, I spent two hours building an application that took me weeks to build a couple of years ago. I used Pythagora, a brand new tool backed by Y Combinator. They just released to the public. Keep in mind that I use AI every day to write code, but Pythagora is something different: it's a tool that leads, and uses you—the human—as the copilot. I go into more details in the video, but here is the TLDR; 1. Holy molly! We've made a ton of progress on this front! This is way better than Devin when I tested it a few months back. 2. Love the approach of generating a plan with sub-tasks before writing any code. 3. The tools never tries to do too much: it tackles every small task one at a time, and gives you instructions so you test everything. 4. It does exactly what you'd do when it gets stuck: writes a bunch of logs and uses those to correct itself. Pretty neat! 5. It's fast. It runs locally. It's an extension to Visual Studio Code. I'm impressed, but I don't think this tool is for me. I'm not the type of developer who's ready to relinquish control. I felt I had no connection with the code because I didn't write it. It was not my code. I know many people who don't care about this. I know many people who will get tremendous value out of Pythagora. I hope they keep pushing the limits, providing feedback, and helping this get to a point where old folks like me feel more comfortable using it. Don't take my word for it. The best thing you can do is to give it a try and see how you feel using it. Thanks to the team who built this, for all of the explanations and support, and especially, for sitting and listening to my dumb questions for 2 hours while I tested this.

Santiago

212,056 次观看 • 2 年前

.cova on why AI made creativity more valuable: "The rise of AI has given way to a massive flooding of the internet. As a creator, I've noticed a lot of audiences have realized this, and the work that really cuts through the noise is work that is really resonant. You can tell it comes from a place the creator is deeply passionate about, and it feels very authentic. It's made for connection, but it's also very true to the person making it." "With AI producing this flood of content, people have felt like the media they're consuming feels more rootless. And therefore the high-taste, high-creativity stuff that's actually crafted by the person, people are starting to value way more." "I use so much AI, and a lot of it's invisible, a lot of it's very visible. I've found a way to automate away the logistical side of things, so I can focus on the creativity. I built a bunch of custom tools for video-making, and I built them all with AI. Even though I prefer to edit myself and I script everything myself, I still use AI to bounce ideas off of." "The way I initially blew up was I used AI to transform my dorm room into different crazy sets, and people thought I was a professional. I was by no means a professional. It was my tiny dorm room, and I added a piano there, a vinyl record player, fairy lights, a moving robot in the background, cool lighting. It was all AI. I really accredit AI to a lot of my success."

.cova on why AI made creativity more valuable: "The rise of AI has given way to a massive flooding of the internet. As a creator, I've noticed a lot of audiences have realized this, and the work that really cuts through the noise is work that is really resonant. You can tell it comes from a place the creator is deeply passionate about, and it feels very authentic. It's made for connection, but it's also very true to the person making it." "With AI producing this flood of content, people have felt like the media they're consuming feels more rootless. And therefore the high-taste, high-creativity stuff that's actually crafted by the person, people are starting to value way more." "I use so much AI, and a lot of it's invisible, a lot of it's very visible. I've found a way to automate away the logistical side of things, so I can focus on the creativity. I built a bunch of custom tools for video-making, and I built them all with AI. Even though I prefer to edit myself and I script everything myself, I still use AI to bounce ideas off of." "The way I initially blew up was I used AI to transform my dorm room into different crazy sets, and people thought I was a professional. I was by no means a professional. It was my tiny dorm room, and I added a piano there, a vinyl record player, fairy lights, a moving robot in the background, cool lighting. It was all AI. I really accredit AI to a lot of my success."

MTS

10,699 次观看 • 2 个月前

Today we're launching Observability Exports in Jitsu. Everything you see in Live Events can now stream into Datadog, Inc., Grafana Cloud, New Relic, Elastic, or your own OpenTelemetry Collector. Here's how it works: 1. Go to your Jitsu account's Settings → Observability exports. Set your OTLP endpoint: 2. Add your auth header. Datadog wants dd-api-key. 3. Send test log, toggle Enabled, then go find it: service:jitsu-live-events Four record types land: function, bulker_batch, bulker_stream, dead-letter. Your raw event traffic is never exported. These are operational logs about your pipelines. Datadog takes OTLP directly, so there's no agent or collector sitting in between. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Observability Exports is on Jitsu Enterprise plan. DM me to enable it for your org. More in comments!

Today we're launching Observability Exports in Jitsu. Everything you see in Live Events can now stream into Datadog, Inc., Grafana Cloud, New Relic, Elastic, or your own OpenTelemetry Collector. Here's how it works: 1. Go to your Jitsu account's Settings → Observability exports. Set your OTLP endpoint: 2. Add your auth header. Datadog wants dd-api-key. 3. Send test log, toggle Enabled, then go find it: service:jitsu-live-events Four record types land: function, bulker_batch, bulker_stream, dead-letter. Your raw event traffic is never exported. These are operational logs about your pipelines. Datadog takes OTLP directly, so there's no agent or collector sitting in between. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Observability Exports is on Jitsu Enterprise plan. DM me to enable it for your org. More in comments!

Soham Mehta

209,141 次观看 • 22 天前

David Friedberg: The AI Jobs Panic Is a Crock of Sh*t Why? The revenue potential outweighs the cost savings by 100x. “There is no job loss with AI. I've said it a thousand times, and I will say it again, and again, and again. What I see on the ground, and what I've seen at dozens of companies, including my company that I run, there are two sides to a business. There is revenue and there’s costs. On the cost side of the equation, AI can be used to reduce humans doing things that cost money, to some extent. The effect there, I would argue, is nominal. The real opportunity with AI is on the revenue side, where suddenly one engineer can do 100x or 1000x what they used to be able to do, meaning you can make more products at your company, whether those are agricultural seed products, or boats and ships, or software for companies, or clothing, or what have you. Because of AI, everyone has the ability to expand their revenue base to create more products, and that is the foundation of good economic prosperity. It is called productivity. We can grow productivity in this country with AI. So where I see AI being used is on the revenue side 100x more than the cost side. And in that equation, people are hiring like crazy. We cannot hire enough people. I just had a review meeting with my product and engineering team two days ago, and they're like, ‘We want to add an extra 15 headcount to our engineering squads because we have all this opportunity to do stuff that we couldn't otherwise do.’ So we are going to hire more people. And to Sacks' point, we are seeing that show up in the jobs numbers. The idea that AI is going to destroy jobs is a Luddite idea that is being disproven every single day, and I see it on the ground. It is only a matter of time before people wake up to this and they realize that this narrative that they've all been sold is a crock of sh*t.”

David Friedberg: The AI Jobs Panic Is a Crock of Sht Why? The revenue potential outweighs the cost savings by 100x. “There is no job loss with AI. I've said it a thousand times, and I will say it again, and again, and again. What I see on the ground, and what I've seen at dozens of companies, including my company that I run, there are two sides to a business. There is revenue and there’s costs. On the cost side of the equation, AI can be used to reduce humans doing things that cost money, to some extent. The effect there, I would argue, is nominal. The real opportunity with AI is on the revenue side, where suddenly one engineer can do 100x or 1000x what they used to be able to do, meaning you can make more products at your company, whether those are agricultural seed products, or boats and ships, or software for companies, or clothing, or what have you. Because of AI, everyone has the ability to expand their revenue base to create more products, and that is the foundation of good economic prosperity. It is called productivity. We can grow productivity in this country with AI. So where I see AI being used is on the revenue side 100x more than the cost side. And in that equation, people are hiring like crazy. We cannot hire enough people. I just had a review meeting with my product and engineering team two days ago, and they're like, ‘We want to add an extra 15 headcount to our engineering squads because we have all this opportunity to do stuff that we couldn't otherwise do.’ So we are going to hire more people. And to Sacks' point, we are seeing that show up in the jobs numbers. The idea that AI is going to destroy jobs is a Luddite idea that is being disproven every single day, and I see it on the ground. It is only a matter of time before people wake up to this and they realize that this narrative that they've all been sold is a crock of sht.”

The All-In Podcast

152,702 次观看 • 3 个月前

Hot topic in vogue is what happens to systems of record in an era of 1000x more agents than humans. Aaron Levie has been the CEO of Box for 20 years and believes that systems of record become more important, not less, with agents: “Systems of record were built for a TAM of human employees. And that was sort of where the value maxed out at. And now maybe we'll have a hundred times more agents than people or a thousand times more agents than people. So I think on a relative basis, the agent layer will seize growth from zero to a trillion. But the system of record layer now has a thousand times more users on it that need to access data and need to execute a workflow and need to move things through various events. And importantly, you need as an enterprise to care about data integrity and security and the controls in your workflow and traffic copying the agents. So basically, this is where I am very diametrically opposed to the view that the system of record gets is squeezed into a database interaction layer because you actually need all of the core system of record properties for the agents to operate on.”

Hot topic in vogue is what happens to systems of record in an era of 1000x more agents than humans. Aaron Levie has been the CEO of Box for 20 years and believes that systems of record become more important, not less, with agents: “Systems of record were built for a TAM of human employees. And that was sort of where the value maxed out at. And now maybe we'll have a hundred times more agents than people or a thousand times more agents than people. So I think on a relative basis, the agent layer will seize growth from zero to a trillion. But the system of record layer now has a thousand times more users on it that need to access data and need to execute a workflow and need to move things through various events. And importantly, you need as an enterprise to care about data integrity and security and the controls in your workflow and traffic copying the agents. So basically, this is where I am very diametrically opposed to the view that the system of record gets is squeezed into a database interaction layer because you actually need all of the core system of record properties for the agents to operate on.”

Corinne Marie Riley

119,410 次观看 • 9 个月前

Gokul (Gokul Rajaram) explains why utility-based software companies like Zendesk are more exposed to AI than systems of record like NetSuite, and why public markets aren't distinguishing between the two: "The software companies that should be the most worried right now is where they are pricing the product based on utility. Zendesk is a good example. Instead of paying for 50 Zendesk seats, you can pay for 20 and I can have 30 AI agents sitting next to Zendesk. For these companies you need to change your pricing model to be based on outcome. It's going to be hard for them to stay public. The companies that are less exposed are ones based on data that has been collected and captured over a period of time. ERP is a great example. There is no compelling reason for someone to put their career at stake by ripping out NetSuite. NetSuite has more time to build AI agents on top of it because they have the data, they can train the AI agent on top of it and bundle it. I think the public markets do not distinguish between these two types of companies." (Jan 2026)

Gokul (Gokul Rajaram) explains why utility-based software companies like Zendesk are more exposed to AI than systems of record like NetSuite, and why public markets aren't distinguishing between the two: "The software companies that should be the most worried right now is where they are pricing the product based on utility. Zendesk is a good example. Instead of paying for 50 Zendesk seats, you can pay for 20 and I can have 30 AI agents sitting next to Zendesk. For these companies you need to change your pricing model to be based on outcome. It's going to be hard for them to stay public. The companies that are less exposed are ones based on data that has been collected and captured over a period of time. ERP is a great example. There is no compelling reason for someone to put their career at stake by ripping out NetSuite. NetSuite has more time to build AI agents on top of it because they have the data, they can train the AI agent on top of it and bundle it. I think the public markets do not distinguish between these two types of companies." (Jan 2026)

Invest Like the Best

63,411 次观看 • 13 天前

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,073 次观看 • 4 个月前

Knowing your nature is critically important to understanding what success is for you. I can't tell you literally what is best for you, but I can tell you that success is not having a lot more money or status than you need. Having the time and freedom to do what you most want to do is far more important. What is success for most people? It is a matter of having meaningful work and meaningful relationships. If you can make your work and your passion one and the same, and do it with people who you care about and care about you, you will have a happy, successful life. Explore Principles for the Graduating Class of 2026 with my AI Twin, Digital Ray in Beta, here:

Knowing your nature is critically important to understanding what success is for you. I can't tell you literally what is best for you, but I can tell you that success is not having a lot more money or status than you need. Having the time and freedom to do what you most want to do is far more important. What is success for most people? It is a matter of having meaningful work and meaningful relationships. If you can make your work and your passion one and the same, and do it with people who you care about and care about you, you will have a happy, successful life. Explore Principles for the Graduating Class of 2026 with my AI Twin, Digital Ray in Beta, here:

Ray Dalio

99,356 次观看 • 4 个月前

🚨Elon Musk:“In 6-12 months GrokBot will be the #1 tool for building agentic systems. In a year, 100% of code will be written by LLMs.” At SpaceXAI, more than 70% of engineers are already using GrokBot to build self-learning agentic systems. In a 40-minute talk, Elon sits down with SpaceXAI engineers and discusses what the future of AI engineering is really going to look like.This conversation is honestly worth more than 2 hours of any Stanford lecture on AI engineering. Watch it today, then go read the article below on how to build a full Grok bot agents team from scratch. Who’s ready to see the future of AI engineering from the people actually building it?

🚨Elon Musk:“In 6-12 months GrokBot will be the #1 tool for building agentic systems. In a year, 100% of code will be written by LLMs.” At SpaceXAI, more than 70% of engineers are already using GrokBot to build self-learning agentic systems. In a 40-minute talk, Elon sits down with SpaceXAI engineers and discusses what the future of AI engineering is really going to look like.This conversation is honestly worth more than 2 hours of any Stanford lecture on AI engineering. Watch it today, then go read the article below on how to build a full Grok bot agents team from scratch. Who’s ready to see the future of AI engineering from the people actually building it?

Hosna ⚖️ בניטה

16,111 次观看 • 1 个月前