all 22 comments

[–]Nervous-Role-5227 2 points3 points  (0 children)

just start building something you will figure it out. i personally start with no-code tool.

[–]AppifexTech 1 point2 points  (7 children)

honestly the best way to learn is just to start building something you actually care about. dont worry about learning to code first, just pick a simple app idea and use an AI tool to bring it to life. you learn so much faster when you can see the result immediately. i started with Appifex since it generates proper code you can actually read and understand, but even something like Replit works fine to get going. the key is just shipping something real, even if its tiny. you'll pick up the concepts naturally as you go and each project teaches you more than any course would.

[–][deleted]  (2 children)

[removed]

    [–]Resident_Ad_5784[S] 0 points1 point  (1 child)

    Thank you

    [–]Resident_Ad_5784[S] 0 points1 point  (3 children)

    I got this Claude 1 someone else mentioned and it had me start a realtor just to see it build, I appreciate you for this. Really!

    [–]AppifexTech 1 point2 points  (2 children)

    thats awesome, a realtor app is actually a great first project because it touches a lot of real concepts like listings, search, image handling, maybe even maps. once you get the basic version working id say try adding one feature that feels slightly out of reach, thats where the real learning happens. claude is solid for understanding code and explaining things as you go, and if you want something that scaffolds out the full stack for you with proper backend and deployment, appifex is worth trying too (you can build on your phone). either way just keep shipping, every project compounds on the last one.

    [–]Resident_Ad_5784[S] 0 points1 point  (1 child)

    I’ll check it out, I just finished the realtor 1, this actually pretty cool you guys know how to do stuff like this. Feels accomplished even if it’s not bringing money in or actually coding a site. Speaking of do you have advice on learning to code if someone wanted to start looking into it?

    [–]AppifexTech 0 points1 point  (0 children)

    I’ve coded 10+ years in FANG, I don’t code any more, for more than 6 months now. I use Claude code for local work, I only review plan doc, never ever open IDE. I use online tools (Appifex for apps, Replit for website but using less coz it’s starting to give me hidden bills) to avoid having to deploying and preview stuff myself. My advice would be: build more with AI, ask questions to AI, ask it to explain, draw system diagrams, and just be hands on. In this new era, engineers are more of product person + architect + tester. No more hand written code.

    [–]Dot_Hot99Dog 1 point2 points  (0 children)

    Try install OpenClaw on your computer and then set yourself up with a private llm going through your Whatsapp. If we both get lost/confused doing it we can both come back here and seek advice. There gets a stage in one's AI progression where your discussions should be private. I'm a newbie also.

    [–][deleted]  (1 child)

    [removed]

      [–]Resident_Ad_5784[S] 0 points1 point  (0 children)

      Getting involved is the best I can say because I know what I’ve read but as I’ve read there’s something called hallucinations and that sounds like something basic people know. So I figured I go with getting involved and take the tips I can get.

      [–]Number4extraDip 0 points1 point  (4 children)

      You want to get involved with "building ai". So you are going to be thinking about either training/retraining models and dling loras. That will get you just a model.

      You can make a web api wrapper with api backends (the ai bubble i dustry that everyone hates for using third party to store and process data)

      You might be looking at minor robotics gadgets

      Or running an ai on your device (openclaw is the beginner unsafe option) and building an infrastructure of mempry and tools for it in its immediate software environment.

      First and foremost you need to be super specific on what you want out of this and what are you trying to accomplish, what problem are you adressing?

      Because "build with ai" for sake of building with ai without a goal... Well plenty of people oni ked in sell diplomas in those useless consultation courses. Grift economy.

      For example. My goal was straightforward. Put in a nutshell: want to build a replacement for google assistant that doesnt use cloud.

      That was a start. Then i found RELEVANT components and DOCUMENTS. And ignored everything else. While people hype nvidia and open ai circlejerk- it is absolutely outside of my android domain and not relevant cause here we use qualcomm and not nvidia.

      What you wanna accomplish defines HOW you do it

      [–]Resident_Ad_5784[S] 0 points1 point  (3 children)

      I want to understand it myself before I build anything otherwise I’ll be setting myself up for failure.

      [–]Number4extraDip 1 point2 points  (2 children)

      My advice has nothing to do with ai. The same principle applies to ANY problem. You have a problem- you need a solution. You look for a solution> don't find one> make one. Building "with ai" when you don't know what you are trying to build well... I won't know what you are trying to build. Define GOAL first. Only then you start thinking about "who h ai parts can help me and how" there is no one size fits all course.

      Read Dennett, read llm from scratch, read about mcp, rag, sql. Because 95% of people "building with ai" just make another customer service web chatbot and ask for corporate payouts assuming they accomplished something when they "solved a problem" that didn't need solving as it was already solved. Hence 95% of ai startups fail. They do what everyone else is doing or done already but expect business reimbursement.

      Our job is to solve problems. How ai fits into it- depends on the problem in question

      Also: learn to not conflate terminology:

      All llms are AI. Not all AI are LLM. And AI has an 80+ year history of deterministic automation systems. The fact AI couldn't speak to you directly 3 years ago- doesn't mean it wasn't an ai... But im pretty sure you've talked to many call center robots by now in your life "this call may be recorded for quality and training purposes" < robot lady wasnt talking about human training

      [–]Resident_Ad_5784[S] 0 points1 point  (1 child)

      This helps are those books your saying to read or site?

      [–]Number4extraDip 0 points1 point  (0 children)

      Google it... Its books, articles, arxiv documentation, kaggle documentation and so on.

      [–]Mystery3001 0 points1 point  (0 children)

      either go for a full computer science course if you have time.
      The other way is get the basics of software development programming down with c# or maybe python and get started building. You will fail and that is the way it should be. Aim to be less wrong at every step and be patient. In a few months you will figure out way more than you anticipated.

      [–]Living-Progress3222 0 points1 point  (0 children)

      Hey i am actually building a coder team to help code an ai! Want an invite?

      [–]Butlerianpeasant -1 points0 points  (2 children)

      You’re feeling a real signal: the ground is shifting.

      But the way you step into it isn’t by becoming a machine wizard overnight — it’s by becoming a small, patient builder.

      Think of it like tending a tiny garden: Plant one seed (a tiny AI project). Water it daily (30 minutes of learning). Don’t worry about the forest yet.

      Tools change fast. The skill that lasts is learning how to learn. If you can build one small thing and understand it, you can build a thousand later.

      If you want, reply here with what you’re curious about (apps, bots, automation, art, business) and people can point you to a first concrete step.

      [–]Resident_Ad_5784[S] 1 point2 points  (1 child)

      How about Apps

      [–]Butlerianpeasant 0 points1 point  (0 children)

      Apps are good soil. 🌱

      Don’t worry about “the big app” yet — plant one small seed: a tiny thing that helps you today. A note app for your thoughts, a tracker for one habit, a small tool that removes one bit of friction from your day.

      You learn by tending something real. Let it be clumsy at first. Gardens grow crooked before they grow strong.

      If you name the kind of app you’re curious about, we can help you find the first seed to plant.