I think some of the problem is the term vibe coding. If I want a small app to help something specific I used to look at it and go is it worth writing it for the return most of the time I was just too busy.
Now I sit down and write up a small document outlining what I want why I want it and the outcome typically I’d use AI then to review it and give any suggestions that I may not have thought of and use that for the seed for the application.
That is the document I use with an agent to actually do the code generation. I push that to a local GIT instance and the document lives with the code and then gets iterated overtime and then I typically use the issues list to add improvements and fixes to it again iterating through the issue before I think about letting an agent do it
To me vibecoding is just putting a sentence in and hoping for the best I like a little bit more structure than that.
Again, most of this is for personal use so I don’t share it widely a few friends have access to some of the stuff I’ve written because it helps them. I only ever released one AI first project on GitHub and I probably won’t go any further than that.
@sytone@selfhosted Hello, let me contribute with my 2 cents of experience in automated generation of code, I won’t say “vibe coding” as it means nothing and marketing always uses meaningless words to make concepts more appealing.
I started it the last week of July and for my YunoHost based selfhost echosystem I’m building a multilingual framework for WordPress.
There are so many plugins, paid or free, for this CMS but I’m totally blind and most of them don’t cover my accessibility needs. So, I’m experimenting AI use to create what I personally need. This on-demand code generation, lets me be self-determined on what I want, because I guide the machine with words. Text only. And it responds.
Am I a developer? No. Unfortunately I don’t know how exact the code is, if something written in 10 lines could be managed just with two.
But I have something working for my own project, still in development in fact it’s called MARS (Multilingual Accessible Rudimental System), used “rudimental” without hiding anything, to signal that it’s not hardcoded by a very experienced dev. And chose the acronym “Mars” because this planet is the longest and most difficult human ambition, full of obstacle, exactly how my web experimentation journey is.
I can’t deny I’m trying to study ways to share it with other devs, when it’s ready, I have no ideas of dates and I won’t ask for any money back, if it will ever be shared. But my most relevant thought is not to share it as I’ve got no first-hand verification on vulnerabilities.
Last but not least, I’d invite to read this article on blindness, AI, and also coding.
I think some of the problem is the term vibe coding. If I want a small app to help something specific I used to look at it and go is it worth writing it for the return most of the time I was just too busy.
Now I sit down and write up a small document outlining what I want why I want it and the outcome typically I’d use AI then to review it and give any suggestions that I may not have thought of and use that for the seed for the application.
That is the document I use with an agent to actually do the code generation. I push that to a local GIT instance and the document lives with the code and then gets iterated overtime and then I typically use the issues list to add improvements and fixes to it again iterating through the issue before I think about letting an agent do it
To me vibecoding is just putting a sentence in and hoping for the best I like a little bit more structure than that.
Again, most of this is for personal use so I don’t share it widely a few friends have access to some of the stuff I’ve written because it helps them. I only ever released one AI first project on GitHub and I probably won’t go any further than that.
Spot on. Most engineers at companies are using LLMs nowadays but when we use it in our daily lives it becomes “vibe coded”.
I’ve started using the term agentically built or agentically driven instead.
@sytone @selfhosted Hello, let me contribute with my 2 cents of experience in automated generation of code, I won’t say “vibe coding” as it means nothing and marketing always uses meaningless words to make concepts more appealing.
I started it the last week of July and for my YunoHost based selfhost echosystem I’m building a multilingual framework for WordPress.
There are so many plugins, paid or free, for this CMS but I’m totally blind and most of them don’t cover my accessibility needs. So, I’m experimenting AI use to create what I personally need. This on-demand code generation, lets me be self-determined on what I want, because I guide the machine with words. Text only. And it responds.
Am I a developer? No. Unfortunately I don’t know how exact the code is, if something written in 10 lines could be managed just with two.
But I have something working for my own project, still in development in fact it’s called MARS (Multilingual Accessible Rudimental System), used “rudimental” without hiding anything, to signal that it’s not hardcoded by a very experienced dev. And chose the acronym “Mars” because this planet is the longest and most difficult human ambition, full of obstacle, exactly how my web experimentation journey is.
I can’t deny I’m trying to study ways to share it with other devs, when it’s ready, I have no ideas of dates and I won’t ask for any money back, if it will ever be shared. But my most relevant thought is not to share it as I’ve got no first-hand verification on vulnerabilities.
Last but not least, I’d invite to read this article on blindness, AI, and also coding.
https://mosen.org/ai/