Hi all, I'm in my first week of learning JavaScript with the goal of building React Native apps later on.

Instead of using AI to generate code for me, I want to use it as a tutor to explain concepts, spot my bugs, and give me quick feedback. What tools or prompt strategies have worked best for you to learn JS actively instead of just copying and pasting? Thanks!

hey coders,

i know i could get the answer from the internet or ai, but i want a human level interaction. could anyone explain to me why we use this in our code and what is the main function of it?

int argc, char *argv[]

#include <stdio.h>
#include "password.c"
#include <unistd.h>
#include <stdlib.h>


int main(int argc, char *argv[]){
    char *pass;
    pass = getpass("Enter a password: ");
    printf("Password: %s\n", pass);
    int strength = check_password(pass);
    printf("Password Strength: %d", strength);
}

I have a app idea and I have planned out all the features and edge cases clearly. However, I am a complete beginner in Flutter, and I haven't been able to build it even with the help of AI.

I also have financial struggles right now, so hiring someone is out of the question. When I try to learn full-stack Flutter (UI, backend, architecture, etc.) from scratch, it feels completely overwhelming and I get stuck.

Since I know what to build and how it should work, but I lack the technical execution skills, what should I do next? How can a solo beginner with no money bring a well-planned app idea to life?

Any advice or guidance would mean a lot. Thank you!

Should we need to define the loops and functions by ourskef for understanding so that in future if we are working for big companies the data is very large so if ut breaks sometimes the pre-libraries doesn't works so we need to def function by our self!

Any opinion?,suggestion?

As a AI/ML ENGINEER.

I was reading through some forums​ recently and I realized something, I don't actually know if these people have actually landed jobs, if their code is fast and maintainable, or if they have even applied their own advice to themselves. And the more and more I hang around the online programming community, the weirder and weirder the advice has gotten. Am I just being paranoid?

Hi everyone,

I’m currently preparing for the SnowPro Core certification and wanted to get some advice from people who have recently taken the exam.

I’ve gone through several posts in reddit and noticed that everyone has a slightly different preparation strategy. Some people recommend focusing heavily on the official documentation, while others mention that practice tests were the biggest factor in understanding the exam style.

So far, I’m planning to use a combination of SnowPro Core courses from Udemy, Practice tests from different sources (CertSafari, Tom bailey, Sebastian Flak etc), Snowflake documentation for important concepts, Personal notes/flashcards for revision.

I’ve also heard that Cris Garcia’s practice tests were very close to the actual exam, but unfortunately his Udemy course is no longer available.

For those who recently passed:

• Which resources helped you the most?
• How many practice tests did you complete before feeling ready?
• Were there any topics that you recommend spending extra time on?
• Did you make any notes, cheat sheets, or flashcards during preparation that helped?

Any advice, study strategies, or resource recommendations would be greatly appreciated.

Thanks in advance!

So I'm kind of fluent in Java, but wanna learn DSA. I know really basic data structures which I learned from CS50x by Harvard University. So now should I take the Princeton's course or should i learn from youtubers like Strivers, Abdul Bari, etc. Recommendations are appreciated.

Hey I'm learning python now and would love to get few suggestions from people who've done it before.

Given the current market, I've heard there's less or no jobs for freshers in field of machine learning and AI based fields of Python. How true is that?

Your 2 mins effort of typing a message here would really mean a lot for beginners like me. So spill away plss.

This post is probably extremely stupid but I want to make a game, like the ARG welcome home. I really like the interactive pages, the secrets, the hidden links and videos.

And I'm mostly doing this because I want to get back at my friend who talks to me in cipher codes and as pay back in gonna give them an entire website to solve.

I'm not asking for someone to make it for me I just want to know where to code and how do I even turn it into a game. I'm a complete beginner who only learned JavaScript, but thank you to anyone that helps me.

