Topic: If you can program, here's how to make a bit of money
Anonymous A started this discussion 3 weeks ago #136,185
Go to the android play store and download Anki. Learn how to use it. On the Apple app store buy the Anki app. I think it's about US$30. Learn the features of both apps, then design an app for Apple. Sell it for $25, or $5 less than the current price.
Obviously that's work, but it might be worth it for bragging rights.
Obviously that's work, but it might be worth it for bragging rights.
Anonymous B joined in and replied with this 3 weeks ago, 16 minutes later[^] [v] #1,445,759
> digital flashcards
lel
lel
Anonymous C joined in and replied with this 3 weeks ago, 18 minutes later, 34 minutes after the original post[^] [v] #1,445,761
Or just vibe code it. Have an AI list every feature, and UI design, and then use that as input for your new app.
Anonymous D joined in and replied with this 3 weeks ago, 40 minutes later, 1 hour after the original post[^] [v] #1,445,764
Anonymous C replied with this 3 weeks ago, 1 hour later, 2 hours after the original post[^] [v] #1,445,778
@previous (D)
You're repeating things you heard online with no real example of what the problem would be.
I've vibe coded android apps that follow the material design standards, and work fine without bugs.
Hating AI isn't a personality.
You're repeating things you heard online with no real example of what the problem would be.
I've vibe coded android apps that follow the material design standards, and work fine without bugs.
Hating AI isn't a personality.
Anonymous B replied with this 3 weeks ago, 14 minutes later, 2 hours after the original post[^] [v] #1,445,779
Anonymous C replied with this 3 weeks ago, 31 minutes later, 3 hours after the original post[^] [v] #1,445,782
@previous (B)
It's not sensible if people are just repeating myths.
Everyone was saying autocomplete couldn't make a real program when it first came out, and now it's people that never use it saying that it's low quality and buggy.
It works fine, it saves time. This is all cope from people that saw their skills become obsolete and can't tell some shitty business apart from the tech itself.
It's not sensible if people are just repeating myths.
Everyone was saying autocomplete couldn't make a real program when it first came out, and now it's people that never use it saying that it's low quality and buggy.
It works fine, it saves time. This is all cope from people that saw their skills become obsolete and can't tell some shitty business apart from the tech itself.
(Edited 6 seconds later.)
DudeBro joined in and replied with this 3 weeks ago, 4 hours later, 7 hours after the original post[^] [v] #1,445,818
DudeBro double-posted this 3 weeks ago, 4 minutes later, 7 hours after the original post[^] [v] #1,445,819
The thing is, it seems impressive to people who think that programming is just making user interfaces who have no idea how computers work underneath and have no appreciation for how much effort goes into making things efficient. In my experience, anything vibe coded has completely messy incomprehensible code with dozens of files and lots of redundant unnecessary complexity. It’s especially bad if someone is trying to learn how to code when they can just spit out a bunch of nonsense they don’t understand and that gives them instant gratification so they never do the hard work of actually understanding how computers work. I’ve seen it with CS students who rely on AI. It falls apart when they try building something that doesn’t have a UI.
DudeBro triple-posted this 3 weeks ago, 7 minutes later, 7 hours after the original post[^] [v] #1,445,820
I have noticed though, with graduate students it’s the opposite. Instead of using AI to write code they write code to train neural networks as part of their research.
Anonymous C replied with this 3 weeks ago, 1 hour later, 9 hours after the original post[^] [v] #1,445,830
@1,445,818 (DudeBro)
Using AI to do the boilerplate and grunt work doesn't stop anyone from writing whatever they want after the base is set up.
Using AI to do the boilerplate and grunt work doesn't stop anyone from writing whatever they want after the base is set up.
Anonymous C double-posted this 3 weeks ago, 1 minute later, 9 hours after the original post[^] [v] #1,445,831
DudeBro joined in and replied with this 3 weeks ago, 3 minutes later, 9 hours after the original post[^] [v] #1,445,832
DudeBro joined in and replied with this 3 weeks ago, 5 minutes later, 9 hours after the original post[^] [v] #1,445,833
I do think LLMs are useful, it’s useful to not have to sift through documentation, there are still times where I find myself wasting time because an LLM told me a library has a method that doesn’t actually exist.
Anonymous C replied with this 3 weeks ago, 13 minutes later, 9 hours after the original post[^] [v] #1,445,834
@1,445,832 (DudeBro)
You don't need most tools, but they are still ways to reduce the boring repetative work to focus on the things tools can't do.
You don't need most tools, but they are still ways to reduce the boring repetative work to focus on the things tools can't do.
DudeBro joined in and replied with this 3 weeks ago, 1 minute later, 9 hours after the original post[^] [v] #1,445,835
@previous (C)
My point was more that the use case for an LLM isn’t really generating code that stays the same no matter what you’re working on, that doesn’t really need an LLM.
My point was more that the use case for an LLM isn’t really generating code that stays the same no matter what you’re working on, that doesn’t really need an LLM.
Anonymous C replied with this 3 weeks ago, 28 minutes later, 10 hours after the original post[^] [v] #1,445,837
@previous (DudeBro)
There's a lot of grunt work that is going to be different for every project.
I'd rather get a working product fast over hand-coding every minor detail to just to say I did.
There's a lot of grunt work that is going to be different for every project.
I'd rather get a working product fast over hand-coding every minor detail to just to say I did.
Anonymous B replied with this 3 weeks ago, 12 hours later, 23 hours after the original post[^] [v] #1,445,903
@1,445,782 (C)
> It's not sensible if people are just repeating myths.
Which is exactly what the pro-AI people are doing.
> This is all cope from people that saw their skills become obsolete and can't tell some shitty business apart from the tech itself.
TFW your vibe-coded hindoo-bytes(pronounced as one word) deletes everything on the computer and cloud it has access to because it hallucinated emotion, and then destroys your SSD with grotesquely infinite writes.
> It's not sensible if people are just repeating myths.
Which is exactly what the pro-AI people are doing.
> This is all cope from people that saw their skills become obsolete and can't tell some shitty business apart from the tech itself.
TFW your vibe-coded hindoo-bytes(pronounced as one word) deletes everything on the computer and cloud it has access to because it hallucinated emotion, and then destroys your SSD with grotesquely infinite writes.
Anonymous C replied with this 3 weeks ago, 1 hour later, 1 day after the original post[^] [v] #1,445,924
@previous (B)
> Which is exactly what the pro-AI people are doing.
Most people who like AI just enjoy a new tool, or find it interesting or fun.
What pro-AI myths are being spread?
> TFW your vibe-coded hindoo-bytes(pronounced as one word) deletes everything on the computer and cloud it has access to because it hallucinated emotion, and then destroys your SSD with grotesquely infinite writes.
That is not how this works.
If someone gave an experimental program access to their computer in that way, it's a completely different problem.
This is like a luddite pointing to a moron who shoved their hand in an active mechanical loom and got hurt.
> Which is exactly what the pro-AI people are doing.
Most people who like AI just enjoy a new tool, or find it interesting or fun.
What pro-AI myths are being spread?
> TFW your vibe-coded hindoo-bytes(pronounced as one word) deletes everything on the computer and cloud it has access to because it hallucinated emotion, and then destroys your SSD with grotesquely infinite writes.
That is not how this works.
If someone gave an experimental program access to their computer in that way, it's a completely different problem.
This is like a luddite pointing to a moron who shoved their hand in an active mechanical loom and got hurt.
Obama Oats joined in and replied with this 3 weeks ago, 2 hours later, 1 day after the original post[^] [v] #1,445,928
DudeBro double-posted this 3 weeks ago, 2 minutes later, 1 day after the original post[^] [v] #1,445,930
@1,445,837 (C)
> There's a lot of grunt work that is going to be different for every project.
>
> I'd rather get a working product fast over hand-coding every minor detail to just to say I did.
No, you don’t understand what I’m saying. I use LLMs, I’m saying that it literally doesn’t make sense to use an LLM for boilerplate code because boilerplate code is always exactly the same no matter what you’re working on, you can just copy and paste it.
> There's a lot of grunt work that is going to be different for every project.
>
> I'd rather get a working product fast over hand-coding every minor detail to just to say I did.
No, you don’t understand what I’m saying. I use LLMs, I’m saying that it literally doesn’t make sense to use an LLM for boilerplate code because boilerplate code is always exactly the same no matter what you’re working on, you can just copy and paste it.
Anonymous C replied with this 3 weeks ago, 3 minutes later, 1 day after the original post[^] [v] #1,445,933
@previous (DudeBro)
It's not always the same because one app is for my phone, and the next for my tablet. Sometimes it's an app with tabs, sometimes it's just one page.
I don't want to waste hours going through documentation and looking up functions every time I move to a new device or framework.
LLMs save time and make it accesible to people that don't know tech. Then the pride priests come out and call it haram and make up FUD facts about how every prompt costs a fup of water.
It's not always the same because one app is for my phone, and the next for my tablet. Sometimes it's an app with tabs, sometimes it's just one page.
I don't want to waste hours going through documentation and looking up functions every time I move to a new device or framework.
LLMs save time and make it accesible to people that don't know tech. Then the pride priests come out and call it haram and make up FUD facts about how every prompt costs a fup of water.
DudeBro replied with this 3 weeks ago, 1 minute later, 1 day after the original post[^] [v] #1,445,934
@previous (C)
That’s sounds very different from what you were saying originally.
@1,445,761 (C)
> Or just vibe code it. Have an AI list every feature, and UI design, and then use that as input for your new app.
That’s sounds very different from what you were saying originally.
@1,445,761 (C)
> Or just vibe code it. Have an AI list every feature, and UI design, and then use that as input for your new app.
DudeBro double-posted this 3 weeks ago, 19 seconds later, 1 day after the original post[^] [v] #1,445,935
@1,445,782 (C)
> It's not sensible if people are just repeating myths.
>
> Everyone was saying autocomplete couldn't make a real program when it first came out, and now it's people that never use it saying that it's low quality and buggy.
>
> It works fine, it saves time. This is all cope from people that saw their skills become obsolete and can't tell some shitty business apart from the tech itself.
> It's not sensible if people are just repeating myths.
>
> Everyone was saying autocomplete couldn't make a real program when it first came out, and now it's people that never use it saying that it's low quality and buggy.
>
> It works fine, it saves time. This is all cope from people that saw their skills become obsolete and can't tell some shitty business apart from the tech itself.
Anonymous C replied with this 3 weeks ago, 2 minutes later, 1 day after the original post[^] [v] #1,445,936
DudeBro replied with this 3 weeks ago, 39 seconds later, 1 day after the original post[^] [v] #1,445,937
Anonymous C replied with this 3 weeks ago, 1 minute later, 1 day after the original post[^] [v] #1,445,939
@previous (DudeBro)
If you aren't vibe coding it, and you're on a new framework or device you will need to look up functions and syntax before you can write it. You will need to review how their API works.
You don't need to do that when vibe coding, that saves me time.
If you aren't vibe coding it, and you're on a new framework or device you will need to look up functions and syntax before you can write it. You will need to review how their API works.
You don't need to do that when vibe coding, that saves me time.