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

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

На главную

Before software engineers even begin writing code, they have to set the stage of the entire development process. This process requires engineers to make complex tradeoffs between requirements, system design, and implementations details. Current IDEs that rely on AI features, like chat and inline coding, can help engineers get...

SwamiSivasubram's profile picture

Swami Sivasubramanian

6,164 subscribers

154,343 просмотров • 1 год назад •via X (Twitter)

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

Anya Rossi• Live Now

Private livecam show

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

Фото профиля Muktesh
Muktesh1 год назад

Interesting. Looking forward to try this as spec driven development is the future and the current direction.

Фото профиля Mobile Scanner
Mobile Scanner1 год назад

Scan any documents, convert images into text, PDF files, etc. 👍

Фото профиля Serge Doubinski
Serge Doubinski1 год назад

congrats on the launch! recognizing importance of specs is better these days - claude code planning mode, cursor todos, but making it an even more core feature is a great call. kind of makes sense that it comes from amazon and given the writing culture

Фото профиля redsquare
redsquare1 год назад

Why is it devoid of any aws branding?

Фото профиля Scalevise
Scalevise1 год назад

This what we were looking for🙌

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

Introducing Kiro, an all-new agentic IDE that has a chance to transform how developers build software. Let me highlight three key innovations that make Kiro special: 1 - Kiro introduces spec-driven development, helping developers express their intent clearly through natural language specifications and architecture diagrams for complex features. This comprehensive context helps Kiro’s AI agents deliver better results with fewer iterations. 2 - Kiro features intelligent agent hooks that automatically handle critical but time-consuming tasks like generating documentation, writing tests, and optimizing performance. These hooks work in the background, triggered by events like saving files or making commits. It’s like having an experienced developer constantly reviewing your work and handling the maintenance tasks that often get delayed. 3 - Kiro provides a purpose-built interface that adapts to how developers work. Whether you prefer chat interactions or working with specifications, Kiro supports your workflow while keeping you in control of the development process. Kiro is really good at "vibe coding" but goes well beyond that. While other AI coding assistants might help you prototype quickly, Kiro helps you take those prototypes all the way to production by following a mature, structured development process out of the box. This means developers can spend less time on boilerplate code and more time where it matters most – innovating and building solutions that customers will love. Starting today, Kiro is available for free during preview and supports most popular programming languages. Here’s how to get started with Kiro today: Excited to see how developers use Kiro, and to work with the developer community to continue to shape Kiro moving forward.
1:11

Introducing Kiro, an all-new agentic IDE that has a chance to transform how developers build software. Let me highlight three key innovations that make Kiro special: 1 - Kiro introduces spec-driven development, helping developers express their intent clearly through natural language specifications and architecture diagrams for complex features. This comprehensive context helps Kiro’s AI agents deliver better results with fewer iterations. 2 - Kiro features intelligent agent hooks that automatically handle critical but time-consuming tasks like generating documentation, writing tests, and optimizing performance. These hooks work in the background, triggered by events like saving files or making commits. It’s like having an experienced developer constantly reviewing your work and handling the maintenance tasks that often get delayed. 3 - Kiro provides a purpose-built interface that adapts to how developers work. Whether you prefer chat interactions or working with specifications, Kiro supports your workflow while keeping you in control of the development process. Kiro is really good at "vibe coding" but goes well beyond that. While other AI coding assistants might help you prototype quickly, Kiro helps you take those prototypes all the way to production by following a mature, structured development process out of the box. This means developers can spend less time on boilerplate code and more time where it matters most – innovating and building solutions that customers will love. Starting today, Kiro is available for free during preview and supports most popular programming languages. Here’s how to get started with Kiro today: Excited to see how developers use Kiro, and to work with the developer community to continue to shape Kiro moving forward.

Andy Jassy

668,383 просмотров • 1 год назад

We’re excited to share that the Kiro waitlist is now removed! You can sign up and start using it today 👻 For a limited time, activating your account gives you 500 free credits (valid for 30 days) to try spec-driven development for yourself. See what developers are saying about building with Kiro 👉
1:09

We’re excited to share that the Kiro waitlist is now removed! You can sign up and start using it today 👻 For a limited time, activating your account gives you 500 free credits (valid for 30 days) to try spec-driven development for yourself. See what developers are saying about building with Kiro 👉

Kiro

43,119 просмотров • 10 месяцев назад

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!
3:40

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!

Andrew Ng

1,225,587 просмотров • 2 лет назад

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.
0:35

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.

Dustin

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

New course: Spec-Driven Development with Coding Agents, built in partnership with JetBrains, and taught by Paul Everitt | @pauleveritt@fosstodon.org. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track!
2:51

New course: Spec-Driven Development with Coding Agents, built in partnership with JetBrains, and taught by Paul Everitt | @[email protected]. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track!

Andrew Ng

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

