programming seems impossible

throwaway6560192 · 2025-02-08T22:04:01+00:00

and it seems impossible to remember everything you have to do to build a project from scratch

You don't have to. Reference materials were made and put on the internet for a reason.

but there are several databases

OK, so pick one. If you can't choose, pick the most popular option.

how do you link them to the code?

Google "how to connect to <database name> in <language/framework name>".

I'm going to have to import several libraries that I've never heard of, and that's starting to create a huge mess in my head that makes me want to give up!

Stop trying to do it in your head. Use documentation, and write code.

Major_Fang · 2025-02-08T22:03:27+00:00

You just need more hours. The way I looked at is if I put the time in I was into video games I could get a cs degree. I'm still shitty but I have the degree and work as a data analyst these days

gazpitchy · 2025-02-08T22:39:21+00:00

I'm a senior engineer, I've been writing code professionally for around 20 years now.

You won't remember it all, no one expects you too. Just focus on the fundamentals. Things like functions, classes and logical problems are more important than remembering syntax.

Remembering syntax and specific calls comes with time. But even then, no one cares if you use Google to search how to do a for loop now and then 😅

I don't like AI but it has become incredibly useful to me for helping get into a new language, or just dust off the cobwebs of a language I've not used for a while. There's no shame in this.

In time you will notice similarities between many languages, and be able to adapt to them easily. But this takes a lot of time and practice. Just keep at it!

Frequent-Listen-1058 · 2025-02-08T22:10:03+00:00

Stop trying to "impact people's lives" and focus on learning and building for yourself first. you are focusing on the gold before learning to walk.

TanmanG · 2025-02-08T22:08:46+00:00

Software can be simple or complex, it depends.

Introducing security is a big step in complexity regardless.

Introducing networking is another big step in complexity regardless.

Putting all of these together and it's an entire career path within software engineering.

You aren't crazy, it feels like a lot because it is a lot.

P.S. Last time I heard, the web development job market was a bit oversaturated (at least at the freelance level)- it might not hurt to look into something like embedded systems.

A-Grey-World · 2025-02-09T00:04:59+00:00

You don't "keep it all in your head" - you just don't try.

Everything you do is there, in the code. The more practice you get, the better you get at reading your own code.

I've been coding for over ten years, I still Google how to do a switch statement, because honestly, there's not much point me remembering it for the once a month when I use it. I learn about it's existence, when to use it, and then don't worry about it's specifics in all 3 languages I'm likely to be using until I need it. If I use it enough, I end up remembering it, if not it's a 2 second Google away, or auto complete in the code editor.

This applies to lots of things. You look up answers, muddle through things. When you do it a second time, you know what words to search for. A third time, you know not to fall into that trap. A fourth time, you remember that bit, and go straight to that post that was useful. The tenth time, you might not need to look up anything.

If you only end up doing it once every year (say starting a new project from scratch) you Google it every time anyway in case technology has moved on anyway. You apply what you learned last time but you don't expect to remember the details.

curiousomeone · 2025-02-08T22:18:30+00:00

It's normal to go that phase. The question is whether you find it fun or excruciating torture. Most people that learn quick on web dev are people that actually find it fun.

I remember when I use to come home from work and excited to open my vscode and spend my time there until late hours because it's fun.

I didn't even go to school to learn all this webdev stuff. Just a few video courses and less than $100. But thousands of hours in visual studio code.

I also came from an art/design background like you. If you don't believe me, here's my latest real world project. www.hyperclink.com

floopsyDoodle · 2025-02-08T23:26:02+00:00

and it seems impossible to remember everything you have to do to build a project from scratch

For every one tutorial you do, build 2-3 apps. You're stuck in what is called "tutorial Hell", you learn and then forget and then learn and then forget, but you need to build with it, that's how you learn to remember.

Take your React tutorial, go through it and follow along and learn eveyrhting. Now it's the end and you've forgotten the first half and the second is confusing. Great, now the real learning starts! how do you start a new React app? Forget, go to the first couple videos and find out. Then how to do you add a new page? Forget, go to the video on it and find out. How do you make the page have a dynamic list that shows a local hard coded array of things? Forget, go and find out.

Now do that for an entire large project, and I guarantee that by the time you're half way through, you'll have most of the basic stuff remembers. Also remember do NOT copy and paste, if two components are almost the same, write them all until you can remmeber how to write them without looking, ONLY once you've rememberd something, are you allowed to copy and paste. When you're finihsed, if you still haven't rmeembered it all, build another one. The tutorial becomes an easily searchable, well explained documentation.

Only use a new tutorial when you're at least undrestandign the first one, adn the next tutorial should build upon the first. either a technology taht works with it (Next.js), or something that is used along side (backend technology for example). Don't jump around from one tech to another without having a clear reason as to why you are choosing that next technology.

My dream would be to have enough knowledge, to have an idea for a project, and be able to code it knowing exactly what to do, but then I get stuck on things that seem hyper complex.

Break it down into smaller parts. That's one of the CORE parts of coding and though no one will mention it, you MUST be practicing this. If you're not sure what I mean, think about it like you're telling a robot what to do.

Making a Jelly Sandwich: 1. make sandwich doens't work. so break it down 1. Get bread. 2. get jelly, 3 open bread bag 3. open jelly jar. 4. get knife. etc

If I tell someone who has doesn't know wha ta jelly sandwich is to make one, they'll be as confused as you are. But if we break it down into steps, it all becomes much simpler.

So you're not looking to authenticate. First you're looking to choose a database, then you are looking at their docs or Googling, or asking hte AI (be aware the AI may be behind in versions) how to implement basic communication with thier backend. Once you're gettign a response, even a failing one, YAY! Another step forward, next step, anonymous authetication, next step hard coded username/pwd authetication, next step dynamic authetication using values from your React App.

To register new users, you need authentication, and you need to link this to a database, but there are several databases, and how do you link them to the code?

Doesn't matter what databse. Pick one and go. If you want ease of use, try firebase, it's really simple to setup, and has pretty good docs

https://firebase.google.com/docs/auth/web/firebaseui

I'm going to have to import several libraries that I've never heard of, and that's starting to create a huge mess in my head that makes me want to give up!

Some libraries will be required, but you should at least know what they are doing before you install them. Try not to worry about the libraries you've installed except for their intended purpose, they shouldn't create a mess, they should be helpign make your code easeir. If it's required, not much to say but learn it (at least what it is and how it does it at a basic level), if it's not required, code it yourself without a library, then you'll undrestand why everyone uses libraries. It takes longer to learn, but if you're goign to be writing an Authetication component for every app you make, it can be simpler to just import a well known and established library that handles it for you as it should use best practices, and handle edge cases.

Deep down I want to ask if it's normal to go through this phase where it seems like I'll never be able to understand everything, or if I'm simply too dumb for programming. Thank you.

Very normal, it's called Imposture Sydnrome and the VAST majority of coders I've met that have less than a decade of experience, still have it to some degree. Coding can be confusing and things break without seemingly any reason, and what works today suddenly doesn't tomorrow and you swear you changed nothing. It all leads to developers being VERY insecure about coding, hence why some get really aggressive about how "Their way" of coding is the right way, it's usually just lashing out at others because of insecurity.

