Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Cline v3.39 can now generate diff view comments to explain the changes he makes 🚀 You can also ask for help reviewing pull requests, recent commits, and more! Writing code is easy–reviewing and approving is the new bottleneck, and we're excited for you to try this new feature.

Saoud Rizwan

19,213 subscribers

200,483 görüntüleme • 11 ay önce •via X (Twitter)

Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

33 Yorum

eigenrobot profil fotoğrafı

eigenrobot10 ay önce

delete your account

kache profil fotoğrafı

kache10 ay önce

Cline smells like shit

The Reverend profil fotoğrafı

The Reverend10 ay önce

Removed Cline from my machine. Fuck off loser. You lost the plot.

The Hero of KVcache profil fotoğrafı

The Hero of KVcache10 ay önce

Are you going to add support for text-to-smell models?

Chud profil fotoğrafı

Chud10 ay önce

This company will fail for 2 reasons: 1. It doesn’t provide any marginal value greater than what you already get from copilot 2. It is hostile to White men Wishing you the worst 😘

mischief - very special 🎖️🏆 profil fotoğrafı

mischief - very special 🎖️🏆10 ay önce

stinky smelly

Kartikay verma profil fotoğrafı

Kartikay verma11 ay önce

Yo! This your guy?

Galloway Farms profil fotoğrafı

Galloway Farms10 ay önce

For future reference: Being cowardly is never a winning move.

Chriscoveries profil fotoğrafı

Chriscoveries10 ay önce

reply here with cline replacements that aren’twoke af

akhivae profil fotoğrafı

akhivae10 ay önce

Sellout

Frameo profil fotoğrafı

Frameo10 ay önce

can cline explain the hackaton smell?

Potato profil fotoğrafı

Potato10 ay önce

Hi Porki

John Flory profil fotoğrafı

John Flory10 ay önce

Imagine the smell

Anon profil fotoğrafı

Anon11 ay önce

Cuck Sepoy

Harrison Dimon profil fotoğrafı

Harrison Dimon10 ay önce

Imagine the smell

🇮🇳 orochi genshin (大蛇源心) profil fotoğrafı

🇮🇳 orochi genshin (大蛇源心)11 ay önce

Is racism an official policy of @cline @sdrzn?

FIRE STRICKLIN profil fotoğrafı

FIRE STRICKLIN10 ay önce

Hire him back

Bruce profil fotoğrafı

Bruce10 ay önce

Every time I take a shit I’m reminded of your smell

Mark Milley’s Stylist 🇺🇸 profil fotoğrafı

Mark Milley’s Stylist 🇺🇸10 ay önce

is "develop a spine" on the product roadmap? begone coward

zach profil fotoğrafı

zach10 ay önce

Slop

gcoum profil fotoğrafı

gcoum10 ay önce

jeet tech

Kondratiev Surge profil fotoğrafı

Kondratiev Surge10 ay önce

Who cares. There's an awful smell of decline of it now.

The Last Cry 🌹 profil fotoğrafı

The Last Cry 🌹11 ay önce

Hey Sapudu, is it okay to be a bigoted racist at @Cline?

Johnny Giagani profil fotoğrafı

Johnny Giagani10 ay önce

Here’s that tweet you deleted.

After Dinner profil fotoğrafı

After Dinner10 ay önce

No one should use this software. You're a disloyal CEO. If you're using this software, delete it, and use Cursor or any other tool.

Autobahn Bisquick profil fotoğrafı

Autobahn Bisquick10 ay önce

I had actually really wanted to try cline’s Task Timeline but I think I’ll look for an alternative now.

Pay Tree Arch, Context Dependent profil fotoğrafı

Pay Tree Arch, Context Dependent10 ay önce

Feature request: please add support for an AI model which reads the text of a tweet containing a joke and tells us how likely we are to lose our job for posting it.

CryptoAcid (💙,🧡)🦇🔊 profil fotoğrafı

CryptoAcid (💙,🧡)🦇🔊10 ay önce

Do you smell too?

Atif Saleem profil fotoğrafı

Atif Saleem11 ay önce

Nice, now I don't need to ask the agent to walk me through what you just implemented and its code every time.

chooch skookum profil fotoğrafı

chooch skookum10 ay önce

Cline sucks.

That guy profil fotoğrafı

That guy10 ay önce

Should've stood behind your employee

- El_Mariachi - profil fotoğrafı

