121–130 of 158 posts
"...coding isn’t about the finished product. its a lot like writing. its about the process. its about how you approach a problem. its critical thinking." For a more comprehensive treatment of this insight, see: Programming as Theory Building by Peter Naur https://pages.cs.wisc.edu/~remzi/Naur.pdf
To me coding is a tool to get things done, not something I intrinsically like or value
Earlier quoted context omitted.
> code I don't understand completely, yet I'm still responsible for it. Is this different than any given library?
You can and should audit your dependencies.
How many teams importing React have even one member who's ever read even a dozen key paths & files in the React codebase? Think it's more than 10%? I'd bet it's closer to 1% than 10%, of teams on which even one member has done that, ever. Do they check the diff for every update? Shit, IME you're lucky if a single person reads the entire changelog before updating, and certainly nobody's reading the diff. Repeat for everything else. Functionally nobody does this, outside niches where small numbers of low-line-count deps are the norm.
Rails, all those imports from Square you used to have to use to cut the "WT actual F is this?" rate in Android dev to something non-crazy making, et c. Basically nobody even skims this stuff, and I don't think the number of businesses willing to pay for their developers to do that is large.
Earlier quoted context omitted.
Odd. How can one get the vibes without looking at the code? Like gleaming diamond vibes versus confused spaghetti vibes.
I think the vibes refer to the running software, not to the code itself. I hate the whole concept deeply.
Cursor has a "yolo mode" where you don't have to click accept for tooling even for system commands and people whitelist commands like sudo, su, and rf :))) I wish I was kidding.
Don't: vibe code. Do: agentic code.
These seem to be terrible reasons to give up on using AI, although they might be valid reason to stop using AI a certain way . You can use AI in different ways, it is extremely good as documentations. Often to understand how a library works you want a specific example, getting that example and having an AI answer questions about particulars has been very valuable to me and often saved me meaningless wandering through…
"Vibe coding" is a very certain way to use LLMs (one where you treat code the same way a junior Java SWE reads generated JVM bytecode), which is what the OP is about. They agree with your point. There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. ... I "Accept All" always, I don't read the diffs anymore. When I get error…
Earlier quoted context omitted.
Grepping is an oversimplification: I ask for specific use cases, for listing all code paths that perform some action, etc. It works really well.
How though? Do you setup RAG for this? Large context window? What do you use?
Earlier quoted context omitted.
Grepping is an oversimplification: I ask for specific use cases, for listing all code paths that perform some action, etc. It works really well.
How though? Do you setup RAG for this? Large context window? What do you use?
Yeah, this makes me feel so sad because as somebody who's been a programmer for about 15 years now, there is definitely an advantage that we have because we actually know how to code. I feel really sad for those who are starting out today. In many cases, especially for frontend programming, vibe coding correctly has a lot of value but it does makes you not learn anything. Which means you remain at what I call the "vi…
My understanding is that typed languages like Haskell and Rust are even easier with vibe coding than untyped.
Earlier quoted context omitted.
Same promise all the no-code or low-code app builders claim. Anyone who has done a serious project with LLM help knows it is no where near able to do half the things needed to run a project.
Skill issue, you aren't vibe coding properly. I am not joking.