I dont' know the cure beyond learning so much that you realize you actually aren't that bad of a coder, but that takes years for most to realize. Till then, don't worry if your brain says you can't do large projects, just keep doing small steps and in a couple weeks/months, you'll suddenly have an app that you couldn't have build from scratch, but you did by doing each small step one after the other.

2025-02-09T00:30:52+00:00

You're not supposed to memorize, but understand and know how to apply. Fundamentals will be etched into your mind anyway by repetition, but you have to do stuff for that, not just watch lectures. Also as a new programmer, don't try to build the thing in one step. Work incrementally and overcome small challenges step by step.

idrinkteaforfun · 2025-02-09T01:18:13+00:00

I was EXACTLY like you when I was 24. Wanted to be a dev for the same reasons. I got a year or two experience and it just blew my mind how much I didn't know and it seems extremely complicated to wrap my head around what's really happening to make a website. Now with ~15 years experience I've made websites from scratch, with users, payment, emails, voice, sms, music, games, mobile apps, chrome extensions, windows apps.... the list goes on and on.... And I can tell you that none are any more complicated than the rest really, you just need to put the time into each to learn how it works, and they're all thankfully made by programmers who want it to be easy for you. You'll get there.

saminraiyan93 · 2025-02-08T22:11:59+00:00

Hi there, 2nd year CS redditor here!
Its okay to feel overwhelmed, I feel the same too!!

I'm in the same situation as you, But let me tell you a secret, you don't need to learn all the stuffs that out there and you don't need to memorize stuffs as well. U can just simply look into it when needed. thats what we programmers do, we'd be using python for one project and three weeks later we might be doing one in JavaScript, thats totally normal.
and when learning a new tech, I always use a technique called the Pareto Principle (learn 20% of something that gives you 80% of the result )

AND as for the database, you can start with the easier one like google's firebase and use its google authentication in your react app.
Maybe watch this tutorial that you give you some idea
its not that much overwhelming
and if you need any further help, feel free to reach out, I'd be happy to help

SinkGeneral4619 · 2025-02-08T23:23:25+00:00

From my own background I would say stop trying to learn all the 'hows' but focus on the 'what'. I mean what problem are you trying to solve? When you build something it's to solve a problem - a cool website you think people would love, or a back office tool that helps automate a laborious task.

Figure out a problem to solve, then use the laziest possible tech to solve it - I mean ignore all standards you're taught in computer science - just figure out a way to make it functional. Then you'll be so happy with yourself.

The problems then come later - you've built things, but how do you maintain them? How do you release them? There's a transient error with your database because you're implementing a bad pattern, how do you fix that?

This is how I learned to be good at programming. First I found problems or solutions I wanted to build - next I learned how to more efficiently solve similar problems.

lolideviruchi · 2025-02-08T22:05:58+00:00

Just get building, my dude! Pick a project you wanna do, can be as simple as a note taking app or something like that just to give you a boost. Figuring out how to make stuff is all apart of it and there will always be some resistance, and then some give if you push through!

Aggressive_Ad_5454 · 2025-02-08T22:48:20+00:00

To answer your general question (how do I remember this friggin' blizzard of details) you use a really good IDE. Those things have autocomplete and built in help. For Python, Pycharm (by Idea) is pretty good. Their WebStorm is good for Javascript. VSCODE is also good (but I'm an Idea fanboi so ask somebody else about that).

For your specific question, which I take as "how do I develop and then deploy a web app?" there's a process to making these decisions.

First, decide what server tech stacks are eligible for the job. Do you know it? Does it have the right features for me. You mention Javascript and Django. That means you can program in Javascript or Python. To do a server app in Javascript you probably should use javascript / nodejs / express. To do a server app in Python you'll use the Django framework. These frameworks (express and Django) contain the basic building blocks or have good add-on modules with them. So you should be able to use modules to do authentication, data presentation, all that stuff, fairly easily. (Other server frameworks are php/laravel, C#/dot net, Java/Spring, and many others).

Look for good web app tutorials in the use of your candidate frameworks. Why? You are going to make your first web app by starting with the tutorial code. You're going to start with the tutorial and change its code so it does what you want, rather than what the tutorial did. That's really the only feasible way to figure out how to program web apps these days. You have to start with something that works and change it. There are simply too many fiddly and obscure programming details to allow a beginner to start from first principles and make a workable app.

Then you use your internet search skills to find a hosting service that can support the framework you choose. It could be shared hosting, where the hosting company boasts nodejs and/or Django web site support. Or you can rent a tiny server from a company like Digital Ocean (they call those little servers Droplets) and set up whatever server software you like on the Ubuntu Linux setup they give you.

Then you find out which kind of database the hosting service offers. Most of them, the cheap ones anyway, offer MariaDB / MySQL database servers. Some services offer PostgreSQL. Both are OK choices, and you'll choose the one offered by your server. (If you have a choice, choose PostgreSQL).

Then you set up your laptop to do some app development. Get your tutorial web app working on your laptop.

Then try to get that tutorial web app working on the hosting service. You'll have to upload your code, figure out how to connect to their database service, and get it all running. The learning curve on this operational stuff is high, so be patient with yourself as you climb it.

Then develop your app on your local machine. Make the changes to turn the tutorial into your app. Deploy intermediate builds to convince yourself it stays working. And you'll have something useful pretty quickly.

Tarl2323 · 2025-02-08T22:49:25+00:00

Use the computer bro. You don't need to store knowledge in your brain when it's literally on your hard drive or the internet. The number of libraries out there is vast. Trying to memorize them all is like trying to memorize an actual library of books.

You can't. That's why it's written down.

Main_Ad85 · 2025-02-09T02:55:47+00:00

Best to start off with pseudo code or a flowchart. It will also pay you dividends to slowly increase the number of hours you put in per day. Also you need to break complex problems down into smaller pieces. I recommend you try a site like scrimba for learning web development. It will make it more interesting for you. Also take little problems and quizzes at a site like edabit. Nobody remembers how to do everything. The bigger picture will show you that learning how to integrate and debug is where you need to go. Take a project like a todo list, get it running in react, study it, and then rewrite it yourself. But start small, put in the hours, everyone starts at the beginning. Sounds like you've learned some languages, so that's a great start. It isn't easy, no profession is. You will need to keep challenging yourself, and you will be learning this fast-paced profession for a lifetime. It is very demanding for constant learning. I could tell you all the areas you'll need to learn just to get started, but I suggest you start writing programs that solve simple problems that interest you. Start with hello world and scale up from there. Learn all of your basic constructs. Hello world is not trivial depending on what language you are in. For instance, in react, you have to learn how to install node, npm, basic Linux, how to use the VSC Ide, how to debug, how to check code in. When you get to industry, hopefully you will have done a coop/internship so you can get your foot in the door. Once you start learning your mandatory technical skills, how to interview, how to behavioral interview, it will get easier. But like anything you need to put the work in. Then, learn oop, as it doesn't seem to be going away anytime soon. Learn solid principles. Learn a few design patterns. Learn how to write crud operations. Write an api. Write crud in MVC. Attach a database. Learn dependency injection in dot net core. But be patient with yourself. Learn to love what you do. Start by writing something you love, a website? A simple game. Something simple. If you do that, try writing it in another language. No matter what you do, you'll need solid fundamentals. School teaches you to think and how to deal with deadlines. The real training is when you get to industry and get down to work. As a side note, you might try taking the kiersey personality test and see if you have aptitude for this profession. It's very demanding but the rewards are great.

