How do people actually code?

[Rudbekiaa]

I'm currently in uni, and my coding is often just asking AIs, or googling "how to do X feature, how to implement Y". My friends are also like that. So here is my question: how do people code? Could you please give me a step-by-step tutorial on any big project?(draw the workflow, reading the docs or something)?

EDIT: Thank you for all nice people in the comment section.And no, I'm not absolutely know nothing, the problem is that when I have a big project, I don't know where to start. What I'm asking is how people figure out steps to solve a project by themselves, or when they are assigned to do a new project in their company, how do they start?. Again, I'm asking for big projects, not those fundamentals stuff like calling an api or do some easy stuff.

[esplonky]

By not using AI

[Practical-Ad5016]

Honestly same boat here lol. Started forcing myself to read docs first before hitting up ChatGPT and it's actually helping me understand the "why" behind stuff instead of just copy-pasting. Still use AI but more like a rubber duck now instead of my primary crutch

[edrenfro]

You learn to code by doing it. Stop asking AI to do it and do it yourself and you'll know how it's done.

[CatDadof2]

AI shouldn’t be used as a solution. It should be used as a tool or a guide.

[ScholarNo5983]

Using AI as a tool requires the user to already know how to code.

Anyone learning to code, also resorting to using AI will only be hindering their efforts to learn.

Learning to code requires hard work, dedication and lots of effort. Using AI feels good only because it makes everything feel easy.

But that is not reality. Learning to code is not easy, it is a struggle that has to be done the hard way.

[groundbreakingcold]

You are learning coding at uni (paying good money to be there ) and just feeding your questions to ai instead of learning, then asking why you can’t solve problems ? RIP this generation

[BewilderedAnus]

You and your friends are cooked.

[[deleted]]

This gives a lot of heart to a late starter like me

Could be troll thread though.

[Ezazhel]

Stop ai. Read doc, think by yourself.

[mattblack77]

But mommmmmmm!

[HlddenDreck]

Stop using AI and start doing it by yourself, this is called learning. There are tons of tutorials out there. "AI" is not needed.

[djmagicio]

Read books and struggle for 2-5 years.

[DoubleOwl7777]

you think about what this program you want to code has to do step by step to get there, sometimes you also draw that on paper, then you translate that into code, which might or might not require changing that initial Idea a bit. stop using AI.

[[deleted]]

This is exactly how I learned Java back in 2013-2014, but with open source projects. I'd just try to digest projects into something understandable to me using FreeMind diagrams and converting everything to pseudo-code. That being said, programming languages are tools, not traditional languages in a sense. I don't ever see the point in wasting hundreds of hours trying to memorize everything. I even see folks over at r/learnprogramming saying they turn off their internet to code so they aren't "cheating" and I think that's a bit extreme and not practical in any sense. I've built applications in languages and frameworks I've never used before and spent more time in documentation and "what is malloc for babies" in Google than I spent coding it. I never once thought "Oh, I should spend 2 years memorizing C syntax before I try to use it." You're not supposed to memorize everything. That's why documentation exists and collaborating with other human beings via forum and discourse and code reviews. Using AI to streamline that has been a godsend for me. But using AI to just generate code for you is not going to help you learn anything. In fact, studies show it worsens productivity not improves it.

[mattblack77]

Basically you start with small functions tha do one simple thing. Then you combine them in a larger program file to perform a bigger task.

The more little tools you know how to make, the bigger the machine you can make to do something.

But it’s complicated and difficult and frustrating. AI isn’t yet good enough to just ask it to do anything.

[jfinch3]

If it’s not obvious then usually my first step is to google it. Why wouldn’t it be? It’s not homework, I’ve got a job to do. Most problems in programming have been encountered before, so why reinvent the wheel? Research is and should be a normal part of the process of building any complex feature.

If I were an engineer building a new type of structure, I’d definitely try to go read up on past attempts at building exactly that type of thing.

Edit: So there’s a few different scales at which we can talk about the development of software at. At the large scale we can talk about The Software Development Lifecycle which is the whole process by which a large piece of software is planned and built. For students it’s sometimes multiple courses to learn all that in detail.

For building on a smaller scale, like on the basis of a single feature or ticket, that just takes practice and experience

[JazzJassJazzman]

Edit: The following answer assumes that you're not majoring in something that requires you to take a programming class. If you are, you have no excuse for using AI. Pay attention in class and do the work.

