@Bhavani_00007 The concept of an IDE was a mistake from the beginning. VS Code was/is the solution. Now they tried to much to become an IDE and some of the purity is gone, but it's still a lot better then any other way of writing code. (shut up vim people) :)
@nalinrajput23 The tools don't matter, only the models do. You can make it write what ever ability you feel like the tool of choice is missing as an agent. The LLMs gladly do it for you.
I am sorry Claudette, you've been a sexy beast, but you always wanted so many expensive gifts. I meet a Chinese Model called "Kimi" .. just as sexy, and she is happy when I make her breakfast.
@manojdotdev I was expecting you getting endless shit for this barely being considered code at all. But I guess since we all just prompt these days, and hard shit became easy (backend) but frontend still being hard (because AI doesn't understand UI/UX) this is code now.
@elonmusk In the age of AI, I think of problems and let AI solve them. What I'm thinking about right now is the democratization of AI, for people to have something to battle against an increasingly complicated world. So user friendly local AI. So I'm interested in cheaper compute!
Now that the AI5 chip design is in good shape, Tesla will restart work on Dojo3.
If you’re interested in working on what will be the highest volume chips in the world, send a note to AI_Chips@Tesla.com with 3 bullet points on the toughest technical problems you’ve solved.
@rutu_3 The all important question is, would it been faster to complete the whole project without the "prototype" ? As much it is annoying to a developer to sort out those kinds of projects, there is net value in vibe coded prototypes.
DON'T VIBE CODE YOUR PROJECTS PLS!!
Recently, I got a project from a client who had vibe coded his entire web platform. Everything was hosted, and it seemed to work fine until he decided to scale it and make it production ready.
He came to me and said, “We need to do this and that. Let me know when you’re done.”
The problem was that the project had multiple artifacts, all vibe coded, spread across different tech stacks. The codebase was huge and inconsistent.
It took me four days just to set it up locally, and there are still parts of the code that I can’t fully understand.
I have a little over one year of experience, and this situation made me doubt myself. I started wondering whether I am capable of writing and understanding a project like this.
So please, don’t vibe code. It may work initially, but it creates serious problems when it’s time to scale or go production ready.
@ganyicz AI is there to let you do things you can't or are not brave enough to try. It's still a lot of work to get things right, but for me, overall, my output at least doubled. And I'm experimenting more, learning how to really understand and desribe problems.
@ganyicz The thing is, if you know how to solve it efficiently, you either work out a plan with the AI specifying what solutions work best, prompting it do go the most efficient route, and you let it interate over the code 2 or 3 times, or you just write it yourself.