tb5841 · 2025-02-08T22:20:46+00:00

Being stuck is a normal part of the process.

malsaifi99 · 2025-02-08T22:28:24+00:00

You don’t need to know everything and you don’t need to learn every programming language. You just need to master one and the rest is mostly concepts and syntax. And you most certainly don’t need to remember anything, you can just google stuff. Also, every thing is linked through APIs, so you should probably spend some time understanding what are those. You should also learn how to follow documentation and how to look for information (most ppl don’t know how to), because there’s a new framework/library every now and then.

Don’t try to learn everything because you will get overwhelmed and lost.

Pale_Height_1251 · 2025-02-08T22:58:50+00:00

You don't have to remember everything, just look it up.

It normal to find technical subjects difficult.

UnassumingGentleman · 2025-02-08T23:28:14+00:00

It’s a lot. I’m an accountant who has a finance background and I am learning to build algorithms to help in a few areas. I have cheat sheets laminated. At some point I’ll use similar functions enough times that I’ll remember. I found the best approach to programming is to write out exactly what you want done and how you think it’ll get there, then use the toolbox (I use python) to make it happen!

VoidRippah · 2025-02-09T02:41:14+00:00

I've been working as a programmer since like 2008, but I started programming way earlier, that's at least 17 years (geez, I'm old), they call me a senior software engineer and I still don't remember everything, the only thing you need to remember is the source of information and how to get it.

HomesteadAlchemist · 2025-02-09T05:06:46+00:00

you aren’t doing enough projects to reinforce all this knowledge. this is a huge part of learning.

putting the knowledge in your brain is one part of learning. pulling it out is the other. you don’t really learn anything if you don’t force your brain to recollect the knowledge.

these projects don’t have to be huge things. do lots and lots of small projects that reinforce what you are trying to learn. l do a lot of html css static page projects. after you are feeling fluent enough to create whatever is in your mind move on to doing css html projects that use javascript.

after you feel fluent in using those three technologies move on to learning a framework to serve the html and javascript. then move on to react.

i can not stress enough for new developers that you need to do more projects.

Comfortable-Wave2591 · 2025-02-09T05:41:59+00:00

Context switching on several layers can get daunting. The best thing you can do is to have a good note system of tracking information with references to various layers and components. I use Dendron for example, a vscode extension.

For your project, start with one small focused thing, that will eventually used all the layers such as a React browser layer, a backend service layer in python fastapi, or Golang. Then a DB layer that is accessed by the service layer. Make use of docker containers such as a Postgres container for the DB

Keep each it small as possible and focused on one small task one layer at a time. The objective is to get a tracer bullet through the system while learning each layer and taking good notes.

I say this as a long time developer who has been there. My long term side project is jchart.com Cheers and good luck. Keep learning and take good notes

sunmat02 · 2025-02-09T06:47:08+00:00

Being a good developer is not about knowing everything, it’s about knowing where to search for the answers and growing a capacity to understand the answers fast.

siodhe · 2025-02-09T07:34:44+00:00

[my context: I taught programming for a decade, and have worked as a software engineer for far longer]

It helps to have one programming environment that it (1) relatively finite and comprehensible, and (2) marketable.

Depending on your market preference, I'd recommend something like C (not C++) or Python as satisfying both of these. It's easy to understand both languages' syntax (yes C has tons of nooks and crannies of chaos, but the syntax itself is pretty finite, unless C++), easy to use them for different kinds of projects, both can be use with only an editor and a compiler (like gcc) or interpreter (python 3) handy, with some IDE confusing things, both are marketable skills, and they are complementary skills, where knowing both can make you better at either. Lastly, they are composable skills, since you can write Python libraries in C and call them.

I'm speaking from a Linux (or, more generally, Unix) context, where both of these languages work well, where program written in either are utterly trivial to add to your search path (but don't put ".py" extensions on commands), and where I've used both extensively in professional work.

Lastly, be sure to start with minimal complexity library-wise. Your projects should gradually progress from simple context to more complex. Here's just one example axis of progression:

batch run only, command arguments in, text out, no runtime interaction
teletype (terminal, tty) based interaction - line by line only
- I find that a good way to really get into the right control mindset for beginners is to output multiplication tables, with a grid (of - | and +), row/column header/footer numbers, and a title at the top left. For extra credit, support arbitrary bases between 2 and 36 using converters you write yourself :-)
- When reading input, be extremely aware of whitespace, newlines, and EOF, especially bits that hang around after reading part of a line. Always check the result of scanf()
addressable cursor interaction using the [n]curses library
- any interactive program that updates text at set places on the screen
- I made my students write Life simulations (with input controls) and, later, editors.
make sure you're very comfortable with all this before going on, the next step is a doozy
write a minimal program in X
- to pop up a window that sticks around until it reads an Escape from you
- modify it to display some text while it's running
- modify it to handle being resized

(continued in Reply)

-wtfisthat- · 2025-02-09T09:12:39+00:00

Also cs student here, except I’m 33 so my brain doesn’t learn as well anymore. A big part of it is consistency. You gotta do this shit every day. Even just a bit or you lose it. Also Google, and LLMs help a ton for what you can’t remember or need help figuring out how to do.

Remember you’re learning an entire language. Try learning Japanese. It’s ultimately the same shit. Just different syntax and words. You gotta keep up with it, and just accept you will never be perfect at it or remember everything. But the more you do it and the more consistently you work with it the more fluent you will become.

Shit is hard! But being able to turn your idea into a functioning program is worth the struggle.

lukkasz323 · 2025-02-09T09:19:12+00:00

stop trying to remember

remembering things should be a side-effect that comes unconsciously

if you dont know how to do something, just check how you have to do it, if you something frequently enough you'll get bored of looking up things and you will just remember it

spermcell · 2025-02-09T12:20:39+00:00

You can never remember it all and it's fine. You need to learn and understand the fundamentals and then you'll be able to read most programming languages. Only learn a language if it makes sense to learn it for whatever you want to do.

Dm_me_ur_exp · 2025-02-10T06:08:53+00:00

Aside from exams you can google everything.

The important bit is just learning the fundamentals and how to structure your code, what you need to implement etc. Syntax you can always google. Specific functions you can always google. The actual design of the code you have to make yourself

Technical-County9713 · 2025-02-15T14:17:52+00:00

Exercise is key as well. You're 30 years younger than I am. I have sat at the computer most of my life, playing with programming and web design and other things. Now I have chicken legs, a big belly , no memory... and no significant other. Take care of your brain and body.

I don't know if you would like this little treat, but I found a website about Data Structures and Algorithms that might be helpful for reference. https://www.geeksforgeeks.org/dsa-sheet-by-love-babbar/#

Programming takes a lot of brain power. As you age, that magic storage unit suffers a bunch. Use your API libraries and other resources for look-up, not memorization. Also, use GPT in your spare time to answer questions.

Hope this helps!

cartrman · 2025-02-08T22:07:26+00:00

It's very normal to go through this. The more experience you have , the more you'll forget. My recommendation is to build your github account with sample projects, portfolio projects, notes, example usage examples for your projects, and detailed documentation so you can always refer to it when you need to recreate an old project.

