←back to thread

192 points imasl42 | 1 comments | | HN request time: 0s | source
Show context
shakna ◴[] No.45311422[source]
> bikeshedding function names

... Function names compose much of the API.

The API is the structure of the codebase.

This isn't some triviality you can throw aside as unimportant, it is the shape that the code has today, and limits and controls what it will have tomorrow.

It's how you make things intuitive, and it is equally how you ensure people follow a correct flow and don't trap themselves into a security bug.

replies(4): >>45311467 #>>45311534 #>>45311834 #>>45312683 #
glimshe ◴[] No.45311467[source]
I think I'd actually have a use for an AI that could receive my empty public APIs (such as a C++ header file) as an input and produce a first rough implementation. Maybe this exists already, I don't know because I haven't done any serious vibe coding.
replies(4): >>45311517 #>>45311611 #>>45311659 #>>45311943 #
simonw ◴[] No.45311943[source]
The leading models have been very good at this for over a year now. Try copying one your existing C++ header files into GPT-5 or Claude 4 or Gemini 2.5 as an experiment and see how they do.
replies(1): >>45312155 #
1. shakna ◴[] No.45312155[source]
They certainly invent new functions whenever I try.