Stage is a code review platform designed to help engineers understand AI-generated code. Your team is drowning in an endless backlog of PRs. Stage turns code review into a guided process and enables you to review changes faster than using GitHub. Congrats on the launch, Charles Pan and Dean Stratakos!
0:50

Stage is a code review platform designed to help engineers understand AI-generated code. Your team is drowning in an endless backlog of PRs. Stage turns code review into a guided process and enables you to review changes faster than using GitHub. Congrats on the launch, Charles Pan and Dean Stratakos!

Y Combinator

1,063,689 просмотров • 3 месяцев назад

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

Why did spec-driven development never take off - the workflow tools like Amazon’s Kiro or GitHub Workspaces encouraged? dex, founder of HumanLayer: “These projects have a really interesting idea: you maintain a set of specifications for your software, and then you maintain the code itself, and the dream is the coding part is just compiling specs into code. But that part never really materialized. I’m on a GitHub issue in spec kit that’s been open for a year, and every couple of weeks I get a new email on the thread of people complaining about the same problem: I edit my specs and then I edit the code, and the code drifts from the specs. How do I keep the specs up to date as the code is changing? You now have two sources of truth, and it stops being useful. That’s why with RPI (Research, Plan, Implement), the docs are tactical execution docs - I do the research, the plan, the implementation, and I throw the docs out. The next time I need research I just do it from scratch, because tokens are cheap and my time is expensive.”
1:36

Why did spec-driven development never take off - the workflow tools like Amazon’s Kiro or GitHub Workspaces encouraged? dex, founder of HumanLayer: “These projects have a really interesting idea: you maintain a set of specifications for your software, and then you maintain the code itself, and the dream is the coding part is just compiling specs into code. But that part never really materialized. I’m on a GitHub issue in spec kit that’s been open for a year, and every couple of weeks I get a new email on the thread of people complaining about the same problem: I edit my specs and then I edit the code, and the code drifts from the specs. How do I keep the specs up to date as the code is changing? You now have two sources of truth, and it stops being useful. That’s why with RPI (Research, Plan, Implement), the docs are tactical execution docs - I do the research, the plan, the implementation, and I throw the docs out. The next time I need research I just do it from scratch, because tokens are cheap and my time is expensive.”

The Pragmatic Engineer

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

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.
2:14

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

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

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

"What you do is you prioritize the top few benchmarks and then you probably bullshit the rest." We talk a lot about how AI is making coding easier for non-technical folks, but don't hear much about how the most elite engineers are delegating their most technically complex work. Ankur Goyal (CEO Braintrust) and team has to deliver huge volumes of data at lightning fast speeds, which means they're always looking at ways to optimize their DB stack. The problem? Technical hypotheses are expensive and slow to test when your human team has to manually review, so you look at 1-2 things and then move on with your best guess. With AI, they're able to bring much more rigor to their most technical work. In this episode, he shows us: - how a coding agent can run a full matrix of benchmarks against ever open source column store; something no eng had time to manually do before - how to build evals the same way you'd write a PRD - how he uses his best engineer's "vibe check" as the gold standard, and scales it across the product as scoring functions This is an episode by engineers for engineers, where Ankur and I geek out on CEOs who code, brute force coding agents, and why you should be using AI to solve your hardest engineering problems. Watch now:
1:17

"What you do is you prioritize the top few benchmarks and then you probably bullshit the rest." We talk a lot about how AI is making coding easier for non-technical folks, but don't hear much about how the most elite engineers are delegating their most technically complex work. Ankur Goyal (CEO Braintrust) and team has to deliver huge volumes of data at lightning fast speeds, which means they're always looking at ways to optimize their DB stack. The problem? Technical hypotheses are expensive and slow to test when your human team has to manually review, so you look at 1-2 things and then move on with your best guess. With AI, they're able to bring much more rigor to their most technical work. In this episode, he shows us: - how a coding agent can run a full matrix of benchmarks against ever open source column store; something no eng had time to manually do before - how to build evals the same way you'd write a PRD - how he uses his best engineer's "vibe check" as the gold standard, and scales it across the product as scoring functions This is an episode by engineers for engineers, where Ankur and I geek out on CEOs who code, brute force coding agents, and why you should be using AI to solve your hardest engineering problems. Watch now:

claire vo 🖤

17,764 просмотров • 2 месяцев назад

We've built 40+ AI agents and internal tools. The hardest part is Context Creation. AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop. Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools. As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions. We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context. Here's how it works: We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it. Then our FDE Factory Agents builds in their expertise in minutes: > Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec > Scope Agent checks the spec against the development roadmap, validates it, and hands it off > Engineering Agent builds a new feature and wires the integration > QA Agent runs tests to prove to itself it works > PR merges, feature goes live, product updates itself in real time It's like the nontechnical stakeholder wrote the code without even knowing it. Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers. But nontechnical people are capped on what they can build without product people and engineers. The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production. Context Creation is the first and most important step in our FDE lifecycle, and we just automated it. Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise. PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.
3:40