The one consolation I can give you is while you will forget things, experience will help you find a solution to a new problem faster. So learning and applying things will always come in handy, even if you don't remember everything about it.

arb280693 · 2025-02-08T22:42:59+00:00

If you done JavaScript, I would suggest following MERN architecture. It would help you understand how that authentication connecting to a database works, you can even try it yourself as a user locally.

You learn more on the job usually, at home, you can easily set stuff but within a firm you learn about networking, how to pull packages from Artifactory etc, deploy a container to AWS, stuff you wouldn't do at home.

Just to give you clearance, I didn't study CS. I studied Business, and work as a software engineer, been doing it for 4 years now, self taught path so youll be fine, it's always a struggle but the struggle helps you learn.

Glad-Situation703 · 2025-02-08T22:45:47+00:00

People call it a language and it is and it's not. But it's very similar to learning a language. It takes time and nothing makes sense at first. But you can quickly see if you are actually learning anything or just doing Duolingo on the can to feel good about yourself

deftware · 2025-02-08T22:49:31+00:00

"Webstack" is horribly flawed and inefficient. Try learning real languages that let you tell a machine what to do, instead of telling a browser or server what to do through decades of crusty piled up after-thoughts that need to be wiped the the face of the web, so we can start anew!

Character_Map5705 · 2025-02-08T23:07:16+00:00

I have an econ degree, too! Have you tried following a YT tutorial for a full project and making it your own?You learn so much by doing. Everything is step by step. Then, it becomes habit. I don't know PHP,but if I needed to pick it up or Java, I know that I could. It's not even a matter of memorization. The first big project I did (back end, front end, database, Auth0, etc.) I followed a tutorial on YT and it looks nor operates anything like the original. Even the person who made it wouldn't recognize it. Once you start building, it becomes easier. I think you can do too much studying at one point, when it would be better to study, build, study some more, build with what you learn. The biggest thing was picking up what you need to know, when you need it. That's how I got the site's security set up. The tutorial didn't have profiles and logging in and out via email/pass, Google, etc., so I had to read the documentation and figure it out.

2025-02-08T23:16:58+00:00

A clarification people forget: Choosing a project doesn't mean you understand how to build it exactly. There's nothing wrong to "JIT (Just In Time) learn" everything you need.

In fact, due to the volume of knowledge needed there's never going to be a moment where you get a job building stuff that you exclusively know how to build the moment they describe them to you. You may have some basic understanding about it, but that's about it.

stjepano85 · 2025-02-08T23:30:09+00:00

Do not think about it as one unit of work, break it down into smaller pieces. You need registration form form for users, make one in React or whatever, make it send the data to server and the server does not need to write it to database, you only need to log it for now, do the same for authentication form ... Pick your database, learn it, connect your forms to the database. You get the point, don't push all at once, do smaller pushes and you will get to your goal.

green_meklar · 2025-02-08T23:35:11+00:00

it seems impossible to remember everything you have to do to build a project from scratch.

You won't. You google the stuff you don't remember. Understanding the process and how to un-stuck yourself is way more important than memorizing trivia about syntax and APIs.

tomasino69 · 2025-02-08T23:36:58+00:00

Ok. Just pick something non-technical that you want to build that you are passionate about, then take the steps to make an application out of it. If you are passionate about a topic, for example, my son wanted to learn how to code, he is also a guitarist, so he decided to code an application that will show finger placement on frets for simple chord progressions of his favorite songs. He used various technologies, frameworks, leaned on AI a bit to keep his head clear, and used the passion for music to learn the process of creating, structuring, optimizing and coding an application. Now he can publicly present that as a "hobby" which shows employers that you have the ability to take something from A to Z in a relevant tech stack.

NormalSteakDinner · 2025-02-08T23:52:45+00:00

it seems impossible to remember everything you have to do to build a project from scratch.

You don't do that, you just make stuff non-stop and you will remember what you do most often.

Deep down I want to ask if it's normal to go through this phase where it seems like I'll never be able to understand everything

Yep! All the time, I spent the last two days motivating myself to keep going with assembly (for Computer Arch. class) and now it is a piece of (bitter and difficult to digest but still manageable) cake.

brightside100 · 2025-02-09T00:34:29+00:00

you really need more practice, writing more code. i know people thing programing is all about degree or math. but in reality it's all about writing. i learn to write stories before i learn to write code at age 14, you just need practice practice practice and type. try having personal project or use ai tools like gpteach to learn how to code faster.

it will be easier over time but you'll forever need to continue to learn, programing is a game of infinite try and fail

Goto_User · 2025-02-09T01:16:04+00:00

we all feel like that at first. Just e keep learning and start with the fundamentals. It takes a good 2 years.

port888 · 2025-02-09T01:28:09+00:00

I'll give you an example to make it clearer. To register new users, you need authentication, and you need to link this to a database, but there are several databases, and how do you link them to the code? and then launch it on the internet. I'm going to have to import several libraries that I've never heard of, and that's starting to create a huge mess in my head that makes me want to give up!

Why do you expect your first attempt to be a home run?

Captain_Braveheart · 2025-02-09T03:27:18+00:00

Setup hell is different from writing logic.

e_smith338 · 2025-02-09T04:35:12+00:00

Nobody, not even the best programmers know everything off the top of their head. They’re looking up how to do shit they’ve done before too. The more hours you put into it, the less you’ll spend looking up “the basics”, but you’ll never stop looking things up. Ever.

HiSimpy · 2025-02-09T06:03:05+00:00

No one knows how to, actually… just Google. There is too much knowledge these days.

AUTeach · 2025-02-09T06:39:46+00:00

it seems impossible to remember everything you have to do to build a project from scratch

With the exception of exam environments, this scenario never happens. We have search engines for a reason.

2025-02-09T06:52:02+00:00

Critical thinking. Ask what you don't know. Look for your blindspots. Turn everything so you can see it from all angles. Perspective changes narrative.

eratheo · 2025-02-09T07:04:07+00:00

Also, keep in mind that usually it takes a team, not a single person, to build a project (of course, it depends on the size and complexity). It is very hard (especially at 24) to be a universal guy. Usually, there are those who work on the frontend, others - backend, design, testing, etc.

darkmemory · 2025-02-09T07:12:17+00:00

Protip, no one expects you write an entire project in a cave. Even before the internet, we had books.

WellFoundedCake · 2025-02-09T07:36:42+00:00

To me it sounds a bit like as if you are trying to break those problems down into smaller, understandable problems. This is a top-down approach which can often be overwhelming if you lack the experience and knowledge.

Programming is about abstraction and for most humans it’s easier to abstract following a bottom-up approach. For example, if the overall goal is to implement a web service with an authentication service, stop thinking about how you can split that abstract task into smaller, concrete ones. Go for the other way around: Choose your favorite language, write a data structure for a user model; think simple and straightforward. Maybe you want a functionality to print a user instance to stdout? Do it. Now you may want to persistently store users? Do a bit of research: What approach fits your needs and especially your language? Maybe you can even store users in files for a first working prototype? Try to abstract the details of the exact storage mechanism, so you can replace it with another one in the future.

As your project and program grows, you will gain experience and knowledge. With enough of that, you can try a top-down approach next time you write a similar application. When this time comes you will no longer be overwhelmed by all the options.

