Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

These are my essential AI coding skills I use to keep code quality high and not bloated when AI writes and merges my code for me. This is video 5 of 7 in my “how to become a 10x ai-native developer” series, and in the first 4 videos I...

170,600 Aufrufe • vor 1 Monat •via TikTok

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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 Aufrufe • vor 5 Monaten

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,227,054 Aufrufe • vor 2 Jahren

Everyone's talking about vibe coding without looking at code. I was skeptical. I decided to give it a shot on a challenging problem and was blown away by what I could accomplish in 8 hours. I'm not skeptical anymore, but I also do NOT think it kills SaaS Notes: - I tried to replicate some of my favorite features from the Solve-It platform as a jupyter extension - I've tried this many times before, and it didn't work. - I gave my agent specific testing tools that I packaged as skills. I used AI to write the skills. I found the right testing workflow for this Jupyter extension by having AI peruse lots of other extensions and the Jupyter source code. - I had the AI write and maintain a large suite of tests the whole time. I think this was important in keeping the AI on track. - I watched the diffs and the thinking traces as they streamed by. From time to time, I would see something very suspicious like " try ... except: pass" And would stop the AI and tell it to stop this behavior. Then trigger a comprehensive code review using AI. - Most importantly, I don't think this kills SasS at all. Even if I can create software that replicates some of my favorite features, there is an insanely long tail of paper cuts and features I don't want to manage. The models and capabilities are improving so fast that I don't want to constantly tune everything. So I would rather leave that up to people who are focused on that daily and have good taste, with the knowledge that it has been battle tested against many users.

Hamel Husain

49,184 Aufrufe • vor 10 Monaten

This might be the best "AI Engineer" I've tried so far. ​ I'm an old school developer who started 30 years ago. I feel very uncomfortable letting AI take control of my code, but for the sake of science, I spent two hours building an application that took me weeks to build a couple of years ago. ​ I used Pythagora, a brand new tool backed by Y Combinator. They just released to the public. ​ Keep in mind that I use AI every day to write code, but Pythagora is something different: it's a tool that leads, and uses you—the human—as the copilot. ​ I go into more details in the video, but here is the TLDR; ​ 1. Holy molly! We've made a ton of progress on this front! This is way better than Devin when I tested it a few months back. ​ 2. Love the approach of generating a plan with sub-tasks before writing any code. ​ 3. The tools never tries to do too much: it tackles every small task one at a time, and gives you instructions so you test everything. ​ 4. It does exactly what you'd do when it gets stuck: writes a bunch of logs and uses those to correct itself. Pretty neat! ​ 5. It's fast. It runs locally. It's an extension to Visual Studio Code. ​ I'm impressed, but I don't think this tool is for me. ​ I'm not the type of developer who's ready to relinquish control. I felt I had no connection with the code because I didn't write it. It was not my code. ​ I know many people who don't care about this. I know many people who will get tremendous value out of Pythagora. I hope they keep pushing the limits, providing feedback, and helping this get to a point where old folks like me feel more comfortable using it. ​ Don't take my word for it. The best thing you can do is to give it a try and see how you feel using it. ​ Thanks to the team who built this, for all of the explanations and support, and especially, for sitting and listening to my dumb questions for 2 hours while I tested this.

Santiago

212,151 Aufrufe • vor 2 Jahren

There's so much focus on "how can AI do my work for me?" I think the more important question is "what work can I now do with AI that I would have never attempted before?" Earlier this year I wrote freestiler, a vector tiling engine for R and Python, with the help of Claude and Codex. I knew what the ideal engine looked like and how it would work at a high level. I didn't know how to put it together, and I don't know Rust, the language I wanted under the hood. Previously I would never have attempted this project as the ROI wasn't there. It would have taken me a year or more to learn the internals of a vector tiling engine and enough Rust to implement one. With Opus-level models, I could take it on. freestiler now powers all my vector tiling pipelines, including the map below rendering 143 million jobs from LODES, and it has 114 GitHub stars. Building this way has required a different set of skills. I don't review the code line by line. I set up adversarial agents to do that and write the test suites. What I review is the architecture, the behavior, and the results. Agent teams surface findings and explain their reasoning; I evaluate and critique. My job isn't to stress over code formatting, but instead to focus on questions like whether the engine is designed right, whether the output is correct, and if the UX makes sense. This means that I haven't "replaced my work." I've taken on entirely new work, with the help of agents, that I would have never done otherwise. It has taken some getting used to shipping code I haven't personally typed. In the old way of working, I built understanding through writing that code. Now I build understanding through managing the project - writing a spec, reviewing structure, evaluating UX. And that's helped me think a whole lot bigger in terms of what I can now do.

Kyle Walker

13,905 Aufrufe • vor 4 Monaten