Cypherpunks code; let's build "Tutorial Mode"

Learn
, , ,
1

With powerful AI “vibe” coding and product development tools, which technical skills are necessary to build today? eg:

  • command line basics
  • git
  • security best practices
  • text-based problem solving (fka “prompt engineering”)

What might a “zero to one” curriculum for building with Waku look like for the novice developer (expecting full use of current AI tools)?

After participating in my first ETH hackathon at ETHPrague earlier this year and debating what constitutes as “vibe coding” vs. “AI peer programming,” I’ve been keen to work on AI Literacy again (I did this pre-web3); I’m also interested in joining Waku hackathons, and would enjoy building out such a “Tutorial Mode” as I learn.

Any recommendations on where to start or want to help/learn together?

5 Likes
2

I actually really need to learn how to vibe code. I have a very general understanding of what it is, but haven’t had to opportunity of sitting down and messing around with these LLM’s in that manner.

Let’s get after it. I’d be game :ok_hand:t4:

  • Shaq
1 Like
3

I think you still need some high level understanding on how the Internet work.The main issue is that LLMs are mainly “yes-men”, meaning that if you are asking for something that simply does not make sense, they will not push back to give you the knowledge and explanation on why “it’s a bad idea”.

I don’t think CLI, git, etc are necessary. I think more than anything, what matters is your ability to write down requirements or specifications. It’s a scary word, but basically, being able to have a consistent idea of what you wan (which is often boasted at the 99% of problems in customer <> developer relations).

if you can do this, most tools today, and even more tomorrow, should allow you to not touch anything else.

1 Like