- El_Mariachi -10 ay önce

Delete this account

Tr1xxkst3r profil fotoğrafı

Tr1xxkst3r10 ay önce

You have rodent physiognomy.

Benzer Videolar

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,477 görüntüleme • 11 ay önce

You've got to get to a higher leverage point and reviewing only the code is not it. Start reviewing the system. I made a skill you can use to generate a system review in your PRs to make reviewing changes much faster and more fruitful.

You've got to get to a higher leverage point and reviewing only the code is not it. Start reviewing the system. I made a skill you can use to generate a system review in your PRs to make reviewing changes much faster and more fruitful.

Kent C. Dodds 🐨

15,222 görüntüleme • 3 ay önce

Plannotator 0.22.0 is out. Code Review (is not dead yet): - Guided reviews give you a list of changes with semantic overviews, ordered by importance & where you need to spend your time reviewing. Inspired by Linear, this works for local and PR changes . You don't need the best models or high reasoning levels to use this! - Pi and Copilot are added as agent review providers. - A new default `git status` view is added. - A new `commits` view is added to easily navigate all commits and view their descriptions+changes.

Plannotator 0.22.0 is out. Code Review (is not dead yet): - Guided reviews give you a list of changes with semantic overviews, ordered by importance & where you need to spend your time reviewing. Inspired by Linear, this works for local and PR changes . You don't need the best models or high reasoning levels to use this! - Pi and Copilot are added as agent review providers. - A new default `git status` view is added. - A new `commits` view is added to easily navigate all commits and view their descriptions+changes.

plannotator

28,086 görüntüleme • 4 ay önce

A lot of you have been asking for Grok Bot to be able to access your XChat messages and message requests to help manage busy inboxes. excited to share this is now live! I've had my Grok Bot reviewing new message requests all week, approving them, and helping me stay on top of my inbox.

A lot of you have been asking for Grok Bot to be able to access your XChat messages and message requests to help manage busy inboxes. excited to share this is now live! I've had my Grok Bot reviewing new message requests all week, approving them, and helping me stay on top of my inbox.

Paul Vann

329,256 görüntüleme • 18 gün önce

introducing diffmap: a new document format for planning and reviewing agent code. The idea behind diffmap is letting you review the important design changes, not massive line diffs. "Write a diffmap spec for the changes on this branch. Use I've been working and iterating on this skill for more than 2 months! I use it every day for any big feature or refactor. Excited to finally make it public

introducing diffmap: a new document format for planning and reviewing agent code. The idea behind diffmap is letting you review the important design changes, not massive line diffs. "Write a diffmap spec for the changes on this branch. Use I've been working and iterating on this skill for more than 2 months! I use it every day for any big feature or refactor. Excited to finally make it public

Tanishq (tk)

50,674 görüntüleme • 4 gün önce

Codex now runs in your IDE Available for VS Code, Cursor, and other forks, the new extension makes it easy to share context—files, snippets, and diffs—so you can work faster with Codex. It’s been a top feature request, and we’re excited to hear what you think!

Codex now runs in your IDE Available for VS Code, Cursor, and other forks, the new extension makes it easy to share context—files, snippets, and diffs—so you can work faster with Codex. It’s been a top feature request, and we’re excited to hear what you think!

OpenAI Developers

182,758 görüntüleme • 1 yıl önce

DeBox New Feature is LIVE! Now supports token price tags! Simply type $+token to generate real-time price and changes. Smarter and more interactive for your community. Try it now: $BTC, $ETH… it’s that easy! #DeBox #TokenPrices #Web3

DeBox New Feature is LIVE! Now supports token price tags! Simply type $+token to generate real-time price and changes. Smarter and more interactive for your community. Try it now: $BTC, $ETH… it’s that easy! #DeBox #TokenPrices #Web3

DeBox

21,933 görüntüleme • 1 yıl önce

We've built a massive verification bottleneck: • 72% of developers use AI to generate code every day • 96% of them don't fully trust it Writing code is now free. All the work now is verifying that the code does what it's supposed to. According to a new State of Code Survey, almost half of the respondents believe the number one skill that will matter most in the coming years is "reviewing and validating AI-generated code for quality and security". Not prompt engineering or vibe-coding, but checking AI's work.

