Latest Titles
-
vibe coding
-
racism in NeurIPS2024
-
moondream
-
genie2
-
stephen wolfram
-
notlikeai.com
-
HunyuanVideo
-
amurex
-
tedai
-
Artificial Intelligence, Scientific Discovery, and Product Innovation
-
daron acemoglu
-
Adapting While Learning
-
Centaur
-
Differentiation and Specialization of Attention Heads via the Refined Local Learning Coefficient
-
fish audio agent
-
OpenAI
-
Xena vision
-
alan turing
vibe coding
1.
here is a tip from fkdev. Here Fatih mentions the importance of creating a folder structure even before start is crucial for success.
He reports to get flatter file structure with better. results. Seems worth giving a shot.
Source: https://x.com/fkadev/status/1903040752990470228
2.
I personally love vibe coding. It speeds me up a lot, minimizes the time and effort to validate an idea. But I sometimes feel like losing the control on the code. What if an ai agent can’t fix a bug? What if I get to lazy and lack my ability to handle amending the code? I feel like there should be a limit, a blend of traditional coding and vibe coding to retain control on the codebase. But usually laziness wins and I skip my part, to be handled by the ai agent. I hope that does not go crazy over time.
3.
A new type of coding, named by Andrej Karpathy in a tweet and got a place in coding world. Andrej proposes a new method of coding, focusing on the prompts and the vibe, forgetting about the code as Cursor, Wİndsurf and other coding agents get better and better.
Here, the user simply prompts the target to be reached. Simply pushes the “accept all” button and proceeds with what the coding agent gives as the result. In the event of errors, the error message is pasted into the coding agent, for bug fixes and upgrades. Similarly, any request would be handled by the coding agent.
The user here nearly forgets about the code. Instead, focuses on the functionality and “vibe” of the piece of software. This method speeds up the coder drastically, but there are drawbacks, of course. The first and obvious question is the complexity of the project one can “vibe code”, of course. It naturally handles MVP’s, side projects, weekend hassles but can it go beyond? Can one vibe-code a complex project, having multiple endpoints, api managements, scaling concerns and the like? Or, when will be able to vibe-code complex projects, with the current advancement speed? Will it depend on our vibe coding abilities or improvements on ai agent capabilities?
The tweet: https://x.com/karpathy/status/1886192184808149383