Do you have a dumb question that you're kind of embarrassed to ask in the main thread? Is there something you're just not sure about?
This is your opportunity to ask questions. No question too simple or too silly.
Culture war topics are accepted, and proposals for a better intro post are appreciated.
Jump in the discussion.
No email address required.
Notes -
Oh, I always manage to hit the 5-hour token limit within the very first hour of every session. This has honestly made development so needlessly slow and frustrating. Because of this, two days ago I switched over to Codex/ChatGPT.
And I'm already out of tokens. I managed to burn through my entire weekly usage limit in just two days. But I'm not annoyed about it. I actually, finally (!!!!) got everything that I wanted done done. I didn't feel like I was being artificially limited in my usage. It didn't feel arbitrary or money-grubby. It was well forth it.
It's full-on no-code development. Neither I nor anyone else in their right mind would ever willingly write the code I am making these poor clankers write for me. You'd have to be insane. It would take so long, and it would be such an awful experience to even attempt to write it all by hand. You get an AI to do it for you.
But even with AI, and now I'm just ranting, it really does seem like most people (not me) just can't be bothered with it. It's like it's a pain in the ass for them to simply ask the AI to make their shit properly. And so you get "vibecoding" and "vibecoders", who then shit up the internet with their shitty, unoptimized apps.
After working it for a while, I get the impression there's a right way of asking it and a wrong way. And if you ask a wrong way, you get something, but that would be an quite shitty code which sometimes does things that make no sense at all. But if you let it split the task into bite-sized parts and go through them one by one while consistently controlling quality and not letting it do stupid things, you get very decent results. Making it plan things first and only then execute (after you verify and correct the plan) is often the key to getting good results. "Just tell it what to do and it'll do it" is not exactly it - unless you don't care about the quality of the result. Sometimes it works - e.g. for throw-away scripts that it doesn't matter how good/bad the code is, just that it runs, but for code that is going to be maintained it needs more effort.
More options
Context Copy link
More options
Context Copy link