We've built 40+ AI agents and internal tools. The hardest part is Context Creation. AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop. Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools. As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions. We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context. Here's how it works: We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it. Then our FDE Factory Agents builds in their expertise in minutes: > Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec > Scope Agent checks the spec against the development roadmap, validates it, and hands it off > Engineering Agent builds a new feature and wires the integration > QA Agent runs tests to prove to itself it works > PR merges, feature goes live, product updates itself in real time It's like the nontechnical stakeholder wrote the code without even knowing it. Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers. But nontechnical people are capped on what they can build without product people and engineers. The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production. Context Creation is the first and most important step in our FDE lifecycle, and we just automated it. Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise. PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.

Mike Fishbein

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

🚨 ANNOUNCING THE WORLD'S FIRST VIBE CODING AGENT FOR APIs. Vibe coders just became LEGIT backend engineers. With ONE PROMPT, you can create an entire microservice and host it on Abacus AI Deep Agent. Vibe coders can now go toe-to-toe with backend engineers and create an API, a Telegram bot, or any AI service. The AI takes care of everything. - creating an API spec - implementing it and hosting it - using a back-end database for tracking - giving you a test bed - providing you with a ready-to-use endpoint! Backend engineers are expensive; now you can start vibe-coding their projects in English.
0:47

🚨 ANNOUNCING THE WORLD'S FIRST VIBE CODING AGENT FOR APIs. Vibe coders just became LEGIT backend engineers. With ONE PROMPT, you can create an entire microservice and host it on Abacus AI Deep Agent. Vibe coders can now go toe-to-toe with backend engineers and create an API, a Telegram bot, or any AI service. The AI takes care of everything. - creating an API spec - implementing it and hosting it - using a back-end database for tracking - giving you a test bed - providing you with a ready-to-use endpoint! Backend engineers are expensive; now you can start vibe-coding their projects in English.

Bindu Reddy

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

Excited to introduce you to Seb, the coding agent for hardware. Seb is trained for low level systems in highly-regulated environments. Thank you to the engineers and companies that already trust Seb with their hardware. The feedback from hundreds of Firmware, Embedded, and Hardware Engineers has been invaluable. If you are building new hardware or updating a legacy system, Seb is here to help. Get started today at And as a thank you from the Root Access team -- the first 100 engineers to use promo code RAGE50 get 50% off their first month of Pro!
0:57

Excited to introduce you to Seb, the coding agent for hardware. Seb is trained for low level systems in highly-regulated environments. Thank you to the engineers and companies that already trust Seb with their hardware. The feedback from hundreds of Firmware, Embedded, and Hardware Engineers has been invaluable. If you are building new hardware or updating a legacy system, Seb is here to help. Get started today at And as a thank you from the Root Access team -- the first 100 engineers to use promo code RAGE50 get 50% off their first month of Pro!

Ryan Eppley

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

"Vibe coding is NOT the same as using AI to write code that's reviewed, tested, and maintained." Here's my new episode with Lee Robinson (Cursor's Head of AI Education) where he shows how to build AI apps properly using planning, test-driven development, agent workflows, and more. Some tips from Lee: 1. Work with AI to create a detailed technical plan upfront including requirements, design preferences, and your preferred tech stack. 2. Ask AI to write tests so that it can check its own work. Add this to the plan: "Write unit tests for business logic, e2e tests for core user journeys." 3. Add "make descriptive commits" to your initial plan so that you can track what AI changed and why. 📌 Watch our beginner-friendly tutorial now: Also available on: Spotify: Apple: Newsletter:
0:52

"Vibe coding is NOT the same as using AI to write code that's reviewed, tested, and maintained." Here's my new episode with Lee Robinson (Cursor's Head of AI Education) where he shows how to build AI apps properly using planning, test-driven development, agent workflows, and more. Some tips from Lee: 1. Work with AI to create a detailed technical plan upfront including requirements, design preferences, and your preferred tech stack. 2. Ask AI to write tests so that it can check its own work. Add this to the plan: "Write unit tests for business logic, e2e tests for core user journeys." 3. Add "make descriptive commits" to your initial plan so that you can track what AI changed and why. 📌 Watch our beginner-friendly tutorial now: Also available on: Spotify: Apple: Newsletter:

Peter Yang

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

CLAUDE CODE IS NOW FREE AND YOU CAN BUILD AN ENTIRE AI CODING SYSTEM WITH 1M CONTEXT, AGENT OS AND OBSIDIAN MEMORY WITHOUT PAYING FOR ANY OF IT. The stack gets smarter over time and costs you nothing to run.
0:34

CLAUDE CODE IS NOW FREE AND YOU CAN BUILD AN ENTIRE AI CODING SYSTEM WITH 1M CONTEXT, AGENT OS AND OBSIDIAN MEMORY WITHOUT PAYING FOR ANY OF IT. The stack gets smarter over time and costs you nothing to run.

0xMarioNawfal

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