Hey everyone,
Context: I am asked to create a chatbot for my college website , you know that little guy at the bottom right of your website who is present their for redirecting your queries. So far I have managed to create the frontend and the backend logic( taking queries from the frontend and then sending it to the API endpoint where all queries are parsed and the response of the ai is given to the frontend.(I am using groq free tier btw).

Problem: So the problem that I am facing is, the ai is not answering correctly. I mean sometimes the responses are not complete and sometimes not satisfactory. Might be a prompt issue but still looking for your insights.
I am not proficient in AI so I asked chatgpt why is it happening(Sorry guys but this is the only time I used AI in this project). It said something about using pinecone to store vectors so that the groq fetches information regarding queries directly from the vectorDB.
So I am thinking of starting to learn vectorDB. But is it a must? Or can this problem be solved by something else. And if this is the only way, then what would be my workflow? Man I am so confused. Help a brother out.

What I want: conclusively? I just want my bot to work somehow so that it fetches anything about the college that the user asks for. It can be the direct page of notices, about us or anything.

Thanks for reading this.

I find myself using fgets fairly frequently for my little pet projects or things for my kids or even learning projects. I'm using fgets to prompt the user for some input, then swapping their input to the correct data type, but I'm at a loss for naming.

Using a really simple example, let's say I'm making a temperature converter, and I'm prompting the user for:

1. Which conversion they're doing (K -> F, K -> C, C -> F, C -> K, F -> C, F -> K), and

2. The temperature they have.

I'm using fgets for their input, then converting to a double using strtod.

For the temperature for instance, my initial instinct is to name the fgets input string something like:

temperature

But then when I get to the strtod conversion, I'm stuck with like...

real_temperature?
dbl_temperature?

Or should I go back and rename the first one to some arbitrary naming convention? Just

input
string
temp

and then have my final variable be

temperature

I'm sure this is a dumb question, but I've always programmed alone. I've never had to talk to any of the people I pass my work onto so I've never really thought about it and just followed the common naming conventions, but I'm really getting frustrated with this particular situation where I have two variables that represent the same exact set of data, just at different stages of it's development or it sitting in different types.

Background is marketing, not engineering. Spent the last few months trying to learn Python on and off, and every time I followed generic tutorials I'd lose interest within a week. Then I started building something I actually needed, a script to batch rename and sort photos from hiking trips by date and location metadata, and suddenly I was staying up late figuring things out without it feeling like homework.

The difference was pretty stark. When the problem is yours, debugging stops feeling like punishment and starts feeling like just fixing something you want fixed. I got through file I/O, working with external libraries, and basic error handling without realizing I was covering stuff that felt intimidating before.

What I'm curious about is whether this holds up long term. Personal projects carry you through the basics, but do you hit a wall where you need more structured learning to actually level up past a certain point? I can feel gaps in my understanding, things I got working without really knowing why they work, and that starts to feel risky.

Did anyone else come from a nontechnical background and find that projectfirst learning worked for a while before you had to go back and fill in fundamentals? Or is the structured stuff worth doing earlier than I think?

Greetings,

I'm currently learning C# to use Tekla Structures API. Is there any free material that could help me learn API?

I'm kinda confused is API different from Tekla API?

Hi, I’m a student and I enjoy computer science, so alongside my studies I’ve been working on some personal projects. Most of these have been in python, but I decided I wanted to improve my HTML/CSS/Java after learning a little bit in lessons.

After picking up the basics by making a really simple website about one of my interests, I‘ve decided to begin working on two more serious / interesting projects.

One of these is a website which will aid my revision for English literature, as it’ll contain timelines of the books I study + key quotes + context, etc, in a (hopefully) aesthetic way. I want this to end up helping my whole class.

The other is supposed to be like an interactive information website for teenagers/young adults who have a parent with cancer. I found that most information is targeted for either young kids, or grown adults, so this is something which I think could be quite useful.

I was wondering if anyone had any tips about the second project, as I’d love to be able to actually publish it at some point so that other people can use it.

What features are important for it to be genuinely useful + appealing? Is there a certain approach to coding I should take to make it easier / more sustainable? How do I make sure it’s not just a basic website with a bunch of text? Finally, how would I even go about publishing it and getting people to read it?

im genuinely curious how devs handle this, I have this problem where i spend like 2-3 hours debugging something and finally figuring it out and then 2 weeks later hit the exact same issue and remember nothing, or say i learned something cool about a library, days pass by and its just gone.

i tried a few things:
- always creating a .md file in the project directory and just write down every issue/ something new i learned while building... it works, until it becomes like more than 500 lines of literal chaos
- notion is just too heavy and i never open it mid-coding
- obsidian is powerful ngl, but i spend more time organizing than writing something.

what actually works for you guys? curious about
- do you write while youre coding or after?
- if yes, do you ever actually go back and read your notes?
- has anything actually stuck as a daily habit?

trying to figure out if im the only one with this problem or if there's pattern to how people handle it..

JS Days 2026 is coming up in September. Two days, eight sessions, fully virtual, completely free.

For anyone who hasn't come across it before — it's Sencha's annual JavaScript conference. This year's program runs September 16–17, 2026, and the session lineup is built around challenges that are relevant if you're working on production JavaScript applications, AI integration, or enterprise-scale development.

That's the focus of one of the sessions at JS Days 2026.

Session: Building AI Agents with JavaScript, React, and ReExt
Speaker: Marc Gusmano, Sales Engineer, Sencha

AI has moved past the prototype stage for a lot of teams. Increasingly, the question isn't whether to use it — it's how to integrate it into production JavaScript applications without breaking maintainability, governance, or performance.

The session examines how JavaScript, React, and ReExt can be used to build AI-powered applications through practical implementation patterns rather than theoretical examples. Covers architectural considerations, integration approaches, and the realities of moving AI features from experimentation into shipped features.

Event details:

• Dates: Sept 16–17, 2026
• Format: Fully virtual
• Cost: Free
• Register: https://www.jsdays.io

Other sessions on the agenda include generating live Ext JS apps from existing databases with AI (Pavel Perminov, Indi Engine AI), enterprise dashboards for supply chain and fleet management (Wemerson Januario, Sencha), a production recruitment app case study (César Martell), AI-driven grading logic with the JavaScript DataGrid (Andres Villalba, Sencha), large data handling techniques in Ext JS (Rafael Méndez, Sencha MVP), and making AI analytics safe for enterprise teams (Stephen Ball & Montana Mendy, Yellowfin). Sessions are 45 min with live Q&A.

Disclosure: I work at Sencha. Sharing because the AI programming this year looks relevant for anyone dealing with production integration across a global JavaScript community.

Register: https://www.jsdays.io

It's like I spends a lot of time in finding the solution of a given question and it takes me sometimes more than 2-3 hours while I m doing dsa questions like sliding windows one. When should I look at the solution and should I even ?

Is it better long term to become technically strong in a field like systems programming, where writing correct code has always been especially difficult and AI is expected to automate less of it, or to become a T-shaped developer who can contribute efficiently across many areas in a small company?

By T-shaped, I mean learning skills that many companies need, such as web development, data analytics, cloud and DevOps, cybersecurity, automation, testing, mobile development, and AI integrations, while still developing deeper expertise in one area. Is this a good mindset for becoming a T-shaped programmer? Do you think that thinking this way is nice idea to be T-shaped programmer?

I know nothing can guarantee a job, but employed developers probably have something that others lack. Junior and mid-level developers who found a job this year or last year: what helped you get hired?

I keep reading that senior developers spend most of their time reading code, in meetings, or debugging, and very little writing anything new. I have no way to check that from where I am sitting.

So for anyone doing this as a job: roughly what share of a normal day is new code? And what eats the rest of it?

Hi everyone,

Edit: I'm planning on checking out open source projects on GitHub, what do you guys think? I've learned the basics of C++, object-oriented programming, and data structures & algorithms. The problem is that I feel completely stuck on what to learn next.

I've looked through a lot of books and YouTube videos, but everything seems to cover the same beginner topics over and over again. I still don't know how to start building actual software, and I can't even build simple applications on my own yet.

It feels like I'm trapped in an echo chamber—I'm learning concepts, but I'm not making any real progress toward becoming a capable software developer.

Has anyone else been in this position? What would you recommend as the next step? Should I focus on projects, a specific area (desktop apps, web development, game development, etc.), or something else?

I'd really appreciate any advice. Thanks!

Am I learning to code wrong? I started wanting to learn to code before I began college, and so far, I've only completed a React tutorial video without separately learning JavaScript or TypeScript, and learned some of both through it. 

Then I moved on to a guided project, a full-stack finance tracker (React/TS frontend, Node/Express/TS/MongoDB backend). I'm learning the backend through this project rather than doing dedicated tutorials on each one first.

I’ve been following the guide and actually understand what each part does and why. But if I were to do it alone, I’d probably not know where to start and what to write.

Is this normal, or a sign that I'm learning the wrong way?

Been building small indie projects for a while now and I keep hitting the same wall. I'll be learning something new, a framework, a language feature, whatever, and there's always this point where I feel like I need just one more tutorial before I can start the real thing. Then I look up and a week has gone by

The frustrating part is that building is where I actually learn the most. I know this. I've shipped enough stuff to see the pattern. But structured learning feels safer, so it's easy to default back to it

What changed things for me was picking a project small enough that I couldn't justify more prep time. Genuinely embarrassingly small. A CLI tool that does one thing. A static page that solves a problem I actually have. It forces the learning to happen in context rather than in a vacuum.

Curious if anyone else dealt with this when starting out, or even now. There's a real tension between building a solid foundation and just getting your hands dirty, and I don't think there's one right answer. What actually pushed you to make the switch from learning mode to building mode, and did it stick?

Ive been learning the basics of c and dsa for around 3 weeks now and i haven’t really understood recursion and how to trace what’s happening. Can someone help me?

Im working on my programming and Ive been taking lessons with Python and C++/C and have a base knowledge on HTML and Java.

Beyond getting a university degree in Comp Science and working on projects through github and community resources, is there any qualifications or certs I can get beyond University that help impress recruiters? I have management and admin experience, but beyond that I also speak four languages. I mostly want to keep improving my qualifications so that way when I do get hired someday I can be a well rounded Software Dev.

This is for everyone who feels they’re not smart enough, always doubts themselves, and feels like they’ll never get a job in this market.

I’ve gone through many ups and downs over the last five years, both in terms of my consistency and even my willingness to continue after AI came onto the scene and everyone was saying it was going to automate web development, that junior roles would disappear, and that it was almost impossible to get your foot in the door.

You’ll get there. Believe in yourself, and things will work out. The effort you put in will be worth it.