Загрузка видео...

Не удалось загрузить видео

На главную

Introducing: PlayerZero The world's first Engineering World Model that puts debugging, fixing, and testing your code on autopilot. We've raised $20M from Foundation Capital, Matei Zaharia (Databricks), Peter Bailis (Workday), Guillermo Rauch (Vercel), Dylan Field (Figma), Drew Houston (Dropbox), and more PlayerZero frees up 30% of your engineering bandwidth...

akoratana's profile picture

Animesh Koratana

9,506 subscribers

2,756,284 просмотров • 4 месяцев назад •via X (Twitter)

Наука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!
1:37

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!

Harjot Gill

4,774,714 просмотров • 3 месяцев назад

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:
4:42

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:

Santiago

296,535 просмотров • 9 месяцев назад

🚀 Today, we announced frontier agents, a new class of AI agents which are a step-function change in what you can do with agents. Our first three agents mark the beginning of a new era in software development: 🟠 Kiro autonomous agent maintains persistent context and learns over time while working independently, so you can focus on your biggest priorities. It can handle a range of tasks—from triaging bugs to improving code coverage—with a single change spanning multiple repositories. 🟠 AWS Security Agent is your virtual security engineer that helps build secure applications by being a security consultant for app design, code reviews, and penetration testing. 🟠 AWS DevOps Agent is your virtual operations team member that helps resolve and proactively prevent incidents. It is on call when incidents happen, instantly responding to issues and using its knowledge of your application and the relationship between components to find the root ause of the problem. More on how we’re helping customers driving towards an agentic future: #AWSreInvent
1:03

🚀 Today, we announced frontier agents, a new class of AI agents which are a step-function change in what you can do with agents. Our first three agents mark the beginning of a new era in software development: 🟠 Kiro autonomous agent maintains persistent context and learns over time while working independently, so you can focus on your biggest priorities. It can handle a range of tasks—from triaging bugs to improving code coverage—with a single change spanning multiple repositories. 🟠 AWS Security Agent is your virtual security engineer that helps build secure applications by being a security consultant for app design, code reviews, and penetration testing. 🟠 AWS DevOps Agent is your virtual operations team member that helps resolve and proactively prevent incidents. It is on call when incidents happen, instantly responding to issues and using its knowledge of your application and the relationship between components to find the root ause of the problem. More on how we’re helping customers driving towards an agentic future: #AWSreInvent

Swami Sivasubramanian

26,037 просмотров • 7 месяцев назад

hockeystick moments are the biggest opportunity of your career. It's exciting and kinda scary. Everything changes! I wrote Scaling Fast: Software Engineering Through the Hockeystick as your guide. 16 years of startup experience condensed into 240 pages Scaling Fast is based on startup war stories, academic research papers, talking to my mentors, and reading industry insights. It shows you what it takes to survive and thrive through the hockeystick. You'll learn about scaling teams and scaling code, how they influence each other, and why none of it matters if the business is bad. Scaling Fast: Software Engineering Through the Hockeystick is organized in 3 sections: - Scaling the Business - Scaling the Team - Scaling the Tech The business part, that's to help you evaluate the companies you join, this isn't a business book. The team part, that's key to shaping your everyday. We talk about delegating decisions, empowering engineers, working smooth instead of fast, finishing things all the way to done, good code review culture, and shipping incrementally without risky big bang releases. The tech part, that's my favorite. We talk about good abstractions, architectural complexity, observing your systems break, making steady improvements to your code without huge refactoring sprints, why tests don't solve everything, what's even worth testing, how your team structure impacts what you can do with the code, and why solving today's problem is more important than building for an imagined future. None of it is about numerical scaling [name|]. That's easy in 2025. Computers are fast. The challenge is building complex systems that don't fit in any one person's brain without breaking the business. oftware engineering when your whole company changes every 6 months is the fun part of this gig. And that's what Scaling Fast is about. 👉
3:35

hockeystick moments are the biggest opportunity of your career. It's exciting and kinda scary. Everything changes! I wrote Scaling Fast: Software Engineering Through the Hockeystick as your guide. 16 years of startup experience condensed into 240 pages Scaling Fast is based on startup war stories, academic research papers, talking to my mentors, and reading industry insights. It shows you what it takes to survive and thrive through the hockeystick. You'll learn about scaling teams and scaling code, how they influence each other, and why none of it matters if the business is bad. Scaling Fast: Software Engineering Through the Hockeystick is organized in 3 sections: - Scaling the Business - Scaling the Team - Scaling the Tech The business part, that's to help you evaluate the companies you join, this isn't a business book. The team part, that's key to shaping your everyday. We talk about delegating decisions, empowering engineers, working smooth instead of fast, finishing things all the way to done, good code review culture, and shipping incrementally without risky big bang releases. The tech part, that's my favorite. We talk about good abstractions, architectural complexity, observing your systems break, making steady improvements to your code without huge refactoring sprints, why tests don't solve everything, what's even worth testing, how your team structure impacts what you can do with the code, and why solving today's problem is more important than building for an imagined future. None of it is about numerical scaling [name|]. That's easy in 2025. Computers are fast. The challenge is building complex systems that don't fit in any one person's brain without breaking the business. oftware engineering when your whole company changes every 6 months is the fun part of this gig. And that's what Scaling Fast is about. 👉

Swizec Teller

56,515 просмотров • 7 месяцев назад

Americans are under surveillance Roughly 40,000-60,000 cameras have been placed throughout 42 states that are tagging your vehicle and entering it into a database to track you “These cameras capture more than your license. They can capture the interior of your vehicle as you drive by these cameras, especially the positioning of the camera and it's legal (Attorney shows a picture of what one of these “Flock Cameras” looks like, when you see it you’ll instantly recognize it. They’re everywhere) “So what happens is this camera captures your tag and when it captures your tag is able to detect where your vehicle has been anywhere in the United States where there are flock cameras. If you're in Georgia and you travel to New York, every time your vehicle tag gets captured by a flock camera, it is entered into a database and they are able to track it.”
1:02