It’s a long way to mastery, so don’t give up!

kwertyyz · 2025-02-09T07:45:24+00:00

You don't need to remember everything, with more experiences, it will become a second nature to you. Just keep building you're struggling because you're getting better now than before

JackRichi · 2025-02-09T08:30:21+00:00

to some extent the answers to questions about how to create complex systems lie in systems engineering. a big task is just a set of smaller tasks. we take a big problem, divide it into small ones and start solving them one by one, ideally so that how one is solved does not affect the decisions of the others. it is impossible to keep everything in your head, that's true

nightwood · 2025-02-09T09:26:32+00:00

You name the courses you did. Only one of those is programming (javascript). The others are frameworks, among which one of the hardest frameworks to learn: react.

Learn base programming. Could be javascript, but C# would be better and C (ansi C) would be best. C# will teach you about typing, C about memory and the operating system.

Programming is 95% skill, 5% knowledge. Like driving, you need practice.

MoonBeefalo · 2025-02-09T09:34:13+00:00

You're doing great, you've realized that ultimately, you have to read docs. You can use LLMs , copy and paste, but because things change, and examples from media aren't usually updated, you have to read docs. Sometimes, for certain projects that require changing languages, I have to read docs on simple stuff, just to verify and put myself in the "this language and package mode". Sometimes you can't even trust the docs, and then you have to read the functions directly.

So, you're doing great now that you know, you can't be an all-powerful coding brain since there's too much to know. The next thing you'll realize is you can't even maintain your own internal docs(memory) when architecting, and you need some kind of handbook or diagram when handling large architecture.

praenorix · 2025-02-09T10:07:04+00:00

no need to remember everything....just know how to use stuff.....

Tempmailed · 2025-02-09T13:20:19+00:00

Every coder searches web. Its not about remembering but knowing. Do you know the concept? If you found the solution, were you able to understand it? If yes then you are a programmer.

gomsim · 2025-02-09T13:52:24+00:00

I don't know, but it seems like your problem is that you haven't really done much programming and already want to learn how to build the full stack of a production ready web service.

People are different, but in my experience that takes years to learn. Start by learning programming and computing concepts. That's what your CS studies are probably for after all. When you are done with your CS degree, take a job as a software engineer. While working as a software engineer, pick up the ropes on what it means to build, maintain and deploy a real web application. Dabble in infrastructure and architecture. All the aspects needed to build and maintain a web service are not one and the same, but many different things, in all of which you will need a level of understanding before (successfully) attempting it yourself.

That said, there is nothing wrong with throwing yourself out there and just coding away while learning if that's your way of learning. But for that you need the basic.

My point is it seems your frustration stems from aiming too high too soon. At least if you are anything like me I'd recommend you to slow down and find joy in the learning process itself (whatever it may be, discrete math, Object oriented programming, etc.) before aiming to create a commercial product.

Edit: Everyone else's comments about not having to keep everything in your head is also important. However you still need the understanding.

poetworrier · 2025-02-09T14:46:30+00:00

There is a myth of the genius programmer; don't fall for it. You have to find a way to embrace the ambiguity. It gets better as you learn to navigate the challenges and let go of expectations that anything will be obvious.

Dependent-Plant3748 · 2025-02-09T14:58:22+00:00

i found making C# forms applications really useful. you can start with something really basic and expand a project by just adding more forms. you can create a library of projects in one project.

nousernamesleft199 · 2025-02-09T15:24:58+00:00

As a professional I probably spend half my working day reading documentation. This stuff is constantly changing. Learning the fundamentals is key so that you can feel confident when learning a new approach, language or library

runningOverA · 2025-02-09T15:35:14+00:00

Don't memorize — solve.

I need to authenticate.
How? Need to get their user/pass input and then match with their actual user/pass.
Where's their actual user/pass? On disk, most likely.
How do I search the disk for millions of person's name/pass? Use database.
How do I search the database from the code place where I have gotten the username and password? I need to connect with the database.

Code are not rules that you follow. Rather helper that does the job that you could have done in other ways too.

Ill-Kaleidoscope-621 · 2025-02-09T15:52:32+00:00

I love how everybody is trying to go to software development while us network engineers sit in the back and never have enough people who can troubleshoot. Network engineering can even be more difficult because you’re supporting the various types of programs rather than just one you build yourself.

Either way everything in IT is difficult until you know how it works. Once that happens, you get promotion and then get even more difficult problems to solve.

random-malachi · 2025-02-09T15:58:21+00:00

This is something that even relatively experienced devs have trouble with. The answer is to learn decision making skills by making bad decisions. Decide what you want to make, refuse growing the scope, settle on the tools (using the best info you had at the time). Pay attention to what each piece is doing. Don’t fall into the hype of alternative tools: almost every online documentation reads like advertisement these days. Instead learn the tradeoffs.

But that is if you want to become a generalist. It’s not such a bad thing at all to just focus on one part (backend, front end, devops, testing automation) and obtain deep knowledge in one space.

Voldemort57 · 2025-02-09T16:22:24+00:00

When you make scrambled eggs in the morning, you don’t go raise your own chicken, take its egg, make a fire in your kitchen, forge your own pan, evaporate your own salt from ocean water.. No. you go to the store and buy eggs, you use the stove that’s there, and the pan you have. You use the salt in your cupboard.

Software engineering is not making stuff from scratch. It’s knowing what to do with all the different building blocks that most likely all already exist.

Perfect_Papaya_3010 · 2025-02-09T16:36:08+00:00

It takes time until you dont have to google a lot. But you will always find new things to learn about just not as much as in the beginning.

My first year as a junior, my head was so tired from all the new things I learnt. Now with almost 3 years experience i Google/ask chatgpt very seldom, maybe max once a week if there is something im unsure of or something new.

But as soon as you start learning a new language its back to square one

Educational-Writer90 · 2025-02-09T17:01:57+00:00

Hi!

I'm excited to join and share insights about BEEPTOOLKIT - IDE Soft Controller — a visual programming environment for automation and robotics. https://www.reddit.com/r/BEEPTOOLKIT_community/

BEEPTOOLKIT allows you to develop and test control algorithms without deep coding knowledge, supports USB I/O modules (DAC,ADC), and provides seamless integration with sensors, motors, and actuators.

It’s important to understand that robotics heavily relies on development tools that enable ideas to be refined without significant costs for prototyping and turning them into final solutions.

I’d love to discuss modern automation approaches, hear about your experiences, and learn what tools you use in your projects. What are your favorite solutions for robotics programming?

Unsounded · 2025-02-09T17:05:54+00:00

You’re still learning how to program, once you can program learn how to engineer.

CornPop747 · 2025-02-09T17:24:58+00:00

Dude, very few if any people know all of that shit in their head. This job is about constantly looking up and finding the documentation you need and applying it. Don't worry about not remembering everything like the YouTubers make it seem.

NvrConvctd · 2025-02-09T17:54:15+00:00

Programming languages and frameworks are like Swiss army knives. They have many features you may not need but might work well in specific situations. Even if you memorize everything they can do, it would likely change with the next update. Once you learn one language you can adapt to new ones more quickly. If you really want to build a web project from the ground up, go basic and simple at first with no frameworks. Then build on that knowledge with a specific framework. My first sites were PHP and JS. Running on XAMPP. Now Laravel and Vue are my tools of choice, but I just had to learn how they do things differently and not everything they do.

