OP
[No sarcasm]. I never had any doubt, JohnK, about you being a much better programmer than ChatGPT, as you have just demonstrated.
I've changed my mind. I will not make any more tests. This topic bores me. Everyone has their mind already set and I'm not a proponent of any sh*t in particular. My experience has been explained; the scripts have been shared. Period.
I've changed my mind. I will not make any more tests. This topic bores me. Everyone has their mind already set and I'm not a proponent of any sh*t in particular. My experience has been explained; the scripts have been shared. Period.
www.forbes.com
JohnK said:What do you mean? I may not know what 'vibe codding' is then.
I don't think chatcpt can come with the logic behind the `aif()` above.
prompt:
> can you implement this in sh (not bash):
> # aif --
> # Aniphoric if.
> # This function will check an expr is not NULL or "-" before returned,
> # otherwise an iffalse value is returned.
> # EX
> # var=$(aif $(some_expr) 7)
response:
> Yep — totally doable in pure POSIX sh (no bashisms).
[...]
> aif() {
> expr=$1
> iffalse=$2
>
> if [ -n "$expr" ] && [ "$expr" != "-" ]; then
> printf '%s\n' "$expr"
> else
> printf '%s\n' "$iffalse"
> fi
> }
Generally speaking:I think "vibe coding" generally means using AI to create an app, without touching code. You interact with the AI and it writes, builds, tests, and does everything else (these days it can also deploy, debug, and a lot more).
IME the generated code is usually trash unless you are very specific, intentional and thorough with your prompts. That said, it can be functional trash that 100% works correctly. AI isn't (yet) very good at applying wisdom and generating clean, maintainable code. But then again, does it need to? You can tell it to achieve a task (e.g. "add X feature and make sure all tests pass") and it could churn away at it non-stop for days until it works, however horrible it may be inside.
Maybe I am misunderstanding what you mean, but this sort of stuff is trivial for AI:
Code:prompt: > can you implement this in sh (not bash): > # aif -- > # Aniphoric if. > # This function will check an expr is not NULL or "-" before returned, > # otherwise an iffalse value is returned. > # EX > # var=$(aif $(some_expr) 7) response: > Yep — totally doable in pure POSIX sh (no bashisms). [...] > aif() { > expr=$1 > iffalse=$2 > > if [ -n "$expr" ] && [ "$expr" != "-" ]; then > printf '%s\n' "$expr" > else > printf '%s\n' "$iffalse" > fi > }
Professionally I find way more success using it as a companion still, asking for certain things and reviewing/tweaking the output, but for throwaway or proof-of-concept code, letting the AI run free (vibing) can save a bunch of time. However, usefulness of AI depends very much on what exactly you do--the type of apps/code you work on, language popularity, the tools available, environment within which you work and the code runs...you can get much more value out of AI in some scenarios than others.
Personally, I think the models need way more context than they currently have, and time to evolve to use it correctly. Most are around 300k tokens I think. Gemini is better in this area with (up to) 1M. Having more context should allow the models to get even better. Supermaven was an AI tool/plugin specifically for auto-completion that had 1M context and it was great (until it got bought and locked behind Cursor, IIRC). Once the AI can reason about a whole codebase, best practices, languages, APIs, libraries, etc., it should be able to make much better output, I think.
set_value: default.path
get_value: config.path
if ( ! get_value ) {
do_something: set_value
else
do_something: get_value
}
set_value: default.path
do_something: (aif (get_value: config.path), set_value)
I've changed my mind. I will not make any more tests.
I possibly deserve that but at the same time I guess at the end of the day I shouldn't be ashamed of "trying", right? And FWITW, I know the quality of my code/tools/widgets/things isn't "top notch", but the effort(s) are from me just trying to help as best I can.Hopefully LLMs will do significant help doing a manpage
I possibly deserve that but at the same time I guess at the end of the day I shouldn't be ashamed of "trying", right? And FWITW, I know the quality of my code/tools/widgets/things isn't "top notch", but the effort(s) are from me just trying to help as best I can.
I don't think this is really happening. AI is very bad at customer service, for instance, because LLMs are novelists, not technicians. So they invent a lot of what they write still today.I mean there are (entire companies) sacking zillions of employees by the truckload right now -- over what you are posting !
Oh?! I thought your post was saying my tool(s) should be lumped in with (or below that of) AI code (from a discussion in another thread about an AI manpage). I'm sorry. You are right. Misunderstanding.There must be some misunderstanding here.
I'm just hoping that I get a shortcut to a manpage.
That's a very good tool because markdown is very easy and having it automatically converted to mdoc is perfect.Oh?! I thought your post was saying my tool(s) should be lumped in with (or below that of) AI code (from a discussion in another thread about an AI manpage). I'm sorry. You are right. Misunderstanding.
![]()
GitHub - JohnKaul/md2mdoc: A program to convert simple markdown style documents to mdoc for manpages.
A program to convert simple markdown style documents to mdoc for manpages. - JohnKaul/md2mdocgithub.com
My "vibe" coding is looking at notes and seeing if I get a vibe for anything I can improveDo I recommend "vibecoding"? Only for personal projects to be executed at home and not shared with the public. Why? Because I believe that a human should write or revise any code that's put "out there" for anyone to use. And if you are gonna revise it, you might as well write it (or you are gonna get really bored just reading code).