Americans are under surveillance Roughly 40,000-60,000 cameras have been placed throughout 42 states that are tagging your vehicle and entering it into a database to track you “These cameras capture more than your license. They can capture the interior of your vehicle as you drive by these cameras, especially the positioning of the camera and it's legal (Attorney shows a picture of what one of these “Flock Cameras” looks like, when you see it you’ll instantly recognize it. They’re everywhere) “So what happens is this camera captures your tag and when it captures your tag is able to detect where your vehicle has been anywhere in the United States where there are flock cameras. If you're in Georgia and you travel to New York, every time your vehicle tag gets captured by a flock camera, it is entered into a database and they are able to track it.”

Wall Street Apes

329,561 просмотров • 1 год назад

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."
2:04

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,011 просмотров • 2 месяцев назад

In two years, every new tech company will run on a CRM you can vibe code to fit your business. This CRM will not be built from scratch on a coding platform though. It will be built on top of managed infrastructure with complete data capture, indices designed for LLMs to understand the whole picture, clean APIs, curated UI frameworks designed for selling, enterprise-grade security, and come with 24/7 support. You’ll instruct the agent using natural language and it will write the code + run it for you. That’s what we’re building at Lightfield and today we’re announcing step two of our plan - code execution. You can now ask your agent to build programs, artifacts, and run complex analysis instantly. It does this by writing and running Python in a high performance sandbox using full customer memory — including every email, meeting, and note that Lightfield has captured — and reasoning across every relationship to deliver high quality work. Ask your agent to build a competitive battle card before a call tomorrow. It pulls positioning, objections, and win/loss patterns from real conversations. Ask it to flag every open deal where your champion's engagement has dropped or sentiment has shifted. It reads across every conversation and tells you where to focus. Ask it to build a pipeline review with charts and graphs for your board. It produces the whole thing in minutes. Here’s what we did with it this week: → We asked our agent to grade our sales team on discovery, rapport, and closing. It gave a structured scorecard with specific examples from real conversations. → Our GTM team asked the agent to build a plan to expand one of our enterprise customers. It pulled competitive threats, upsell paths, stakeholder mapping, and a phased execution plan — in minutes. → We used it to find every feature request from the last quarter that our engineering team has since shipped, and draft a personalized follow-up to each customer using their original words. It closed loops across dozens of accounts that would have taken days to track down manually This is the first step towards building any custom GTM workflow in natural language on top of what Lightfield knows about your business - a world model built from every single interaction your team has had with customers.
1:00

In two years, every new tech company will run on a CRM you can vibe code to fit your business. This CRM will not be built from scratch on a coding platform though. It will be built on top of managed infrastructure with complete data capture, indices designed for LLMs to understand the whole picture, clean APIs, curated UI frameworks designed for selling, enterprise-grade security, and come with 24/7 support. You’ll instruct the agent using natural language and it will write the code + run it for you. That’s what we’re building at Lightfield and today we’re announcing step two of our plan - code execution. You can now ask your agent to build programs, artifacts, and run complex analysis instantly. It does this by writing and running Python in a high performance sandbox using full customer memory — including every email, meeting, and note that Lightfield has captured — and reasoning across every relationship to deliver high quality work. Ask your agent to build a competitive battle card before a call tomorrow. It pulls positioning, objections, and win/loss patterns from real conversations. Ask it to flag every open deal where your champion's engagement has dropped or sentiment has shifted. It reads across every conversation and tells you where to focus. Ask it to build a pipeline review with charts and graphs for your board. It produces the whole thing in minutes. Here’s what we did with it this week: → We asked our agent to grade our sales team on discovery, rapport, and closing. It gave a structured scorecard with specific examples from real conversations. → Our GTM team asked the agent to build a plan to expand one of our enterprise customers. It pulled competitive threats, upsell paths, stakeholder mapping, and a phased execution plan — in minutes. → We used it to find every feature request from the last quarter that our engineering team has since shipped, and draft a personalized follow-up to each customer using their original words. It closed loops across dozens of accounts that would have taken days to track down manually This is the first step towards building any custom GTM workflow in natural language on top of what Lightfield knows about your business - a world model built from every single interaction your team has had with customers.

Keith Peiris

27,584 просмотров • 5 месяцев назад

We are truly overwhelmed with gratitude for each and every one of you who took the time out of your incredibly busy days and navigated through the Lagos traffic just to support Violet Charm at our very first pop-up event. It means so much to us that you chose to spend your precious time with us, and your presence brought so much warmth, energy, and joy to the day. This milestone is just the beginning of what we hope will be a beautiful journey, and while this was our first pop-up, it certainly won’t be the last. We are inspired by your encouragement and are committed to learning, growing, and improving every step of the way. Next year, we promise to come back bigger, better, and more exciting, all because of your unwavering support. Thank you from the depths of our hearts for believing in us and being part of this special moment ,we couldn’t have done it without you, and we can’t wait to create even more unforgettable memories together. Full video on my instagram
0:38

We are truly overwhelmed with gratitude for each and every one of you who took the time out of your incredibly busy days and navigated through the Lagos traffic just to support Violet Charm at our very first pop-up event. It means so much to us that you chose to spend your precious time with us, and your presence brought so much warmth, energy, and joy to the day. This milestone is just the beginning of what we hope will be a beautiful journey, and while this was our first pop-up, it certainly won’t be the last. We are inspired by your encouragement and are committed to learning, growing, and improving every step of the way. Next year, we promise to come back bigger, better, and more exciting, all because of your unwavering support. Thank you from the depths of our hearts for believing in us and being part of this special moment ,we couldn’t have done it without you, and we can’t wait to create even more unforgettable memories together. Full video on my instagram