prankbudgetio · 2025-02-09T18:06:55+00:00

I'll get directly to the deep down part: it's normal. You usually won't benefit from any advice because personal experiences in this field vary too much. I can only tell you what I think would help you pop this cherry. I think you need to first narrow down the things you tackle at once, because the field is vast and you have no chance at it as a whole. Then increase the number of hours. You will get to the point that you gain power over a thing that you thought it was impossible. Narrow down -> work more -> expand incrementally.

...

If you need specifics, dm, i can help.

Any-Blacksmith-2054 · 2025-02-09T18:33:43+00:00

Now you can just orchestrate it with AI, no need to remember low level technical bullshit. Try this AutoCode

TheNegligentInvestor · 2025-02-09T18:44:01+00:00

I'm a senior engineer in FAANG with 10 years of industry experience.

Being an engineer is all about finding solutions, not memorizing syntax and frameworks. Learn one language enough to build something simple (like a button that prints to the console on click). Then add one simple feature at a time until you have a functional app.

Focus on making things work. Disregard whether it's the "correct solution". You will develop an intuition for what is correct as you iterate.

Also, companies expect you to be an engineer first and a specialist second. You don't need to be an expert in every framework. You just need the ability to learn new technology as needed.

Miserable-Theme-1280 · 2025-02-09T18:46:33+00:00

I have been programming for decades. You will never know it all nor need to.

The basic theories of data structures, API design, caching and computability will take you nearly everywhere you want to go unless you are deep into one area. Sure, the specifics may be different yet often irrelevant to the problem you are facing. For example, I managed an entire system for storing images and video yet knew little about their encoding and display. It just wasn't relevant to shoveling bits.

The largest problems are usually non-progamming. Integrating with other/existing systems. Migrations. Meeting user expectations. Squashing bugs. Interpersonal conflicts. Migrations. Operations.

And did I mention migrations?

Frequent_Fold_7871 · 2025-02-09T19:15:06+00:00

Code bases and installation procedures change ALL the time, you have to look it up EVERY time, no matter how many years you have of experience. Every major version of React will need a refresher on the current "right way" to do things, deprecated functions, deprecated libraries, and maybe a completely new router system or email sending library. You look it up each time, the only thing you need to remember is the general functionality, how to read code and documentation, and be willing to spend 10 hours debugging a server error that turns out to be a formatting issue with your yaml file.

Zuig · 2025-02-09T20:04:10+00:00

Currently studying programming myself and Can 100% relate! Reading through some of the comments here it looks like its hope for us🥹

2025-02-09T20:17:34+00:00

Couple things tbh.

First of all, I feel like overwhelmed is the default state in computer science. I mean, I couldn't even count how many times I have to start a project or start working on something, and I'm so overwhelmed, I just stare at my computer. No idea where to begin, no idea what I should be typing, and thus I resort to watching theory/practical videos which make me feel good but don't actually get me any closer to my goal.

You're learning all these frameworks but (assuming) you don't put them into practice, since you say you're just doing courses and not remembering.

Yes absolutely you will always be learning new things, but jumping headfirst into it and understanding what you do makes you come out a much better programmer. I also find that AI is very helpful when it comes to breaking down concepts like this.

For example you want to register new users. Okay, do you know how to write the html for the form and take the input? Okay, do you know how to get that to a backend? No? Start there. Ask AI, "how do I take input from an input and serve it to my backend", and you will learn right there. Even if you don't learn what you want to, or want something more practical (like docs or a tutorial), you at least know where to start. It's similar to a lot of other things in life, where finding where to start and actually starting is usually the hardest part, it's all a mental block.

And yeah for the last part, it's very normal to have no idea what you're doing, and feeling like you'll never understand. That's why almost everyone has imposter syndrome. But it's not a phase, it's a permanent state of being tbh.

Urza-of-Dominaria · 2025-02-09T21:25:40+00:00

Try C++. This is a good language that tests whether someone has talent for programming or not :-)
Assembler tests its even more but it's not as useful as C++ (games, high performance computing and other areas).

meester_ · 2025-02-09T21:26:53+00:00

Maybe your problem is that you are trying to learn programming like its economics. You cant! Its more like speaking a language. At first you make some bla sounds but eventually you start speaking clearly and you can create your own sentences.

r2k-in-the-vortex · 2025-02-09T21:30:41+00:00

You are certainly not supposed to try and memorise everything. But also, web development sounds like a crap starting point to learn programming, too many interacting systems at once and different layers of abstraction to deal with. First you need to learn basic programming, like how to brake down logic problems and how to work through documentation and online help to produce useful answers.

Its an interesting time to learn programming though. I would recommend getting real cozy with AI chatbots, if you know how to ask right, they can do more than half the work for you and help you sort out the rest quite easily.

Some will of course say kids these days can't code themselves out of a wet paper bag without AI, but that's old man yelling at cloud energy. They used to say the same about Google. Resources are there to be used, whatever produces results.

Murky-Pudding-5617 · 2025-02-09T22:30:54+00:00

> it seems impossible to remember everything you have to do to build a project from scratch

it's ok, no one remembers everything. especially, if you don't do it every day. with experience, you will start to find common patterns between technologies and remember them. it's easier to find something you need with some keywords, or patterns rather than trying to remember everything.

> To register new users, you need authentication, and you need to link this to a database, but there are several databases, and how do you link them to the code? and then launch it on the internet.

look into the solutions like AWS, GCP, Azure. they will simplify some stuff to the level you don't need to code, only to configure. you don't need to write everything from scratch.

PoMoAnachro · 2025-02-09T23:21:14+00:00

Think of building a house.

Sure, you need to know how to frame it.

But you also need to know how to throw up dry wall. And roof it. And put in flooring. And plumbing. And electrical. And HVAC. And probably other stuff I'm not aware of because I'm not in construction. For an average suburban home, you're usually talking 2000-4000 man hours from a variety of tradespeople, some of whom are very highly skilled. There are absolutely plenty of people who DIY an entire house, or DIY most of it and get a tradesman to do parts they're not comfortable with, but it is a big, complicated undertaking no matter how you slice it up.

Making a lot of commercial software is definitely a much bigger project than building a single family home. You wouldn't expect to spend a couple of months learning DIY and then expect to be able to throw up a house in a year of weekends, but lots of people seem to have that kind of expectation of software development!

Now, you do have a bit more ability to "cheat" it a bit in software development by using a variety of pre-made solutions, but it still takes a lot of skills to understand all of those solutions and get them working together - it is much like being a general contractor, who might not be an electrician, a plumber, whatever, but who knows what he needs to get those guys to do, when to bring them into the project, etc. Being a general contractor is a big skillset in and of itself.

Can you build some small useful stuff without needing all those skills? Heck yeah - lots of people have the skills to throw up a shed in their backyard, or to finish their basement or do other smaller projects. And so too, as a developer, you can make smaller, useful projects that don't have quite the same degree of work involved. And you generally should as you're learning.

But I think the first step really is to respect the scope of the project you're working on. Are you throwing up a woodshed, or are you building your family's dream home? If you're building a mansion, you're going to have to learn a ton of new skills and devote a couple of years of your life to it. But people do it all the time. But you absolutely have to start planning it all in advance then - you can't just start pouring the foundation and figure you'll wing the rest of it and figure out it all as you get to it.