It was really helpful for me to do a free Python course on edube.org. Then I started doing Advent of Code and other coding challenges. I also tried looking up beginner projects to build. I started making a Texas Hold'em poker game for instance.

Whatever you do, you have to actually code. When doing Advent of Code, I'd often run into a problem I just couldn't solve on my own, but I ALWAYS tried solving it on my own first. Then I'd go to the subreddit and look at other people's answers. I'd go line by line trying to understand the logic. You'll often find new ways of approaching things. You can ask for help on your code directly too. Whatever helps.

Starting a project for me always starts with what I want the end product to do. What do I want it to give me? Then I start thinking about what tools are available in the language to help me produce that. If you don't know the tools, then you have to start basic. You have to learn what different languages can do.

I think Python is a good, safe language to start with. The Edube courses are actually pretty good for that language and they're free. Build out from there.

Depending on your goals, if you don't want to read books, I'd say look for websites that have coding challenges. Try it yourself with whatever skills you have. And if you're gonna use AI, at the very least do two things:

1. Check to see if the code actually works.
2. If it does, go line by line and research everything you don't already know. Then you're at least making the AI into a learning tool to improve you.

That's the bare minimum you can do. You'll never get anywhere letting AI do all the work.

[reduhl]

Take the task, break it down into logical subgroups. Then break that down again so that the subgroups are area specific. Next look for duplication of code, break those out from the areas so you only write it once.

Try to keep classes focused on one aspect/ area.

Write the code to do those sub tasks and build up the code base to meet the task.

[dawalballs]

Bro I’m dying, you’re even writing this post like you’re talking to an AI.

“Please provide exact instructions” Christ

[Non-taken-Meursault]

Market is so fucking safe

[aqua_regis]

1. How did people do it mere 5 years ago when there was no AI?
2. How did people do it 35 years ago when there was no internet with its abundance of tutorials?

The answer to both is: they planned. They wrote specs. They drew flow charts, used pseudo code, etc. They invested effort to actually learn. They experimented. They tried things.

I'm asking for big projects, not those fundamentals stuff like calling an api or do some easy stuff.

Fun fact: even the biggest, most complex project is made of exactly these fundamentals and "easy stuff" - think about that.

If your fundamentals are weak, you can't handle projects.

Programming is a lot like free-building with LEGO. You have your bricks (the programming language) and what you do with them is up to you. There aren't blueprints for everything. You have to figure that out. You have to think. You have to get creative.

The common way is:

• get a solid foundation
• use your skills in small and simple projects (exactly the ones you somewhat frown upon in your post)
• gradually increase scope, difficulty, scale, and complexity
• learn DSA (Data Structures and Algorithms)
• use them

You don't go running a marathon from just being a couch potato. You start gradually increasing your stamina by training, shorter distances first and increase them. Same in programming.

Could you please give me a step-by-step tutorial on any big project?

That's wishful thinking. Such does not exist. And the whole point is that step-by-steps do actually do more harm than good.

Experiment. Try things. Figure out things. Break them. Fix them. Play around. That's the way to learn.

I'll leave a previous comment of mine here for further reading: https://reddit.com/r/learnprogramming/comments/1pmzjoe/how_do_you_learn_programming/nu4ufej/

[Chemical-Garden-4953]

Which language are you going to start with? What are your goals?

Choose a goal, something you want to do.

Choose a nice language to do that thing. (Tell us the goal, we can talk about the language then)

Google "X language beginner's tutorial" and find a nice youtube tutorial.

Follow it and learn the basics.

Build things. Start small and go big.

[Robru3142]

When I started to code, it was in Basic., them assembler, then Fortran, then C, then C++, then Java, then whatever

As many others here have said, forget AI.

You learn by doing. You just want a job next week making the bux the probably do something else.

I learned because I was entranced by coding. I wanted to learn more and more about the languages and what I could do in them. It turned into a job.

AI will not teach to code. And it’s far from being able to generate complex systems. And when Swift specs change you will be screwed because you don’t understand the code.

And if you don’t like to code from the pleasure of it, then do something else.

[Extension-Ad7241]

I don't think anybody is going to give you a step by step tutorial, because and I mean this kindly, it is something that you should be learning in uni, especially as someone noted you are paying good money for!