Isabella Esther Georgewill

55,880 просмотров • 7 месяцев назад

New short course: Collaborative Writing and Coding with OpenAI Canvas! Explore new ways to write and code with OpenAI Canvas, a user-friendly interface that allows you to brainstorm, draft, and refine text and code in collaboration with ChatGPT. In the short course, created with OpenAI, and taught by , a research lead at OpenAI, you’ll learn to use Canvas to enhance your workflows. Canvas lets you go beyond simple chat interactions. It provides a side-by-side workspace where you and ChatGPT can edit and refine text or code collaboratively. This makes brainstorming, drafting, and iterating as you write feel more natural and effective. As the first major update to ChatGPT’s visual interface since its launch in 2022, Canvas gives a new, innovative approach to collaboration with AI. For instance, after writing the first version of your code, Canvas can review it and give suggestions for improvement. It can also help with debugging by adding logging, identifying problems to fix, and writing comments. In addition, you'll also learn what it takes to train the model for an interface like Canvas. In this video-only short course, you’ll: - Learn how to ask for in-line feedback and control the iteration of your work by directly editing selected areas of your text or code from the model’s output. - Learn how to access quick automation tools in a shortcut menu that allows you to modify your writing tone and length, enhance your code, and restore previous versions of your work. - Learn how to use Canvas as a research assistant tool with an example of asking the model to reason through the screenshot of a plot to write a research report, in which you can ask questions within the created report. - Ask the model to write Python code to replicate the graph seen on a screenshot image. - Go behind the scenes of how you can create a video game, such as Space Battleship, from scratch, edit it, and display it in one self-contained HTML file. - Get a real-world application example of creating a SQL database from the image of its architecture. - Understand the model training and design processes that power Canvas! Please sign up here:
1:49

New short course: Collaborative Writing and Coding with OpenAI Canvas! Explore new ways to write and code with OpenAI Canvas, a user-friendly interface that allows you to brainstorm, draft, and refine text and code in collaboration with ChatGPT. In the short course, created with OpenAI, and taught by , a research lead at OpenAI, you’ll learn to use Canvas to enhance your workflows. Canvas lets you go beyond simple chat interactions. It provides a side-by-side workspace where you and ChatGPT can edit and refine text or code collaboratively. This makes brainstorming, drafting, and iterating as you write feel more natural and effective. As the first major update to ChatGPT’s visual interface since its launch in 2022, Canvas gives a new, innovative approach to collaboration with AI. For instance, after writing the first version of your code, Canvas can review it and give suggestions for improvement. It can also help with debugging by adding logging, identifying problems to fix, and writing comments. In addition, you'll also learn what it takes to train the model for an interface like Canvas. In this video-only short course, you’ll: - Learn how to ask for in-line feedback and control the iteration of your work by directly editing selected areas of your text or code from the model’s output. - Learn how to access quick automation tools in a shortcut menu that allows you to modify your writing tone and length, enhance your code, and restore previous versions of your work. - Learn how to use Canvas as a research assistant tool with an example of asking the model to reason through the screenshot of a plot to write a research report, in which you can ask questions within the created report. - Ask the model to write Python code to replicate the graph seen on a screenshot image. - Go behind the scenes of how you can create a video game, such as Space Battleship, from scratch, edit it, and display it in one self-contained HTML file. - Get a real-world application example of creating a SQL database from the image of its architecture. - Understand the model training and design processes that power Canvas! Please sign up here:

Andrew Ng

128,180 просмотров • 1 год назад