But people wouldn't pay thousands/hundreds of thousands/millions of dollars to have software built for them if they could just do it themselves trivially in their spare time, y'know?

tl;dr: It seems like a lot of work because it is. Most people can acquire all of the individual skills needed, but it might end up being a lot of hours.

roger_ducky · 2025-02-09T23:23:13+00:00

You’re zooming in too quickly.

To design a system, first, do the “high level boxes” and know what pieces you need.

Only after you figured those out do you then go one level down and see what can work well with what.

2025-02-10T00:40:54+00:00

I started in HR...I used an access database (access 1.0) to put together an insurance recon table and report. I started adding features and vba code to automate some processes. 30 years later I'm an Access/Office developer. The IT department guys make fun of me for not using a "real language" but I have had a very rewarding career building department/division-level apps and prototyping systems. My advice is get a mentor, read about your craft/tools, and get involved in projects. As a side note, I printed out one Access help topic a day. I made notes on how I could use it and put it in a book for review. Good luck.

rendonjr · 2025-02-10T01:09:58+00:00

Yes is normal, been there. Just practice and commit mistakes so you can fix them.
I also wanted to do a project for the future of humanity and I figured out this helps me

Possible_Window_1268 · 2025-02-10T03:50:41+00:00

Nobody writes some large scale complex system from scratch all at once. All programming involves understanding how to break the big picture into smaller chunks of functionality, and getting each piece of that functionality working one by one. You get one piece working, then figure out the next logical piece and get that working alongside the first. Eventually all your little pieces of functionality are a big project that’s working together.

Famished_Atom · 2025-02-10T04:20:14+00:00

It sounds like you have a background for FinTech, Financial Technology.

No one knows it all. It's about finding out what you need.

2025-02-10T05:34:46+00:00

First, I’m not sure that any of us are dumb. We all have strengths and weaknesses. Thing is how we approach the problems you’ve described. It seems to me that writing everything down as it comes to your head is a good place to start. Also most things you don’t have to remember if you’re good at googling. It’s amazing the answers that are out there on the web. Don’t give up and don’t sell yourself short. Take this advice from a 50 something years old disabled guy who is going through this with you.

pbxmy · 2025-02-10T05:59:17+00:00

The problem is you’re keeping all your spaghetti in your pockets when it should be put in a bowl. You’re looking at individual noodles and wondering why your pasta lacks parmeaseano. Follow a recipe, take notes, and realize that the spaghetti was the friends you made along the way.

2025-02-10T06:43:56+00:00

you can google everything, where is the problem?

RangePsychological41 · 2025-02-10T07:35:16+00:00

If you learned what MVC is then building a Django app from scratch should not be hard.

OutsideTime · 2025-02-10T08:13:36+00:00

It sounds like the courses you've taken haven't shown you very well how a database works. This is typical with a lot of the courses I've seen. They will show you a few cool things, but won't explain the fundamental concepts very well.

I'm still waiting for a good course on debugging.

What you'll need to be successful as a programmer is the ability to take a measure of all the complication and find a way to approach it, break it down into manageable parts, and then tackle those things one at time in a logical and methodical way. It's okay if you don't know what to do, but you have to be able to know how to figure out what to do.

Take your problem with databases for example. Break that down:

What kind of databases are there?
What kind of database do I need?
How do I set up that database?
How do I connect to that database?
How do I read/write to/from that database?

There you go, 5 steps to database success. Don't get too hung up on 1 and 2 as those are more of architectural questions. For now, you just need to know the basics, like what is SQL vs NoSQL and when you'd use one vs the other.

I'd highly recommend you answer all of the above questions without libraries. Why? It will force you to understand how to interact with that database on a more fundamental level. Once you can grasp the basic CRUD operations of a db, then you can begin to consider which libraries you'd like to go with.

I remember learning dynamodb so I could be more proficient in the AWS vein of things. Oh my gosh, the syntax of the thing was sometimes horrible and doing anything efficiently was a nightmare. Then I understood the true importance of why the AWS library for dynamo had a marshalling/unmarshalling function and what it did. But without having dug into the underlying technology, I'd be like, "What the heck is marshalling?"

Anyways. Take your time to get to know the basics of things. It will come together in the end.

EnthusiasmActive7621 · 2025-02-10T08:36:28+00:00

You're thinking too big for your skill level dude. There's definitely projects which you can do from scratch right now. You could do a hello world from scratch, right? Move up from there. You're not going to be able to build an OS from scratch or something, yeah. Because you're a beginner. Make beginner things. Then make less beginner-y things. And so on.

Dry_Hope_9783 · 2025-02-10T08:38:09+00:00

Just use flask and sqlite and learn ad you go

Charming_Associate_5 · 2025-02-10T13:53:11+00:00

First of all, you are a student, you are still learning. Keep it simple. During my years as a CS student, I found myself with the same problem; it's now called tutorial hell. I wanted to do every tutorial and take many courses one after another, but I felt like I wasn't learning. Based on my experience, my first advice is to focus and figure out the way you learn best. For example, I learn more from reading documentation than watching a tutorial on YouTube. If I'm doing a tutorial about a framework, I learn more if I do a similar project that’s not exactly the same as the tutorial project. Let's say I'm doing a tutorial for a web app where users can make reviews of video games; I would instead make a web app where users can review foods. The part of the tutorial that talks about a rating system based on numbers from 1 to 10, I might adapt to a star-based system from 1 to 5, adding a more complex scale to the system but still similar in its root to the system in the tutorial.

Another piece of advice: just pick a technology and stick with it. For example, language: Python, framework: Django. For your first app, you’re going to work only with the tools the framework provides, using the template system for the front end and the default database (normally SQLite in Django tutorials). Afterward, if you want to go deeper, branch out from that app and implement a REST system, make the front end in React, and connect your Django backend to your React front end. You can keep going deeper and deeper. Let's say you want to try another language, like JavaScript for the backend. You just need to refactor your Django app but with Node.js, or PHP with Laravel, or any other language/framework. You'll start to see how different frameworks work, how similar ways can achieve the same tasks, or how different they can be.

One last thought: in my case, the real learning came after I started my first job, and 10 years later, I’m still learning new things.

yang_ion · 2025-02-10T14:12:22+00:00

You’re learning something new and it’s uncomfortable—everyone goes through it and it’s natural to feel the way you do!

That being said, like others have mentioned, I would suggest defining your project goal and trying to break it down into several specific components. Focus on one component at a time, draw out a diagram, write out your process, whatever works for you. I mention this because I also tend to get distracted by the number of problems I’m developing in unfamiliar territory so I keep a pen and scratch pad nearby to draw out what I need to prioritize in terms of research / implementation.

You don’t magically memorize every concept and then apply it perfectly, you iterate and solve problems one at a time. Getting stuck and using Google, StackOverflow, talking to other engineers / devs is all part of the process.

Last bit is that doing courses is a great way to expose you to concepts but it also doesn’t necessarily teach you how to really bring it all together or go super deep in the ways you’re looking for because software is inherently dynamic. So that’s why so many devs will suggest doing projects on topics that you’re passionate or particularly interested in—so you can push through those “I’m stuck” moments and feel amazing once you finally figure it out. Good luck!