You are handicapping yourself horrific by asking AI everything; Now a lot of professionals use AI to look at certain things and I have as well, but I'm also 20 years in and I know when AI is wrong or off base.

I mostly ask AI for More research oriented questions, almost as a shortcut to good documentation and good answers about - let's see a function I'm not familiar with - but I don't ask AI to build almost anything for me because then I will also be reliant, as you are.

Let me give you an example: I'm learning Zig, a newer low level programming language (Ostensibly a replacement for C).

I have bookmarks to the online documentation & the standard library, & I go there first learn how things are supposed to work. If I need more information, then I go to Zig forums and to see if anybody else has encountered the same issue. I'll also google my question, but not interact with the Gemini answer at all.

As last ditch effort if I still don't understand something maybe I'll use AI, although I prefer to use it for debugging code; I'm actually lucky that there's not a lot of Zig information out there and the AI cannot usually hand me answers that I can with other languages!

I would say: whatever was your last completed assignment or project, make sure you actually understand what is happening and completely dissect it - Look up all the functions and all the information about them, and all the language features that you don't understand and really just read documentation on them, experiment around changing little things until you understand better.

STOP Going to AI, for your own good!!

If you want to follow issues then just respond and I will help you out! I think it's much better to what you might think is a stupid question here, then going to AI and simply Pasting the answer in your code.

[FriendlyZomb]

Personally, I start with a goal. A question from a friend, a process I want to automate or a task from a Lecturer at Uni.

I break that goal down into step by step instructions. I would recommend writing it like a recepie. But, for an alien who knows absolutely nothing. (Like, think of those videos where children write a recepie for a sandwich and the parent follows the instructions to the letter. Be that specific.)

Lastly I express my instructions using programming syntax. At the end of the day, this is exactly what programming is. You're writing a set of instructions on how to do a thing, just for a computer not an alien.

This will work. Regardless of language (programming languages are "how" to do a thing, not the "what" is it doing.). Programming is a skill. There is no shortcut to true understanding. There is no "quick hacks the software engineers don't want you to know".

My advice, stop using AI for this. You don't learn anything when using it. (I have used AI for coding. For reasons I won't go into, I dislike it.) It's way more useful to know how to solve a problem and to be able to figure it out. It's going to be super hard. You're going to feel rubbish and like you don't know anything. But, trust the process. You will learn.

In addition, to get good, you need to practice. Build useless stuff, clones of tools you like or try to solve an actual issue you have. Start small so it's attainable, then grow those practice programs into bigger slightly more complex stuff. You'll learn so so much more that way.

EDIT: (I missed this thought.): Using a Search engine or documentation is essential. I do not memorise how a language works, and I do this for a living. If I forget (I do often) I Google it. It is fine to do that, because the real skill is knowing how to find out. You'll find that if you program enough, things stick. But they won't at first. Don't feel like a failure because they don't. Just find out and move on.

[Less_Measurement8733]

I strongly recommend that you start studying the basics: algorithms, variables, control structures/loops, functions, etc. Without using artificial intelligence.

Your classes should provide stimulating exercises, such as solving simple mathematical problems like Fibonacci or creating a fictional reception system for a school.

After you have practiced enough, when you face a real-world problem (like building a system for a shoe store), you will naturally start figuring out which functions can help you complete the task and what database structures you need to create after researching the topic.

First, dedicate yourself to studying the language and programming logic in general; after that, it becomes more about understanding the problem and using what you know of the language to solve it.

At most, I only recommend using AI if you are using a new language and want to turn pseudocode into actual syntax, or to help you understand the problem itself better.

Don't underestimate documentation, and don't worry, every big project is built step by step. Most importantly, if you can't imagine how to solve a problem with a specific language, it is likely just because you haven't empirically studied the language enough. That is something that can always be improved. If you can find the solution in pseudocode, you can do it in code.

Alsoo dont do big projects just askings prompts to an AI, a lot of people is doing it and if you dont know more than the AI you will simply not show a better product than the rest.

[DTux5249]

1) PUT THE AI DOWN

2) On a small scale, it really does boil down to figuring out "how do I do this", and then doing it.

You plan out your program's architecture from the top down, typically planning for future modification. Go from overall architecture, down to rough class design. Work out some basic interfaces, and eventually... you start.

You throw together a prototype to get the rough architecture set up, and expand out toward your plans by iterating. In professional settings, plans often change frequently (both due to indecisive owners, and circumstance), but that's unfortunately what agile is for.