Insane: 90-95% of Claude Code is now written by Claude Code. I asked Mike Krieger (Anthropic's CPO) what changes when so much of your code is written by AI? His answer: The bottleneck moves from coding/design to: 1. Upstream: aligning the team around what to build. 2. Downstream: the PR merge queue, reviewing and merging all of the new code into production. Anthropic is where other product teams will be in a year or two, so it's important we pay attention. "I would expect that a year from now, the way that we are conceiving of building and shipping software changes a lot. Because it's gonna be very painful to do it the current way."
0:36

Insane: 90-95% of Claude Code is now written by Claude Code. I asked Mike Krieger (Anthropic's CPO) what changes when so much of your code is written by AI? His answer: The bottleneck moves from coding/design to: 1. Upstream: aligning the team around what to build. 2. Downstream: the PR merge queue, reviewing and merging all of the new code into production. Anthropic is where other product teams will be in a year or two, so it's important we pay attention. "I would expect that a year from now, the way that we are conceiving of building and shipping software changes a lot. Because it's gonna be very painful to do it the current way."

Lenny Rachitsky

369,898 просмотров • 1 год назад

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this
13:23

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 просмотров • 1 месяц назад

In 1977, Ashtar (leader of Sirius and Sirians within Galactic Federation) interrupted a British television broadcast with a warning that we "have a short time to learn to live together in peace" so that we can share in the "Great Awakening of the New Age of Aquarius." Peace is an individual choice. Humans are being morally tested to determine who ascends to become a galactic civilization. Not everyone will ascend. "Only those who learn to live in peace will pass to the higher realms of spiritual evolution." Galactic Federation are the angels of light walking among us and assisting us unseen. They continually send teachers to remind us that this is our planet, and we're the ones in control of our outcomes. ------- ASHTAR COMMAND - "For many years you have seen us as lights in the skies. We speak to you now in peace and wisdom as we have done to your brothers and sisters all over this, your planet Earth. We come to warn you of the destiny of your race and your world so that you may communicate to your fellow beings the course you must take to avoid the disaster which threatens your world, and the beings on our worlds around you. This is in order that you may share in the great awakening, as the planet passes into the New Age of Aquarius. The New Age can be a time of great peace and evolution for your race, but only if your rulers are made aware of the evil forces that can overshadow their judgments. Be still now and listen, for your chance may not come again. All your weapons of evil must be removed. The time for conflict is now past and the race of which you are a part may proceed to the higher stages of its evolution if you show yourselves worthy to do this. You have but a short time to learn to live together in peace and goodwill. Small groups all over the planet are learning this and exist to pass on the light of the dawning New Age to you all. You are free to accept or reject their teachings, but only those who learn to live in peace will pass to the higher realms of spiritual evolution. You must learn to be sensitive to the voice within that can tell you what is truth, and what is confusion, chaos and untruth. Learn to listen to the voice of truth which is within you, and you will lead yourselves onto the path of evolution. This is our message to our dear friends. We have watched you growing for many years as you too have watched our lights in your skies. You know now that we are here, and that there are more beings on and around your Earth than your scientists admit. We are deeply concerned about you and your path towards the light and will do all we can to help you. Have no fear, seek only to know yourselves, and live in harmony with the ways of your planet Earth. We here at the Ashtar Galactic Command thank you for your attention. We are now leaving the planes of your existence. May you be blessed by the supreme love and truth of the cosmos."
2:59

In 1977, Ashtar (leader of Sirius and Sirians within Galactic Federation) interrupted a British television broadcast with a warning that we "have a short time to learn to live together in peace" so that we can share in the "Great Awakening of the New Age of Aquarius." Peace is an individual choice. Humans are being morally tested to determine who ascends to become a galactic civilization. Not everyone will ascend. "Only those who learn to live in peace will pass to the higher realms of spiritual evolution." Galactic Federation are the angels of light walking among us and assisting us unseen. They continually send teachers to remind us that this is our planet, and we're the ones in control of our outcomes. ------- ASHTAR COMMAND - "For many years you have seen us as lights in the skies. We speak to you now in peace and wisdom as we have done to your brothers and sisters all over this, your planet Earth. We come to warn you of the destiny of your race and your world so that you may communicate to your fellow beings the course you must take to avoid the disaster which threatens your world, and the beings on our worlds around you. This is in order that you may share in the great awakening, as the planet passes into the New Age of Aquarius. The New Age can be a time of great peace and evolution for your race, but only if your rulers are made aware of the evil forces that can overshadow their judgments. Be still now and listen, for your chance may not come again. All your weapons of evil must be removed. The time for conflict is now past and the race of which you are a part may proceed to the higher stages of its evolution if you show yourselves worthy to do this. You have but a short time to learn to live together in peace and goodwill. Small groups all over the planet are learning this and exist to pass on the light of the dawning New Age to you all. You are free to accept or reject their teachings, but only those who learn to live in peace will pass to the higher realms of spiritual evolution. You must learn to be sensitive to the voice within that can tell you what is truth, and what is confusion, chaos and untruth. Learn to listen to the voice of truth which is within you, and you will lead yourselves onto the path of evolution. This is our message to our dear friends. We have watched you growing for many years as you too have watched our lights in your skies. You know now that we are here, and that there are more beings on and around your Earth than your scientists admit. We are deeply concerned about you and your path towards the light and will do all we can to help you. Have no fear, seek only to know yourselves, and live in harmony with the ways of your planet Earth. We here at the Ashtar Galactic Command thank you for your attention. We are now leaving the planes of your existence. May you be blessed by the supreme love and truth of the cosmos."

Kab

210,158 просмотров • 1 год назад

Father God, I thank you for everyone here. I pray that you would give each person here in this audience, clarity of mind, clear thoughts. That you would speak to them in their hearts and minds to, prepare them. That you would, fill them up where they aren’t full, where they are full, that you would give them perfect opportunities that suit your will to be a blessing so that you may increase their blessing, that you may refill their blessing. Make their glasses bigger to receive the blessing that you have for them, Father God. And give them clarity of mind and purpose to be a blessing to all around them. Blessings for healing, blessings for prosperity, so that in the midst of the storm, those around them will be able to be fed and cared for, and to know your presence, your peace, your way. We pray for all those warriors of truth, that they would, be encouraged and strengthened in their soul to proceed forward apace in this dark moment, and the dark moments ahead. That as we go through this near-death experience as a country, that it will go, we will go through it and, and prevail by faith, and that you would increase all of our faith through faithfulness to do your will, Father God. That we would come through this storm, this group specifically, as shining like the noonday sun, that your presence would shine brightly through each person here out into the country, and that we would dispel the darkness in souls, in actions, in justice, in lawfulness. That we will, push out the darkness that has, that has clouded our land, and those principalities, those powers of darkness in high places would be purged from the land by the light of your presence in your people doing your will, your way, Father God. We seek to be children of the light, the heavenly light, the godly light, and not a false light. But through truth and justice, that we would be, reign supreme in our land over every power of darkness, every evil, every sickness. That those demons of disease and dis-ease would be cast out of our land, and then that we, being strengthened, being made whole as a people, would be able, with power, to go forth into the world with ample supply from our own shores. To go into the world and to be not our brother’s keeper, but our brother’s brother. To be friends and, through kindness and through, acts of beauty, and your righteousness, Father God, to bring healing out into the world, wholeness into the world, and to oppose the devil wherever we may find him. To attack his activities, wherever he may be, and to bring light to those held in darkness, and freedom across the world according to your will, Father God, that men may serve you from liberty, not from compulsion, and not having to hide their faith in the dark. We look to you, Father God, for the energy, the supply, the clarity of mind, and the understanding of how to move to accomplish these things according to your will. We pray to be Gideon’s, those that are chosen by you specially, as we go into the enemy’s camps and at the appointed moment, bring them to complete chaos. Not against us or your children or your purposes, but to destroy each other’s camps, to destroy each other’s armaments, to destroy each other’s evil intention. That we may enjoy a time of peace, prosperity, clarity of mind across the world according to your will, even in the midst of the darkness. We ask for, protection, angelic protection throughout this whole camp and throughout those places that the people in this camp are warriors to protect and defend. That each one here would have all the necessary provision, angelic assistance, divine direction to do your will, Father God, your way, with an instant of, of clarity of mind and purpose. We thank you for the opportunity to come together, for the will in our hearts, that you have put your presence inside of us, and we ask for your help to do your will your way, and enjoy your supply accordingly, your blessing, Father God. Bless us, that we may be a blessing according to your will. We ask all this in Jesus’ name. By the blood of Christ, make it so, Amen. Full program today from Washington D.C. Where Juan and a group of Patiots gather.
6:24

Father God, I thank you for everyone here. I pray that you would give each person here in this audience, clarity of mind, clear thoughts. That you would speak to them in their hearts and minds to, prepare them. That you would, fill them up where they aren’t full, where they are full, that you would give them perfect opportunities that suit your will to be a blessing so that you may increase their blessing, that you may refill their blessing. Make their glasses bigger to receive the blessing that you have for them, Father God. And give them clarity of mind and purpose to be a blessing to all around them. Blessings for healing, blessings for prosperity, so that in the midst of the storm, those around them will be able to be fed and cared for, and to know your presence, your peace, your way. We pray for all those warriors of truth, that they would, be encouraged and strengthened in their soul to proceed forward apace in this dark moment, and the dark moments ahead. That as we go through this near-death experience as a country, that it will go, we will go through it and, and prevail by faith, and that you would increase all of our faith through faithfulness to do your will, Father God. That we would come through this storm, this group specifically, as shining like the noonday sun, that your presence would shine brightly through each person here out into the country, and that we would dispel the darkness in souls, in actions, in justice, in lawfulness. That we will, push out the darkness that has, that has clouded our land, and those principalities, those powers of darkness in high places would be purged from the land by the light of your presence in your people doing your will, your way, Father God. We seek to be children of the light, the heavenly light, the godly light, and not a false light. But through truth and justice, that we would be, reign supreme in our land over every power of darkness, every evil, every sickness. That those demons of disease and dis-ease would be cast out of our land, and then that we, being strengthened, being made whole as a people, would be able, with power, to go forth into the world with ample supply from our own shores. To go into the world and to be not our brother’s keeper, but our brother’s brother. To be friends and, through kindness and through, acts of beauty, and your righteousness, Father God, to bring healing out into the world, wholeness into the world, and to oppose the devil wherever we may find him. To attack his activities, wherever he may be, and to bring light to those held in darkness, and freedom across the world according to your will, Father God, that men may serve you from liberty, not from compulsion, and not having to hide their faith in the dark. We look to you, Father God, for the energy, the supply, the clarity of mind, and the understanding of how to move to accomplish these things according to your will. We pray to be Gideon’s, those that are chosen by you specially, as we go into the enemy’s camps and at the appointed moment, bring them to complete chaos. Not against us or your children or your purposes, but to destroy each other’s camps, to destroy each other’s armaments, to destroy each other’s evil intention. That we may enjoy a time of peace, prosperity, clarity of mind across the world according to your will, even in the midst of the darkness. We ask for, protection, angelic protection throughout this whole camp and throughout those places that the people in this camp are warriors to protect and defend. That each one here would have all the necessary provision, angelic assistance, divine direction to do your will, Father God, your way, with an instant of, of clarity of mind and purpose. We thank you for the opportunity to come together, for the will in our hearts, that you have put your presence inside of us, and we ask for your help to do your will your way, and enjoy your supply accordingly, your blessing, Father God. Bless us, that we may be a blessing according to your will. We ask all this in Jesus’ name. By the blood of Christ, make it so, Amen. Full program today from Washington D.C. Where Juan and a group of Patiots gather.

Juan O Savin 107

45,348 просмотров • 23 дней назад

Lightspeed's Bucky Moore says the real opportunity in the AI app layer is in large industries far enough afield from where the model providers are today — and where the context engineering to get customer data into the model is extremely nuanced and messy. "I think this is kind of the elephant in the room right now — whether post-training open-source models combined with the unique user feedback you get from being an application provider is defensible enough." "That is going to be an inevitable challenge for any of these industries that hit a maturation point of AI adoption, like legal and software engineering have." "But on the other hand, there are some industries where they're very large, they're far enough afield from where the model providers are today — and probably will continue to be — and the context engineering to actually get the customer data into the model is just so messy. It requires going across different business functions, it requires a lot of hands-on forward-deployed engineering." "Those are the kind of companies that we get really excited about. Because I think being really good at that is not only defensible, but it also allows you to generate a feedback loop with your customers, where you hear a lot of their secrets. And those secrets allow you to feed that back into how you make your product better at the expense of anyone else playing in the space. Because if you're serving the customer, they're only serving you those secrets." "I think Palantir is a good example of this in the pre-AI era, and I think we're going to see many companies ascend in that same way."
2:28

Lightspeed's Bucky Moore says the real opportunity in the AI app layer is in large industries far enough afield from where the model providers are today — and where the context engineering to get customer data into the model is extremely nuanced and messy. "I think this is kind of the elephant in the room right now — whether post-training open-source models combined with the unique user feedback you get from being an application provider is defensible enough." "That is going to be an inevitable challenge for any of these industries that hit a maturation point of AI adoption, like legal and software engineering have." "But on the other hand, there are some industries where they're very large, they're far enough afield from where the model providers are today — and probably will continue to be — and the context engineering to actually get the customer data into the model is just so messy. It requires going across different business functions, it requires a lot of hands-on forward-deployed engineering." "Those are the kind of companies that we get really excited about. Because I think being really good at that is not only defensible, but it also allows you to generate a feedback loop with your customers, where you hear a lot of their secrets. And those secrets allow you to feed that back into how you make your product better at the expense of anyone else playing in the space. Because if you're serving the customer, they're only serving you those secrets." "I think Palantir is a good example of this in the pre-AI era, and I think we're going to see many companies ascend in that same way."

TBPN

46,746 просмотров • 4 месяцев назад

This isn't alien technology, literally or metaphorically. The breakthrough here isn't in engineering at all — it's in corporate organization. See, most machines are broken because the organizations that make them are broken. As an engineer, I would estimate that at least 30% of the parts of any given device exist only to correct for the design flaws in the other 70%. Works like this. Suppose I, an engineer, design a set of pipes and injectors to feed fuel to a combustion chamber at a consistent and controllable rate. Except in testing, there's some corner cases it doesn't handle well. Now, if you're an engineer, you understand this is normal. Nobody ever gets a design right the first time, unless it's so trivial that it's probably been done before. Your first design doesn't survive the wind tunnel, your first code doesn't compile right away, and if does, it segfaults. Your rockets blow up. And there's a flow problem with your fuel feed lines. It happens. Doesn't mean you're stupid. Means you didn't have enough information. But you have an even bigger problem. Middle management. Middle management is a special variety of hazmat suit, which is worn by the finance, sales, or market guys who run companies, so they don't have to touch the icky engineers. C-suite guys hate hate hate engineers, because it's a terrifying sensation to be dependent on someone you cannot understand, who doesn't appear to respect you much. (It does not occur to them that it is also extremely frustrating to have your work paid for, and thus controlled, by someone who cannot understand what you do, who doesn't appear to respect you much.) The primary role of middle management is talk to engineers so C-suite guys won't have to, and the primary qualification is to be a member of the right social class, and to hate engineers. This qualification is dressed up in secret handshake buzzwords like "management experience", as used in the sentence "I know you have been an engineer for twenty years and the other engineers all come to you for advice and leadership, but you don't have management experience, so I am going to hire my golfing buddy's 23 year old kid, who just graduated business school." So the fact that the fuel lines lines are not working quite right isn't your problem. That's part of the normal engineering process. Your problem is that your manager hates you and everything you stand for, and doesn't trust you or take your word for anything. He think his job is to keep you in line rather than help or empower you. So when you say "the fuel feed lines need to be redesigned", he says "we already spent six months and seventeen million dollars design the fuel feed system, we can't let you do it again." He thinks you are telling him seventeen million dollars worth of work needs to be thrown away and redone, and he cannot be told otherwise, because he cannot be told anything. So he says "you have two weeks and fifty thousand dollars to fix it". So you add another turbopump. What else can you do in two weeks? Now there's a new part. And if something goes wrong with that, another new part will be added to fix it. Because the company's actual priority isn't what you are responsible for — the design. It's what middle management is responsible for — the schedule and the budget. You have to play the villain so they can play the hero. What middle management doesn't understand, is paid to not understand, is what engineering actually is. Engineering is the process of making mistakes until you run out of mistakes to make. So when you spend six months and seventeen million dollars, and ended up with a design that doesn't quite work right in all cases, you weren't throwing away money, you were burning through mistakes. You've gotten a lot of them out of the way and won't make them again. But you have to get rid of some more before the design is actually right and doesn't require extra parts. The work of engineering isn't making the thing. It's teaching yourself to make the thing. Once you've done that, you can make the thing with minimal effort and time, because you know how to make the thing. C-suite financiers would hate this idea if they understood it. Why? Because it's unpredictable. Financiers like safe investments that make money. Not knowing how long something will take or how much it will cost is terrifying to them. So they train engineers to lie to them, by hiring a middle managers who try to force them to lie, and just interpret every guess as a promise if engineers still refuse to do so. But lying to yourself doesn't make the truth go away. The truth is that engineering projects take as long as they take, and cost as much as they cost. And that no one knows how long or how much they will be, because no one knows how many mistakes are waiting to be made, until they actually make them. The only thing you thing you can do about this is hire really good engineers, who catch more of their mistakes on the white board, leaving fewer to be caught in the wind tunnel, and this makes engineering faster... but it doesn't make engineering more predictable. Gantt charts are nothing but a collection of lies that corporations have taught themselves to tell themselves, lies that middle managers try to make true by enforcing them as promises. The ultimate reason that machines are 30% unnecessary parts is that the corporations that build them are 30% unnecessary people. This is what's different about Elon Musk. It's not that he's a better engineer. It's that he's a better manager. He understands engineers and engineering, and he doesn't hate them because he is one. He understood all along that green-field design is full of unknown-unknowns, and that there is absolutely no number-crunching, pie-chart, MBA magic that can eliminate this risk... it can only be hidden from view. The critical understanding is in the video clip below, where he says that SpaceX only had a 10% chance of success. You cannot say something like that unless you get it. And when you get it, you are free. Free from artificial anxiety about schedules and budgets. Anxiety about schedules and budgets is based on the delusion of control. Managers can't make a project finish "on time". They never could. The only power they have is the power to screw it up. The fate of a project is already written in the unknown unknowns before it ever starts. And the best, the absolute best, an engineering team can ever do, under any circumstances, is to confront those unknowns with clear-eyed honesty, and a willingness to adapt. Well, when you say to yourself, "This project has a 10% chance of succeeding", you've already confronted the pain of those admissions, which means you have already conquered the fear. The fear that makes you try to treat a prediction as a promise. The fear that makes you insert an extra turbopump, when what you really need to do is get busy redesigning the pipes, even though you have no idea how long it will take or much it will cost. Even when your rockets blow up. The SpaceX Raptor engine isn't just, or even primarily, a triumph of engineering smarts. It's a triumph of character. It's about an entire team with virtues MBAs lack: self-awareness, persistence, courage, humility, and, ultimately, hope. Because that's what it takes to pursue the best design, the RIGHT design, not even knowing if it exists to be found, much less whether you'll find it before you run out of money. Great things are not accomplished by middle managers with spreadsheets and Gantt charts. They are accomplished by teams of experts with passion and vision. Who are willing to risk failure so they can succeed. So what's the point in me saying all this? Am I just writing a puff piece on SpaceX and the Raptor engine? No. The point is that this is not special, one-off, magic alien technology. It's the systematic result of a correct understanding of engineering. Which means that EVERY COMPANY CAN BE LIKE THIS. If the people who control the purse strings are willing to learn from this example, and stop managing with spreadsheets and fear.
0:40

This isn't alien technology, literally or metaphorically. The breakthrough here isn't in engineering at all — it's in corporate organization. See, most machines are broken because the organizations that make them are broken. As an engineer, I would estimate that at least 30% of the parts of any given device exist only to correct for the design flaws in the other 70%. Works like this. Suppose I, an engineer, design a set of pipes and injectors to feed fuel to a combustion chamber at a consistent and controllable rate. Except in testing, there's some corner cases it doesn't handle well. Now, if you're an engineer, you understand this is normal. Nobody ever gets a design right the first time, unless it's so trivial that it's probably been done before. Your first design doesn't survive the wind tunnel, your first code doesn't compile right away, and if does, it segfaults. Your rockets blow up. And there's a flow problem with your fuel feed lines. It happens. Doesn't mean you're stupid. Means you didn't have enough information. But you have an even bigger problem. Middle management. Middle management is a special variety of hazmat suit, which is worn by the finance, sales, or market guys who run companies, so they don't have to touch the icky engineers. C-suite guys hate hate hate engineers, because it's a terrifying sensation to be dependent on someone you cannot understand, who doesn't appear to respect you much. (It does not occur to them that it is also extremely frustrating to have your work paid for, and thus controlled, by someone who cannot understand what you do, who doesn't appear to respect you much.) The primary role of middle management is talk to engineers so C-suite guys won't have to, and the primary qualification is to be a member of the right social class, and to hate engineers. This qualification is dressed up in secret handshake buzzwords like "management experience", as used in the sentence "I know you have been an engineer for twenty years and the other engineers all come to you for advice and leadership, but you don't have management experience, so I am going to hire my golfing buddy's 23 year old kid, who just graduated business school." So the fact that the fuel lines lines are not working quite right isn't your problem. That's part of the normal engineering process. Your problem is that your manager hates you and everything you stand for, and doesn't trust you or take your word for anything. He think his job is to keep you in line rather than help or empower you. So when you say "the fuel feed lines need to be redesigned", he says "we already spent six months and seventeen million dollars design the fuel feed system, we can't let you do it again." He thinks you are telling him seventeen million dollars worth of work needs to be thrown away and redone, and he cannot be told otherwise, because he cannot be told anything. So he says "you have two weeks and fifty thousand dollars to fix it". So you add another turbopump. What else can you do in two weeks? Now there's a new part. And if something goes wrong with that, another new part will be added to fix it. Because the company's actual priority isn't what you are responsible for — the design. It's what middle management is responsible for — the schedule and the budget. You have to play the villain so they can play the hero. What middle management doesn't understand, is paid to not understand, is what engineering actually is. Engineering is the process of making mistakes until you run out of mistakes to make. So when you spend six months and seventeen million dollars, and ended up with a design that doesn't quite work right in all cases, you weren't throwing away money, you were burning through mistakes. You've gotten a lot of them out of the way and won't make them again. But you have to get rid of some more before the design is actually right and doesn't require extra parts. The work of engineering isn't making the thing. It's teaching yourself to make the thing. Once you've done that, you can make the thing with minimal effort and time, because you know how to make the thing. C-suite financiers would hate this idea if they understood it. Why? Because it's unpredictable. Financiers like safe investments that make money. Not knowing how long something will take or how much it will cost is terrifying to them. So they train engineers to lie to them, by hiring a middle managers who try to force them to lie, and just interpret every guess as a promise if engineers still refuse to do so. But lying to yourself doesn't make the truth go away. The truth is that engineering projects take as long as they take, and cost as much as they cost. And that no one knows how long or how much they will be, because no one knows how many mistakes are waiting to be made, until they actually make them. The only thing you thing you can do about this is hire really good engineers, who catch more of their mistakes on the white board, leaving fewer to be caught in the wind tunnel, and this makes engineering faster... but it doesn't make engineering more predictable. Gantt charts are nothing but a collection of lies that corporations have taught themselves to tell themselves, lies that middle managers try to make true by enforcing them as promises. The ultimate reason that machines are 30% unnecessary parts is that the corporations that build them are 30% unnecessary people. This is what's different about Elon Musk. It's not that he's a better engineer. It's that he's a better manager. He understands engineers and engineering, and he doesn't hate them because he is one. He understood all along that green-field design is full of unknown-unknowns, and that there is absolutely no number-crunching, pie-chart, MBA magic that can eliminate this risk... it can only be hidden from view. The critical understanding is in the video clip below, where he says that SpaceX only had a 10% chance of success. You cannot say something like that unless you get it. And when you get it, you are free. Free from artificial anxiety about schedules and budgets. Anxiety about schedules and budgets is based on the delusion of control. Managers can't make a project finish "on time". They never could. The only power they have is the power to screw it up. The fate of a project is already written in the unknown unknowns before it ever starts. And the best, the absolute best, an engineering team can ever do, under any circumstances, is to confront those unknowns with clear-eyed honesty, and a willingness to adapt. Well, when you say to yourself, "This project has a 10% chance of succeeding", you've already confronted the pain of those admissions, which means you have already conquered the fear. The fear that makes you try to treat a prediction as a promise. The fear that makes you insert an extra turbopump, when what you really need to do is get busy redesigning the pipes, even though you have no idea how long it will take or much it will cost. Even when your rockets blow up. The SpaceX Raptor engine isn't just, or even primarily, a triumph of engineering smarts. It's a triumph of character. It's about an entire team with virtues MBAs lack: self-awareness, persistence, courage, humility, and, ultimately, hope. Because that's what it takes to pursue the best design, the RIGHT design, not even knowing if it exists to be found, much less whether you'll find it before you run out of money. Great things are not accomplished by middle managers with spreadsheets and Gantt charts. They are accomplished by teams of experts with passion and vision. Who are willing to risk failure so they can succeed. So what's the point in me saying all this? Am I just writing a puff piece on SpaceX and the Raptor engine? No. The point is that this is not special, one-off, magic alien technology. It's the systematic result of a correct understanding of engineering. Which means that EVERY COMPANY CAN BE LIKE THIS. If the people who control the purse strings are willing to learn from this example, and stop managing with spreadsheets and fear.

