Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

First version of JetBrains ReSharper for Visual Studio Code coming in hot! ๐Ÿ”ฅ ๐Ÿ—บ๏ธ Navigation & Syntax Highlighting ๐Ÿ–Š๏ธ Editing & Completion ๐Ÿ†• File, Live, Postfix Templates ๐ŸŽญ Rename Refactoring ๐Ÿ’ก Quick-Fixes & Context Actions Give it a try and tell us what you think! ๐Ÿ”—

15,171 Aufrufe โ€ข vor 1 Jahr โ€ขvia X (Twitter)

9 Kommentare

Profilbild von JetBrains ReSharper
JetBrains ReSharpervor 1 Jahr

Going to #MSBuild? Stop by the JetBrains Booth to see ReSharper in VS Code in action! Look up booth #508 to find us: #dotnet #MicrosoftBuild #MicrosoftBuild2025

Profilbild von RedDeer.Games
RedDeer.Gamesvor 4 Jahren

What are your favourite #AAAClock colours ? ๐Ÿ•๐Ÿ•‘๐Ÿ•’๐Ÿ•“๐Ÿ•” Drop screenshots of your clocks in down in the comments โฌ Head to โžก๏ธ for more details! #indiedev #indiegame #IndieGameDev #nintendo #OLED #switchOLED

Profilbild von Bitsy ๐ŸฆŠ
Bitsy ๐ŸฆŠvor 1 Jahr

@code Oh my

Profilbild von Miguel Fialho
Miguel Fialhovor 1 Jahr

@code NeoVim Next?

Profilbild von Elias Bui
Elias Buivor 1 Jahr

@code Hmm

Profilbild von Luiz Thiago
Luiz Thiagovor 1 Jahr

@code OMG

Profilbild von chriscanal
chriscanalvor 1 Jahr

@code ๐Ÿ˜ณ๐Ÿคฏ

Profilbild von Viktor Dzundza
Viktor Dzundzavor 1 Jahr

@code Do you have such plugin for C++ ? I used resharper 10 years ago, it is AMAZING

Profilbild von JetBrains ReSharper
JetBrains ReSharpervor 1 Jahr

@code Thank you, Viktor! No, there's no extensions for C++ for VSC at the moment, and no immediate plans for one. However, we we'll be closely monitoring demand for such a tool. Filing a request on our issue tracker is a good place to record your interest -

ร„hnliche Videos

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 Aufrufe โ€ข vor 1 Jahr

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) ๐Ÿงƒ where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

193,219 Aufrufe โ€ข vor 3 Monaten

New Andrej Karpathy interview Says AI agent failures stem from user skill, not model capability. Poor instructions cause errors. He suggests delegating 20-minute macro actions like coding and research to parallel agents and reviewing their work. --- "I think everything, like so many things, even if they don't work, I think to a large extent you feel like it's a skill issue. It's not that the capability is not there; it's that you just haven't found a way to string together what's available. Like, I didn't give good enough instructions to the agents in the file, or whatever it may be. I don't have a nice enough memory tool that I put in there, or something like that. So, it all kind of feels like a skill issue when it doesn't work to some extent. You want to see how you can parallelize them, and you want to be a 'Pierce tender,' basically. Pierce famously has a funny photo where he's in front of lots of these Codex agents behind the monitor. They all take about 20 minutes if you run them correctly and use high effort. You have multipleโ€”you know, 10 or 20โ€”pull requests checked out. It's just like you can do much larger macro actions. It's not just, 'Here's a line of code, here's a new function.' It's like, 'Here's a new functionality, delegate it to agent one. Here's a new functionality that's not going to interfere with the other one, give it to agent two.' Then, you try to review their work as best as you can, depending on how much you care about that code. You look for these macro actions that you can manipulate your software repository by. Another agent is doing some research, another agent is writing code, another one is coming up with a plan for some new implementation. Everything just happens in these macro actions over your repository. You're just trying to become really good at it and develop a muscle memory for it. It's very rewarding when it actually works, but it's also a new thing to learn. Hence, the psychosis." --- From No Priors YT channel (link in comment)

Rohan Paul

23,122 Aufrufe โ€ข vor 4 Monaten

I just built a self-improving second brain in Claude Code ๐Ÿคฏ A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time โ€” re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: โ†’ Build 3 foundation files once: brand DNA, voice, and customer โ†’ Every skill you create reads from them automatically โ†’ Wire in live data โ€” your ad account, competitor ads, customer reviews โ†’ A weekly routine refreshes the brain with what's actually working โ†’ Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: โ†’ The exact 3-file foundation that runs the whole system โ†’ The skill structure that makes every tool brand-aware by default โ†’ The live-data wiring that keeps it grounded in reality โ†’ The weekly self-improvement loop that keeps it sharp โ†’ The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

17,780 Aufrufe โ€ข vor 1 Monat