Ask HN: What would you recommend a vibe coder learn about how all this works?
31–40 of 44 posts
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#32Don't you mind about the future. Don't you try to think ahead. Save tomorrow for tomorrow. Think about today instead.
I could give you facts and figures. Even give you plans and forecasts. Even tell you where I'm going.
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#33For the former, I think some hand coding will get the best results.
A large part of "thinking like a programmer" is thinking about the sort of invisible structures that code will produce in a computer's memory when it runs - which is not the same as what's literally written in the code file. IMO, the best way to get a feel for that is to write code yourself, run it, examine the results, etc.
But writing code can be a rather dry activity if you don't have motivation for what to write. The usual vibe coded projects are probably too complex to hand code without experience. I think two good starting points could be Code Katas [1] or the Pico8 game engine [2] (and of course any good "intro to Python" or "intro to JavaScript" tutorial on the web)
--
For the latter, you could maybe start with the history of generative text models (like markov chains) and neural networks. Both technologies are several decades old and sort of form the very basic building blocks that made development of LLMs possible.
In particular, neural networks made use of the gradient descent and backpropagation algorithms that are still the basis of most LLM training processes - even if they might now run for months and take exabytes of training data.
Then there is of course the "Attention is all you need" paper that introduced the Transformer architecture - the kind of latest-generation neural network that underpins most LLMs - and basically started the whole LLM revolution. (It's also the "T" in GPT)
(For historical interest, there is also the whole theory of formal languages/grammars and automata - which was the previous attempt to understand human language with computers. That theory gave us a lot of things - such as the Turing Machine and the entire theory of how to build and read a programming language. What it didn't give us though was a way to process human language...)
--
As for the specific question of how an LLM can take this request in human language and generate that code from it that happens to fullfill all the requirements - that's an active area of research and I honestly doubt that right now anyone understands that in all entirety.
Through I believe Anthropic and LessWrong had some interesting blog posts about this topics where they tried to understand the functions of certain specific neurons in an LLM. See also "Golden Gate Claude".
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#34If you are enjoying vibe coding, the biggest "aha" for me is realizing that software is mostly about managing state, data flow, and failure, not syntax. Once you get how data moves, where state lives, and what happens when things break, a lot of the "magic" disappears. Learning basic debugging and reading stack traces also compounds forever, even with AI. One thing that helped me: think a bit like a PM. Spend time cr…
Its also why you'll hear many engineers opine over functional programming.
Most start by thinking about 1. What does a system do for me?
Then onto 1. What actions does a system do? 2. Where should files and folders live? 3. Where should services live?
and stop there.
But the true key is when you just think about how data moves through your system.
Then you learn to simplify.
No classes, no hidden state, just simple functions with an input and an output and nothing else.
Long story short: Think about your system in data, and learn how to keep your code super simple to help with that thinking
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#35Earlier quoted context omitted.
Hard disagree, the interface hasn't changed at all. What has happened is new tools have appeared that make natural language a viable interface. It is a new lesser interface, not a replacement. Like a GUI, more accessible but functionally restricted. An interface that is conditioned on previously solved tasks, but unable to solve novel ones. What this means is coding becomes accessible to those looking to apply someth…
I've seen non-programmers successfully launch real apps — not toy projects — through vibe coding. I'm doing it myself, and I'm about to ship a developer tool built the same way. They'll still need to pick up the fundamentals of the programming — that part isn't optional yet. And getting to that level as a non-programmer takes real effort. But if the interest is there, it's far from impossible. In fact, I'd argue some…
Think of it like image generation AI. You can make acceptable if sloppy art with it, using styles that exist. However, you cannot create a new style. You cannot create pictures of things that are truly novel, to do that you have to pick up the brush yourself.
coding with llms is the exact same thing. It can give you copies of what exists, and sometimes reasonable interpolations/mashups, but i have not seen a single succesful example of extrapolation. Not one. You simply leave the learned manifold and everything gets chaotic like in the example i provided.
If AI can make what you want, then the thing you made is not as novel as you thought. You're repurpising solved problems. Still useful, still interesting, just not as ground breaking as the bot will try and tell you.
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#36Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#37Use AI for building still. But have non AI sessions for learning. Good luck!
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#38Raw dog code on small projects while avoiding using AI, except to explain things when you get stuck.
Learn theory. Learn algorithms. Learn data structures. Learn about secure coding. All of these will help inform you, even if you stick with agentic coding.
Go as deep or as shallow as you want to.
If you want to go deep, read some of the classics (SICP, C book, Pragmatic Programmer, etc), but don't beat yourself up if you don't find them interesting. Most programmers haven't read those books either.
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#39I'm a CS professor at an undergraduate college. I'm currently teaching a class on AI coding for non-programmers and also using Claude Code for all the projects in my upper level courses. I'm also planning to update our first course in the fall to include an intro to agentic programming. Here are some practical suggestions based on what I've seen with my students. To summarize: AI programming de-emphasizes the specifi…
Re: Ask HN: What would you recommend a vibe coder learn about how all this works?
#40Use the AI to teach you. I’m similar not full coder, although tinkered since I started in early 2000’s with html in notepad :) I made a /teach-me slash-command. Everytime I run into something I want to know about I run it. It launches a background subagent (forking context) that check (and updates) my ‘learning-profile.md’. I can pass additional requests, but otherwise it just deduces from context. It then creates an…
I am not a developer. Could you explain the process in a bit more detail? I want to build the same command. I only have the $20 subscription for Claude. Do I need to create a project and create a learning profile.md file and feed what I already know? And then what do I do?
Sorry if that's too many questions.