Devon Eriksen

126,470 просмотров • 6 месяцев назад

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.
0:20

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

14,920 просмотров • 3 месяцев назад

Fan Video For #TAEMIN in Chile 🇨🇱 [English]: "Hello, Taemin from this part of the world we open our hearts to send you this message. Showing you the deep love and admiration we have for you. Every step you take, every melody you share and every time we see your smile the bond between us grows stronger despite the distance. Chile it's a country that it's far away from Korea, it's on the other side of the world. Here when the sun shines there (in Korea) the sun sets. The distance, cultural and linguistic differences seem to distance us but none of that has stopped us or prevented us from deciding to always be by your side. The time difference (12hs), more than an impediment, it's a way to strive for your dreams while you rest. Your fans in Chile have passion, commitment, and unconditional love towards you. We support all your decisions and every step you take. We feel very proud to follow the artist and the person that you are, and it fills us with happiness to be able to celebrate your achievements, your birthdays, and your anniversaries. No matter the place or the day we always feel accompanied by you. Do you remember how many times you have visited Chile? Your visits to Chile have left indelible marks, in 2014 with SHINee, in 2018 with Music Bank, and in 2019 with SMOTWON. With this we are filled with emotion/pride and energy, so thank you for connecting so deeply with us through things like singing and speaking in Spanish putting a lot of effort and love into it. Your authenticity and dedication make you a unique artist. You fill our hearts with every song, every choreography, and every word you share (with us) because what you offer can't be compared. Chilean fans want to express our gratitude and love which extends over more than 4,000 km of our country; one of the largest in the world. Chile, it's far from Korea, on the other side of the world, but it's at that distance that feelings can be purer, stronger, and generous. Also, we are joined by Taemates and Shawols from Bolivia, Argentina, Peru, and more countries from South America, because this feeling crosses/surpasses all borders. This continent it's your house and Chile is your home. Thousands of Taemates and Shawols gathered from different parts of the country because you are the one who unites us. From this city, which rises between mountains, you can have the certainty in your heart that on this side of the world, there is a lot of passionate, understanding, and unconditional love for you. I love you, from Chile [...]. Thank you for being the inspiration that unites us. [...]" P.S. It's not the full translation since there were a lot of screams and I couldn't hear what the video said, but they were really beautiful words for Taemin.
4:04