We've built a massive verification bottleneck: • 72% of developers use AI to generate code every day • 96% of them don't fully trust it Writing code is now free. All the work now is verifying that the code does what it's supposed to. According to a new State of Code Survey, almost half of the respondents believe the number one skill that will matter most in the coming years is "reviewing and validating AI-generated code for quality and security". Not prompt engineering or vibe-coding, but checking AI's work.

Santiago

16,299 görüntüleme • 9 ay önce

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

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

The Pragmatic Engineer

39,073 görüntüleme • 5 ay önce

If you are reviewing 100% of your AI-generated code by hand, you aren't moving fast enough. It's just impossible. Reviewing code has become the biggest bottleneck in software. Here is how to make this better:

If you are reviewing 100% of your AI-generated code by hand, you aren't moving fast enough. It's just impossible. Reviewing code has become the biggest bottleneck in software. Here is how to make this better:

Santiago

20,167 görüntüleme • 4 ay önce

New in Chrome DevTools: Annotate performance findings with Gemini! You can now ask Gemini to explain performance traces. Specifically you can generate annotations about events in the performance trace. This is a total game-changer. Double-click an event in the Main track, then click Generate label next to the input field. Gemini can suggest a label based on the stack trace and context. Try it out and let us know what you think!

New in Chrome DevTools: Annotate performance findings with Gemini! You can now ask Gemini to explain performance traces. Specifically you can generate annotations about events in the performance trace. This is a total game-changer. Double-click an event in the Main track, then click Generate label next to the input field. Gemini can suggest a label based on the stack trace and context. Try it out and let us know what you think!

Addy Osmani

88,311 görüntüleme • 1 yıl önce

The Gen48 participants are the first group to use Gen4 References, but let me briefly explain why this tool is going to change the way you work in Runway: Seamless consistency. Being able to seamlessly generate the exact same characters in new outfits, in new locations (keeping those locations consistent) AND generate realistic B-roll for each location is something that has been extremely difficult to do until now. New angles. New perspectives. New compositions. Gone are the days of countless hours compositing and tweaking a composition to just get it to be "close enough"... With references you can just do things and ask for things in a very conversational way. I'm super excited for people to try this when we release to everyone!

The Gen48 participants are the first group to use Gen4 References, but let me briefly explain why this tool is going to change the way you work in Runway: Seamless consistency. Being able to seamlessly generate the exact same characters in new outfits, in new locations (keeping those locations consistent) AND generate realistic B-roll for each location is something that has been extremely difficult to do until now. New angles. New perspectives. New compositions. Gone are the days of countless hours compositing and tweaking a composition to just get it to be "close enough"... With references you can just do things and ask for things in a very conversational way. I'm super excited for people to try this when we release to everyone!

Always Generating

46,752 görüntüleme • 1 yıl önce

With our new Ask Maps feature, you can truly ask anything about anywhere, with help from the latest Gemini models. Ready to roll? Try asking for a walking ghost tour in your city. 👻 Now rolling out in the US and India.

With our new Ask Maps feature, you can truly ask anything about anywhere, with help from the latest Gemini models. Ready to roll? Try asking for a walking ghost tour in your city. 👻 Now rolling out in the US and India.

Google Maps

70,261 görüntüleme • 7 ay önce

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Tibor Blaho

136,117 görüntüleme • 2 yıl önce

We’re introducing soon a brand new pull request view in the @GitHub Copilot App for chatting and reviewing with different models.

Maxime De Greve

25,689 görüntüleme • 3 ay önce

Reviewing agents is the new bottle neck. What if you could review your whole frontend at once? Checkout Decode's new commenting system that makes giving agents multi-screen feedback, as easy as reviewing a Figma file. Try it out:

Reviewing agents is the new bottle neck. What if you could review your whole frontend at once? Checkout Decode's new commenting system that makes giving agents multi-screen feedback, as easy as reviewing a Figma file. Try it out:

Francois Laberge

22,208 görüntüleme • 3 ay önce

Google NotebookLM is absolutely insane, easily the best AI product out there, and it is free to use. The new Mindmap feature makes learning so easy. You can use it to understand your codebase. Just convert your codebase to a single file and try it out.

Google NotebookLM is absolutely insane, easily the best AI product out there, and it is free to use. The new Mindmap feature makes learning so easy. You can use it to understand your codebase. Just convert your codebase to a single file and try it out.

AshutoshShrivastava

241,207 görüntüleme • 1 yıl önce