Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Better Cursor alternative? I've been playing with the new AI IDE Windsurf launched by Codeium past few days, and the result was impressive, particularly: 1. Code base understanding: One thing Windsurf did really well is its understanding of the whole code base & dependencies; This led to a big...

64,713 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von Julian Harris
Julian Harrisvor 1 Jahr

@codeiumdev If I’m working with APIs or libraries that are new or changed in the last 12 months (hint: almost everything) the only way code-gen works reliably for me is if there’s a web search in the loop. I’ve struggled to get Cursor to do this reliably. What about Windsurf?

Profilbild von Jason Zhou
Jason Zhouvor 1 Jahr

@codeiumdev Ideally yes.. I just paste doc in, and I found windsurf follows better than cursor in my experience; But still, it tends to revert back to old knowledge unless you prompt it hard

Profilbild von Edwardooo
Edwardooovor 1 Jahr

@codeiumdev I have been using cursor for three months daily. I just tried Windsurf. I say it is pretty smart. It learned the code base to make a new page that plot all the locations. (with auto zoomout to see all the spots )

Profilbild von Phatic
Phaticvor 1 Jahr

@codeiumdev Welp

Profilbild von Jason Zhou
Jason Zhouvor 1 Jahr

@codeiumdev Oh woah, didn’t know about this, pretty exciting

Profilbild von Louiepecan.base.eth🗡🛡
Louiepecan.base.eth🗡🛡vor 1 Jahr

@codeiumdev @grandorganics

Profilbild von George Siosi Samuels
George Siosi Samuelsvor 1 Jahr

@codeiumdev Just downloaded

Profilbild von Axel Sachmann
Axel Sachmannvor 1 Jahr

@codeiumdev Thx for the great presentation 🙏

Profilbild von konstantinpaulus
konstantinpaulusvor 1 Jahr

@codeiumdev

Profilbild von pharo
pharovor 1 Jahr

@codeiumdev I tried it today Feels more powerful than cursor But I have to test it more

Ähnliche Videos

Will tools like Windsurf result in fewer software engineers? "It feels like it's people hating software engineers who say this" says Windsurf cofounder and CEO Varun Mohan In today's podcast episode, we go into the engineering challenges (and tradeoffs!) of building an AI-powered IDE like Windsurf and how Windsurf has changed how the Windsurf dev team (and non-developers!) write software. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • CodeRabbit — Cut code review time and bugs in half. Use the code PRAGMATIC to get one month free at • Modal — The cloud platform for building AI applications Get started at Three of my takeaways: 𝟭. 𝗔𝗜-𝗽𝗼𝘄𝗲𝗿𝗲𝗱 𝗜𝗗𝗘𝘀 𝗺𝗮𝗸𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗺𝗼𝗿𝗲 “𝗳𝗲𝗮𝗿𝗹𝗲𝘀𝘀” 𝗮𝗻𝗱 𝗰𝗼𝘂𝗹𝗱 𝗿𝗲𝗱𝘂𝗰𝗲 𝗺𝗲𝗻𝘁𝗮𝗹 𝗹𝗼𝗮𝗱. I asked Varun how using Windsurf changed the workload and output of engineers — especially given how most of the team have been software engineers well before LLM coding assistants were a thing. A few of Varun’s observations: • Engineers are more “fearless” in jumping into unfamiliar parts of the codebase — when, in the past, they would have waited to talk to people more familar with the code. • Devs increasingly first turn to AI for help, before pinging someone else (and thus interrupting that person) • Mental fatigue is down, thanks to tedious tasks can be handed off to prompts or AI agents Varun stressed that he doesn’t see tools like Windsurf eliminating the need for skilled engineers: it simply changes the nature of the work, and can increase potential output. 𝟮. 𝗙𝗼𝗿𝗸𝗶𝗻𝗴 𝗩𝗦 𝗖𝗼𝗱𝗲 𝘁𝗵𝗲 “𝗿𝗶𝗴𝗵𝘁” 𝘄𝗮𝘆 𝗺𝗲𝗮𝗻𝘀 𝗱𝗼𝗶𝗻𝗴 𝗮 𝗹𝗼𝘁 𝗼𝗳 𝗶𝗻𝘃𝗶𝘀𝗶𝗯𝗹𝗲 𝘄𝗼𝗿𝗸. While VS Code is open source and can be forked: VS Code Marketplace and lots of proprietary extensions. For example, when forking VS Code, the fork is not allowed to use extensions like Python language servers, remote SSH, and dev containers. The Windsurf team had to build custom extensions from scratch — which took a bunch of time, and users probably did not even notice the difference! However, if Windsurf had not done this, and had broken the license of these extensions, they could have found themselves in legal hot water. So forking VS Code “properly” is not as simple as most devs would normally expect. 𝟯. 𝗖𝗼𝘂𝗹𝗱 𝘄𝗲 𝘀𝗲𝗲 𝗺𝗼𝗿𝗲 𝗻𝗼𝗻-𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗰𝗿𝗲𝗮𝘁𝗲 “𝘄𝗼𝗿𝗸 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲?” 𝗠𝗮𝘆𝗯𝗲. One of the very surprising stories was how Windsurf’s partnership lead (a non-developer) created a quoting tool by prompting Windsurf. This tool replaced a bespoke, stateless tool that the company paid for. Varun and I agreed that a complex SaaS that has lots of state and other features is not really a target to be “replaced internally.” However, simple pieces of software can now be “prompted” by business users. I have my doubts about how maintainable these will be in the long run: just thinking about how even Big Tech struggles with internal tools built by a single dev, and then when this dev leaves, no one wants to take it over.

Gergely Orosz

34,355 Aufrufe • vor 1 Jahr

I built an agent that answers machine-learning questions. It's autonomous, and the best part is that I built the whole thing without writing a single line of Python code. Here is what I did and how I did it: Over a year ago, a friend and I built a site that publishes multi-choice questions. You get a new one every day. I decided to have GPT-3.5 answer questions. Here is what I needed to build: 1. Connect to the site's API to retrieve today's question 2. Extract the question and the potential choices 3. Connect to OpenAI's API and ask GPT-3.5 to answer the question 4. Parse the answer from the model 5. Submit the answer back to the API to get the score Not difficult. Likely several hours of work. But I didn't have to write any code. I built the whole thing by dragging and dropping components using Vellum is a YC-backed platform for developers to build LLM applications. They are the only ones I've seen offering this functionality. They sponsored this post, and their team helped me with all my questions while I built this. I created a workflow. The platform supports several node types to build whatever you have in mind. I show how I put the whole thing together in the attached video. The only code I had to write was a few lines of Jinja to parse and transform the API and the LLM results. There are three lessons I want to share from this experience: First, the best possible code is the one you didn't write. I'm a big fan of no-code tools because they help me materialize my ideas fast. They help product people, designers, and no coders collaborate on the solution. Second, Large Language Models are sensitive to how you prompt them. Small changes to prompts can make a big difference in results. This is more pronounced when you are building a multi-step workflow. Third, automated testing and evaluation for prompts is critical. There aren't many companies thinking about this. They'll have a hard time moving from a demo phase. The attached video will show you what I did.

Santiago

309,825 Aufrufe • vor 2 Jahren