🧠 When development is as easy as building LEGO, do programmers still need to write code?
At the roundtable of TinTinWeekly on May 14th, we had a chat with the three responsible persons from @btspoony | @flow_blockchain, @BinaryHB | @NextDotID, and @akirawuc | TingTogether about "Vibe Coding" - this seemingly trendy development paradigm. In fact, behind it lies the agile revolution of the next generation of Web3 products.
From AI collaborative code writing and drag-and-drop development to contract security and the reconfiguration of collaborative logic, we are attempting to answer a key question: Will future developers still need to be able to write code, or will they have to be able to "train AI"? Now, let 's take a look back at the roundtable 👇
💡 1. What is Vibe Coding?
Vibe Coding = Modular development + AI collaboration + Visual interaction + real-time collaboration experience
A development approach similar to building with blocks and drag-and-drop: combining highly abstract components/modules to form a complete application.
Utilize AI to assist in code generation, rapid debugging, prototype construction, and even participate in logic construction and testing.
The biggest difference from traditional development lies in lowering the threshold, enhancing agility, and introducing new collaboration paradigms and code quality challenges at the same time.
🧠 2. Guest Insights summary
🔹 Bohao Tang (Flow)
Bohao shared the "Documentation as AI capability" practice that Flow is experimenting with: structuring the Flow SDK documentation and importing it into the AI model, enabling developers to ask questions through natural language and obtain automatic output such as code snippets and deployment methods. This greatly enhances development efficiency, especially suitable for Web3 beginners and small teams.
However, he emphasized that the issues of AI's errors and illusions remain unresolved. In the development of contracts involving asset security, AI should be limited to being a "code completion tool", and human control over key logic should be retained.
🔹 Duan Shao (https://t.co/0r6m5esTOd)
He believes that this paradigm enables "non-technical roles" such as products and designs to also participate in the construction of product prototypes, blurring the traditional boundary between "technology" and "non-technology".
Vibe Coding enables non-technical roles such as product managers and designers to participate in "prototype building", and the "entry threshold" for development is reconstructed.
But he also pointed out the "inertia trap of AI" : when every step relies on model prompts, we may lose sensitivity to code structure, debugging, and logical chains.
He emphasized that in the long term, the hard skills of "reading code, understanding architecture, and refining debugging" are still needed.
🔹 Akira Wu (TingTogether)
Akira emphasized the significance of Vibe Coding for small teams and early-stage projects and shared the practical experience of TingTogether in practicing Vibe Coding:
In small teams and start-up projects, AI reduces cumbersome documentation writing, testing processes and deployment writing, and is particularly suitable for the rapid verification of product ideas in the early stage.
At the same time, a warning was issued: "If there is no good documentation, testing and going live mechanism, a 'seemingly usable' demo may have major problems on the chain."
🔍 3. Core discussion topics
🛡️ Ease of use vs. Security
All the guests mentioned that Vibe Coding has brought about a leap in development efficiency, but at the same time, it may also weaken control over the essence of the code.
Especially in the Web3 scenario, "Code is contract and contract is fund", security is the overriding bottom line. A strong Code Review and test case mechanism must be established to ensure the security of going online.
🧰 Core Competence Shift for developers
Bohao: In the future, developers will need to be like a hybrid of "product manager + architect + auditor".
Duan Shao: Development skills will not be abolished but "abstracted". The more fundamental and complex the technical ability is, the scarcer it becomes.
Akira: Writing fast does not equal writing correctly. The ability to "judge whether it is correct" is the key barrier that determines a developer's value.
🤝 Reinventing the collaboration paradigm
AI plays a new role in collaborative development, for example:
Automatically generate unit tests;
Module disassembly suggestions
Unify the code style by referring to the document.
The team needs to clearly define which tasks should be assigned to AI and which must be reviewed manually, and establish traceable collaboration processes (version control, collaboration annotations, etc.).
✅ Conclusion: A Portrait of future developers
It's not about whether AI will replace developers, but whether developers can make good use of AI.
Under the wave of Vibe Coding, the role of developers will shift to: designer + organizer + quality inspector + code maintainer;
The underlying capabilities are still important. They enable you to "step more steadily" above the high abstraction layer.
The truly leading person is not the one who writes the most code, but the one who can have AI write the right code for them.
#TinTinWeekly #VibeCoding #Developer #AI #Review #Event