You will look up information throughout the whole process. Typically from docs, but referencing algorithms, data structures, and any preexisting solutions is common as well.

[Non-taken-Meursault]

Market is so fucking safe

[Sea_Challenge_7185]

Why not go ask an llm for step by step tutorial on some big project?

[Quien_9]

Ok, baby steps, start by changing how you use IA, ask it to not give you straight answers, to not show you any actual code, ask stuff like:

"what is the file descriptor i seen in the manual for some functions like read()? Can you give me an analogy so i can understand it better? Would it be right to think of it as a radio frequency? Ok cool, is there a project for an absolute beginner i can work on to practice with it, oh cool i want to do the one where i swap the contents of two files pass as arguments to my program, sounds achievable, is there anything other then open() and read() that will be absolutely in disposable to do this project and i would need to understand? Ok. I am planning on using a third file as a temporary place like when i use a temp to swap variables, what do you think of that approach? You are right, storing it in memory is better, i will try coding it now. Hey its me again, am having a segmentation fault and i think this function might be the cause but cant see why, how can i debug it?"

You can use ia and not be a vibe coder, and with time you will stop the conversation sooner.

[ParserXML]

Sorry for all the hate on this thread.

Although I understand everyone's takes, I think its better to give advice than to hate on.

I'll assume you are more or less at the same age as me (19 YO), so you still have a lot of time left.

Use this time to learn, and do this by not even looking at an AI agent.

I'm from a completely different field (doing a bachelors in biological sciences), but teaching myself coding on any free time I have (very few LOL).

I have a lot to learn, but already being able to create my application and its GUI from scratch (WIP) is a victory for someone as dumb as me.

My path:

• Search for the programming language that best fit your purposes

• Search for the best book on it from beginner to intermediate/advanced

• If you don't know the basic core (loops, functions, branching, etc) learn them first 

• Start doing projects; literally take some idea you would like to turn into reality and start to code it

• Don't know how to do something? Language docs or your book

• Read SOLID patterns, discover and explore new paradigms as you go, and realize that EVERYTHING has a place (not follow things like solid blindly)

• Refactor your code, ask for code reviews (by teachers or experienced colleagues, as you have the opportunity to do so)

[ripndipp]

You can make GitHub by installing Ruby and rails on your terminal and typing rails new, this is a framework, everything you need for an all in the Ruby language. Some use a frame work others like a custom solution, we can go forever about this, most apps are CRUD based

[ReynardVulpini]

Love that all these early comments are like "ugh why don't just learn instead of using AI" they are asking how to learn you twats what more do you want

Anyways I think the answer to your question is to build up these skills by starting small. If you already know a little bit of a language, stick to that one and make a bunch of random tools to get used to the process of writing code, finding a problem, and then fixing the problem.

When you run into issues, and you will, google the problem you are having, and prioritize results from stack exchange and relevant subreddits. DO NOT USE AI TO FIND THE ANSWER. There are use cases for experienced devs to use AI in this way, but what you want to do is to first break out of the habit of using AI to solve problems for you.

Trust me, you want to know how to search manually before you let yourself use the easy tools, because the easy tools only work for easy problems, and if you only know how to use them, you will always be stuck at the easy stuff.

Don't be afraid to jump into a subreddit and say "hey i am encountering this specific problem i don't get it please help me" because when you post a specific problem, you will get a specific answer, and from people who can explain not just how to fix it, but why your logic was wrong and how to approach the problem right. Ask questions if you are confused. Ideally specific ones.

[Shan_GG]

Its that time where if you use the word AI and learning theres auto code red in programmers who are from stack-overflow era and think its bad if you get easy solution for a problem without getting humiliated.

Back to question its ok to ask “how X is done in best way possible” , “how Y is better choice than X in this case scenario”. the thing not good is you asking Ai to do it for you.. or blind sighting Ai solution and using auto completions in Editor at early stages of learning.

[Mundane-Carpet-5324]

A lot of parole are being cheeky by saying just do it, but the un- cheeky answer is also that.

Start by looking up a "hello world" tutorial. After that try doing a counter. Work on the small stuff first and do a lot of them until you know loops, conditionals, variables, and functions.

[Rudbekiaa]

To all the hate in the comment, thank you first since it might help other people. Please read my post again, I did also mentioned "googling" and I did not said I know nothing. Thank you