Live data from Hacker News

Ape Coding [fiction]

rsaksida.com

31–40 of 154 posts

Re: Ape Coding [fiction]

#33
I call it Tradcoding. Not using AI for anything. (You just copy-paste from StackOverflow, as our forefathers once did ;)

I also have two levels "beneath" vibe coding:

- Power Coding: Like power armor, you describe chunks of code in English and it's built. Here you outsource syntax and stdlib, but remain in control of architecture and data flow.

- Backseat Coding: Like vibe coding but you keep peeking at the code and complaining ;)

- Vibe Coding: Total yolo mode. What's a code?

Re: Ape Coding [fiction]

#34
I always thought that ape coding is what we call vibe-coding nowadays. Maybe the write of the article (maybe an ai generated blog?) misunderstood the terms.

Re: Ape Coding [fiction]

#35
It's pretty strange to me that we imagine a world where AI can handle every problem but we still talk about code. It's like how the Jetson's had bulky TVs.

You don't talk about all the assembly high level languages make, or at least it's no longer how people view things. We don't say "look at this assembly I compiled." Instead the entire concept fades to the back.

Re: Ape Coding [fiction]

#36
I would probably just call it hand coding, as we say we use hand tools in wood working. Many do this for fun, but knowing the hand tools also makes you a better woodworker.

It's an interesting question: Will coding turn out to be more like landscaping, where (referring to the practice specifically of cutting grass) no one uses hand tools (to a first approximation)? Or it will it be more like woodworking, where everyone at least knows where a Stanley hand plane is in their work shop?

Re: Ape Coding [fiction]

#37
post #24

It's not ape coding. It's skill coding. People who don't have the skill to do math and logic ask others to do it for them. The reason we have programming languages is the same reason we have musical notation or math notation. It is a far more concise and precise way of communicating than using natural languages. We could write music using natural language, but no one does because a single page of music would require…

This is why I never use a calculator. Since my school days I have the skill to do long division. Why hit the sin button when I have the skill to write out a Taylor series expansion? For many other purposes I have the skill to use Newton Raphson methods to calculate values that mostly work.

Those who use a calculator simply don't have these skills.

Re: Ape Coding [fiction]

#39
post #33

I call it Tradcoding. Not using AI for anything. (You just copy-paste from StackOverflow, as our forefathers once did ;) I also have two levels "beneath" vibe coding: - Power Coding: Like power armor, you describe chunks of code in English and it's built. Here you outsource syntax and stdlib, but remain in control of architecture and data flow. - Backseat Coding: Like vibe coding but you keep peeking at the code and…

I feel like this distinction isn't made often or clearly enough. AI as a superpowered autocomplete is far more useful to me than trying to one-shot entire programs or modules.

Re: Ape Coding [fiction]

#40
post #24

It's not ape coding. It's skill coding. People who don't have the skill to do math and logic ask others to do it for them. The reason we have programming languages is the same reason we have musical notation or math notation. It is a far more concise and precise way of communicating than using natural languages. We could write music using natural language, but no one does because a single page of music would require…

This is why I never use a calculator. Since my school days I have the skill to do long division. Why hit the sin button when I have the skill to write out a Taylor series expansion? For many other purposes I have the skill to use Newton Raphson methods to calculate values that mostly work. Those who use a calculator simply don't have these skills.

There is a notable difference between say, calculating long division through a calculator compared to prompting an AI to calculate the derivative of a simple continuous function. one requires _understanding_ of the function, while the other just skips the understanding and returns the required derivative. One is just a means to skip labor intensive and repetitive actions, while the other is meant to skip the entire point of _why_ you are even calculating in the first place. What is the point of dividing two numbers if you don't even understand the reason behind it ?
Post reply on HN