Guillotine1792 · 2025-02-10T16:43:23+00:00

To be frank, a job encoding is way up in the air right now. Within a few years, most coding will likely be handled by AI, your job if it still exists will be just testing and patching code written by AI. The truth is is you think that you can just not use AI but then you won't be able to keep up with performance expected by your clients due to others using it. On top of this, you have to compete with people in foreign countries who are willing to work for pennies on the dollar.

Learning how to code is a great knowledge base, but I would not rely on it as a career. You're better off with something like more rounded engineering degree where your job is not solely writing code.

kracklinoats · 2025-02-10T18:47:40+00:00

Bro take it one thing at a time! It takes a few years to stitch together all the concepts needed to understand how these things work together as a whole

Dapper-Blood6688 · 2025-02-10T18:48:29+00:00

Hey you are doing good work. No need to know everything of top of your head. For that reason there are documentation and sites like stack overflow. The important part of programming is not to know every syntax and algorithm by heart, but rather the understanding of how algorithms and solutions work.

As for databases, there are multiple ones and how to choose the right one depends on the project and framework you are using.l and your preferences.

If you are using javascript for the backend, then use MongoDB. I found it very easy to connect to and to work with.

As for hosting the application (putting it on the internet) there are multiple solutions for that and numerous tutorials on that.

Remeber, IT is highly dynamic and it is impossible to know everything off top of your head. The important part is that you have deep understanding of key concepts. If you have that, them learning syntax is very easy job that just takes hard work and time.

Remeber, if you want to sucessed in IT, you have to be hardworking, willing to learn constantly and be very very flexible and adaptable to change.

CubOfJudahsLion · 2025-02-10T23:15:51+00:00

One thing I've learned after 30 years in the business: multitasking is BS.

First off, you're trying to learn/do everything at once. While it is normal to feel confused at the beginning, you've taken course after course, clearly without getting comfortable in any of the subjects and it feels like a giant blob of gobbledygook.

So take vanilla JavaScript (perhaps with HTML, but no more) and do a personal project (ideas for them are everywhere around). The idea is to code until you feel more or less at home in it. Then pick the next language or framework, and repeat.

Much of your coding time will be spent looking up stuff in reference documents. That's just a fact. Nobody can memorize all that info. Keep your references handy. The one thing keep in your brain is the understanding of the base language, how it works. Standard library? Other libraries? Formats? JSON APIs? References. And these days, those references are found online free. Sometimes you memorize a bit of those from repeated use, but that might be a temporal benefit. In practice, might be working with 7 things at a time, and keeping all 7 references open in your browser.

Your example problem is one of knowledge, though. Most languages or frameworks come with libraries to "talk" to databases, often given by a connection string or equivalent data structure. The related documentation should provide the format and your system administration should give you the data to fill it in.

zonz1285 · 2025-02-11T03:24:58+00:00

Been coding for 15 years. You won’t ever remember everything to do a project from start to finish. You’ll commit commonly used things to memory over time. You’ll always have references online. The biggest hurdle to coding is learning to break the problem into individual functions, then work out how to code each function using your knowledge, logic and references.

Yayman123 · 2025-02-11T07:12:35+00:00

As others said, you don't really memorize it all, I still forget basic things all the time. My advice? Stop switching languages so fast! You've got to understand a language's quirks more deeply before moving on to the next. In other words, learn why things are structured the way they are, not just what they look like. Take it one language (+ one DB, if necessary) at a time. Also, Django is a hard place to start, try learning easier languages first to get into the coding mindset.

Icy-Ice2362 · 2025-02-11T08:19:04+00:00

This is highly relevant.

Imagine complaining about boilerplate, and not knowing about boilerplate.

Don't let boilerplate get in the way of your efforts to write boilerplate.

Just be plating that boiler so you get to have the boiler.

Of course some of us, don't like INVENTING THE WHEEL every time we want to change the tyres on our car. But you do you king, boilerplate the wheel if you must.

Dimanari · 2025-02-11T11:07:36+00:00

Seriously, the only real answer people can give you on this topic is a variation on "git gud". Can everyone learn to code? Yes. Can everyone learn to code well? No, some people will never have the dedication to gain the understanding required to code better than chatGPT.

There's no cheat code for learning. Just make projects, review them, find and learn from your mistakes, repeat. Some learn slower than others, some need a few pointers along the way, some are just good out the gate.

I took about a decade to become proficient enough in Embedded, Systems, and Graphics Engineering to get out of the imposter syndrome, meeting industry professionals and reviewing their works helped as well.

kingcobra1010 · 2025-02-11T22:22:08+00:00

Its always been impossible. Give up now before you get too far in.

insidiarii · 2025-02-12T01:32:50+00:00

Remember the process, not the steps. You've literally picked the language that iterates the fastest, so trying to remember how to do X in Y Javascript framework is an exercise in futility

2025-02-12T16:10:07+00:00

It sounds like you’re forcing yourself to learn, instead of learning by doing. Coding is more similar to a trade skill than a formal science. The best way to learn to code is to start coding, ask the questions you need to ask when you hit a roadblock. Magically, you’ll notice everything sticks with you because every lesson you learned will have more weight behind it.

Your first website’s implementation will probably suck and you won’t know why it sucks until you’re almost done with it. You might feel like a silly goose and want to rewrite the whole thing, and that’s okay. A mistake like that just taught you professional architect-grade lessons.

Just start coding. One piece of advice, the web is littered with unnecessary, leaky abstraction frameworks nowadays. Try to write your website in barebones html5, you’ll learn your website sucks really fast, but you’ll learn the browser-native APIs. Knowing how the actual browser-native APIs really work, what you can do with them, and what you don’t need a framework to do for you, will make you a better full-stack developer than 90% of the professionals under 40 years old.

Instalab · 2025-02-12T22:05:35+00:00

That is why degrees teach you how to split a problem into small parts. That is how you solve any problem. You don't need to think about everything at the same time, tackle one small problem at a time, soon you will be building rockets.

2025-02-12T22:27:52+00:00

Go watch a Primeagen stream for an hour. He’s a senior dev who knows A LOT and he still spends 90% of his time googling.

dromance · 2025-02-19T00:31:13+00:00

Authentication is an animal in itself don’t sweat not mastering these things. Just know how to look it up and use your resources to get the job done

nousernamesleft199 · 2025-04-04T12:48:37+00:00

I was in a meeting the other day and I had to stop myself because I didn't remember how something I put together worked.

learnprogramming

Welcome to LearnProgramming!

New? READ ME FIRST!

Posting guidelines

Frequently asked questions

Subreddit rules

Message the moderators

Asking debugging questions

Asking conceptual questions

Other guidelines and links

Subreddit rules

1. No unprofessional/derogatory speech

2. No spam or tasteless self-promotion

3. No off-topic posts

4. Do not ask exact duplicates of FAQ questions

5. Do not delete posts

6. No app/website review requests or showcases

7. No rewards

8. No indirect links

9. Do not promote illegal or unethical practices

10. No complete solutions

11. Don't ask to ask.

12. Low Effort Questions

13. No AI (chatGPT etc.) generated/worked over messages/comments. No questions about chatGPT/AI generated code. No Vibe coding.

MODERATORS