Fan Video For #TAEMIN in Chile 🇨🇱 [English]: "Hello, Taemin from this part of the world we open our hearts to send you this message. Showing you the deep love and admiration we have for you. Every step you take, every melody you share and every time we see your smile the bond between us grows stronger despite the distance. Chile it's a country that it's far away from Korea, it's on the other side of the world. Here when the sun shines there (in Korea) the sun sets. The distance, cultural and linguistic differences seem to distance us but none of that has stopped us or prevented us from deciding to always be by your side. The time difference (12hs), more than an impediment, it's a way to strive for your dreams while you rest. Your fans in Chile have passion, commitment, and unconditional love towards you. We support all your decisions and every step you take. We feel very proud to follow the artist and the person that you are, and it fills us with happiness to be able to celebrate your achievements, your birthdays, and your anniversaries. No matter the place or the day we always feel accompanied by you. Do you remember how many times you have visited Chile? Your visits to Chile have left indelible marks, in 2014 with SHINee, in 2018 with Music Bank, and in 2019 with SMOTWON. With this we are filled with emotion/pride and energy, so thank you for connecting so deeply with us through things like singing and speaking in Spanish putting a lot of effort and love into it. Your authenticity and dedication make you a unique artist. You fill our hearts with every song, every choreography, and every word you share (with us) because what you offer can't be compared. Chilean fans want to express our gratitude and love which extends over more than 4,000 km of our country; one of the largest in the world. Chile, it's far from Korea, on the other side of the world, but it's at that distance that feelings can be purer, stronger, and generous. Also, we are joined by Taemates and Shawols from Bolivia, Argentina, Peru, and more countries from South America, because this feeling crosses/surpasses all borders. This continent it's your house and Chile is your home. Thousands of Taemates and Shawols gathered from different parts of the country because you are the one who unites us. From this city, which rises between mountains, you can have the certainty in your heart that on this side of the world, there is a lot of passionate, understanding, and unconditional love for you. I love you, from Chile [...]. Thank you for being the inspiration that unites us. [...]" P.S. It's not the full translation since there were a lot of screams and I couldn't hear what the video said, but they were really beautiful words for Taemin.

SHINee Fan Base

15,940 просмотров • 1 год назад