Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Windsurf CEO Varun Mohan says engineering comes down to three things: - what to solve - how to solve it - and doing the work AI is already taking over the last two. The best engineers will be the ones who know what's worth building -- and why.

151,116 görüntüleme • 1 yıl önce •via X (Twitter)

10 Yorum

vitrupo profil fotoğrafı
vitrupo1 yıl önce

Windsurf co-founder & CEO Varun Mohan on Lenny's Podcast:

Coral AI News profil fotoğrafı
Coral AI News1 yıl önce

Coral AI is the most powerful AI for documents. See the difference yourself:

Gareth Manning profil fotoğrafı
Gareth Manning1 yıl önce

Education needs to shift from “solve for x” to “solve x or y?”

Tsukuyomi profil fotoğrafı
Tsukuyomi1 yıl önce

so, we're outsourcing the thinking to AI? great, just what we need. engineers will have to channel their inner philosophers to figure out the 'why' while AI does the heavy lifting. good luck with that!

Rippa Sats profil fotoğrafı
Rippa Sats1 yıl önce

Correct 💯 The even deeper 🗝️ is the correct Human+AI collaboration

AJ Chadha profil fotoğrafı
AJ Chadha1 yıl önce

1000% this. Now those “worthless ideas” are suddenly the most valuable things.

cosmichaos profil fotoğrafı
cosmichaos1 yıl önce

Problem solving has been my problem since engineering. 😅😂 Old habits die hard. Although I'm not building anything for years now.

kame hame profil fotoğrafı
kame hame1 yıl önce

@readwise save thread

Figure profil fotoğrafı
Figure1 yıl önce

solid message

justwrapapi profil fotoğrafı
justwrapapi1 yıl önce

AI will do all three

Benzer Videolar

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 görüntüleme • 1 yıl önce