This is Why Programming Is Hard For you
Vložit
- čas přidán 25. 03. 2024
- To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/TheCodingSloth . You’ll also get 20% off an annual premium subscription.
Programming is hard, but you can do it.
This video was sponsored by Brilliant
// NEWSLETTER //
Sloth Bytes: slothbytes.beehiiv.com/subscribe
// BUSINESS INQUIRIES //
Email me: thecodingsloth88@gmail.com
// SOCIALS //
Twitter: / thecodingsloth1
TikTok: / thecodingsloth
Discord: / discord
If you'd like to support me I'd appreciate if you get a membership for the channel so I can give at least give you exclusive perks for the support
/ @thecodingsloth
To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/TheCodingSloth . You’ll also get 20% off an annual premium subscription.
I hope this video helped any of you who felt stuck when learning to program. Better start thinking like a programmer and not rely on tutorials.
EDIT: I LOVE PRIMES CONTENT. I USED HIS IMAGES FOR MEMES/ENTERTAINMENT ONLY NO HATE
Great video as always, I love them.
Programming is the most counterintuitive thing ever. I normally pick up on things pretty fast; but when entering the programming world you have to be IN THE KNOW to understand every phrase.
Analogy: When your just starting math you learn that math is done with numbers. Perhaps your learn to divide, add, subtract etc. But once there’s random letters and things in there that’s when you **reference points** dwindle. Example: 5(5)=x(squared). Show this to anybody that’s only learned the basic fundamentals of math and they’ll look at it and try to solve it only using previous things they’ve learned. Therefore: you need to context of how these things operate.
All learning is built on a foundation of prior knowledge.
Dude.. Computers are humbling. Everyday I question my intellect because of them. Everyday I’m left with a headache.
Programming sucks.
I can tell you this one thing that you were wrong about.
Programming is NOT HARD. I can guarantee that it is not.
You know what is?
It's the political battles in every single company you work in.
They will spend their their time to argue about what features they should add/remove, then remake the design like...a zillion times.
Then, they're gonna test your "patience" by seeing how you comply with their st**** demands.
Those are the things that everybody will encounter in every company they work for.
Other than that, I agree, you need to stop watching tutorials.
isn't brilliant just one of among other app that will end up being a tutorial hell? I'd rather advertise something else if i were you
@@aru6575 people say it's interactive learning, maybe when you interact with environment you'll learn better? maybe?
I stopped watching tutorials when I realized I could read the documents by my self and honestly speaking. Reading docs is so much better than watching tutorials.
same here, on both points :)
I haven't searched for tutorials in a long time, when I want to know something I search then go the the official docs, I learn more that way sometimes I get carried away by other functions that might solve a future problem or make my code writing better.
It depends on the quality of the doc, the videos and you. I learned more about Authentication/Authorisation with Identity management watching a 10 min Nick Chapsas video than reading plenty of doc about the subject. I use also CZcams tutorials to be aware of what is done outside of the languages/framework I use.
@@enubiakadaniel8132Im a beginner in python, what do you mean by docs?
Remember: ctrl+f
Realistically speaking
I built a full stack website for a local client the website was simple I used bootstrap for the UI and node for backend with MongoDB for storage.
The project was relatively simple but i remember just how frustrated and stressed I was when I was coding it. Yelling back and forth at ChatGPT. Trying to scrape through stack overflow.
Today (6 months later) i opened the code again and I was blown away just how simple it was.
The point being that: what you find hard today wouldn't be as hard in the future, the point is to keep going and keep learning.
Cause remember: the more you F**k around the more you find out.
In essence Programmers should fvck around More. Only your imagination holds you back.
hell yeah man thank you ❤️❤️❤️
Sorry what?
Well said 😂!
Very true. Code bases I agonized over in the past now seem trivial.
im so cooked
same here
I'm getting out of this stuff while I'm ahead, it's just too frustrating for me.
@@Cheesehead302 :
weakness @@Cheesehead302
@@senzmaki4890 yeah how are puzzles too much for you
One of the hardest parts of coding for me is that often you can't see all the tools at tools at your disposal.
When I'm doing electrical work & get stumped I can go over to my toolbox, open it up & just have a poke around to see if there's a tool or combination of tools that might do the job or at least inspire the solution.
With digital tools its much harder to look at all your options.
I think you really hit the nail on the head with my problem with this stuff. With various parts of my life I've been so conditioned to having a set of limitations and tools that do very specific tasks, no more no less. With this stuff there is page after page of potential tools, and when the time arises that you need one, you don't even know it exists.
This is something I genuinely struggle with too. I almost think it might be worth having a giant print out of every single tool of a language, but my walls aren't big enough
literally this. i don’t feel lost if i use something like scratch to code but when i look at the actual coding language itself idek where to begin because i don’t know what i can actually do
As a HTML engineer, I disagree
You will never know why this comment has so many negative replies 🙃😅🤣😂
@@its_past_here All of the rich software devs turned everything devs that can make an actual product lmao. Go learn UI/UX and you'll understand why you're broke.
As a plumber, I also disagree
As a CSS martial artist, i agree
so tru
This year i landed a great web developer position starting at $30/hour full time. I love it because all the hours i am putting in is making my programming skills WAY better by working 8 hours a day writing and testing and debugging and getting feedback. Its been a great experience and praise the Lord i got this job.
Good for you, most of us are suffering. But hey, keep boasting.
@@TheSCPStudio I was there too man. I just landed it 4 weeks ago. A huge tip is to apply to local places. That's what helped me.
@@TheSCPStudio this is why you’re suffering. Fix your nasty paradigm and learn how to be happy for others.
He is risen!
@@TheSCPStudio Don't be a crab in a bucket
I thought I was the only person in the world who kept saying to myself "Maybe this isn't for me" every time I struggled to work out a problem or thinking why isn't this concept sinking in. I can't stop thinking about a coding problem when I have one and I'm so mentally exhausted after I finally crack it that I feel like I've just been to war. Perseverance is definitely necessary when coding in my experience, as is having fun solving problems. Spent many nights screaming at my monitor, but the feeling you get when you finally solve the problem is amazing. Very funny video btw.
I'm currently stuck in the same boat, I feel like everyone breezes through these simple concepts that I just cant fathom at the moment. Any advice?
@@TheMelonbros123 Everyone learns concepts at different rates, there are things that you may breeze through that others may struggle with. My advice would be to make sure you read the official documentation (can be kinda geeky), look at other people's code which incorporates the concept you're struggling with to see how they're utilizing the concept and play around with the concept yourself to see how it behaves. Everyone says it but it's true, Practice and Perseverance.
That's the satisfaction of this job when you see the thing you have been building for a long time finally working. And what you say about code isn't necessarily bad. I always catch myself thinking about projects or about code I want to write or wrote
I've been there even though I had written tons of projects. Doing projects you're motivated to do is a great way to avoid frustration or burnout imo. Doing projects just to do them is not a good approach, find something that interests you and give yourself plenty of breaks, and give yourself the benefit of doubt. Just my 2 cents lol
idk man im in cs at uni and i feel like this isnt for me, Ive never liked coding too much and always been average at it
8 minutes in I realize I’m just watching a really well crafted ad for Brilliant. You don’t need tutorials, you need Brilliant. smh.
46 upvotes? really? people can't be that dumb. In case people are that dumb, no it's not a Brilliant ad because dozens of people say the same way without the segue.
@@meltygear5955realizing that it's not just a brilliant ad would require logical thinking and the lack of it is the reason many of them are here in the first place. Unless, of course, person is being sarcastic, but I wouldn't be surprised if he genuinely believes what he says
@@meltygear5955r/woosh
@@Metall1st3 it is actually a really well crafted ad, but that doesnt change anything on the fact that what he says is true
@@meltygear5955 r/ihavereddit
Something I'd like to add is to read up on books on software development like Pragmatic Programmer, Martin Fowler's books, etc. It helps with the foundation of your skills
Well, as I am currently in College (University), I think this is one of the most important lessons.
I am really enjoying the books from "No Starch Press".
Oh come on, how much can you over engineer a detonator?
100% agree. When looking back at university, the one thing I'd like to change is reading more books, and rely less on professor provided material. Another thing is doing more networking, vitamin B really helps a ton when searching a new employer.
Up to and including Think Like a Programmer because it helps with problem solving which is what programming ultimately is.
If the author of the *The Coding Sloth* won't mind, a few timestamps...)
0:00 - 6:11 the definition of the problem _Why Programming Is Hard For you_
Tips by *The Coding Sloth* :
6:12 Tip 1: Break down problems
8:36 Tip 2: Project - based learning
9:05 Tip 3: The Feynman technique
9:43 Tip 4: Embrace failure as a learning tool. Fail stands for: First Attempt In Learning
9:57 Tip 5: Practice Regularly and for a long period of time
10:17 Tip 6: Stop comparing yourself to others
Thank you, *The Coding Sloth* , for your doings!!! Great Job!!! 🙏🙏🙏🙏
I couldn't agree more, people think its just another language, how hard can it be, but in reality its much more than that because copying a script will never be the same as writing one. To write one, you must know exactly what you're doing.
i agree, i dont see why people would spread hate on something that obviously isnt meant for them
Because of school just teach you how to copy and alot of these work shops are the same. They just teach you how to copy work.
I felt like i wasted my money because i didnt really learn shit that would help me get a job in college. My college suck ass with the math and sciences but its was all i could afford. But id didnt know it sucked until after i graduated
@@mesekkai im a first year in college and i disagree. it depends on a lot of factors and college isnt for everyone. for me, i just focus half the time on passing minimum and the other half on actually learning stuff on my own for personal projects later. it isnt that bad imo. but then again, im a tech major
@@mesekkai youre comment is really toxic and does more damage than good. I went back to school after already getting my bachelors because alot of these content creators for CS are just as bad as your example. When i went back to school for CS i learned so much i wouldnt have gotten from online diy learning. May not be for everyone but ive already learned more in 1 year at community college than 4 years browsing the internet for actual learning that didnt involved the same cookie cutter learning plans i see constantly with these type of youtube channels
@@seaweed428 thats how it should be honestly. I started working on my own personal projects as well because our professor told us taking the courses and getting a degree is barely anything anymore. Make your projects we worked on speak for themselves. Thats why you see all over the internet, "I did 4 years of CS and graduated but cant get a job." then you realize they never did anything outside of their education.
Great breakdown, failing and making errors doing real things is often the best teacher
Yeah, if you don't have a good textbook or manual... It is all about five-minute tutorials and 50-step-by-step-recipes-how-to-do-something-very-specific books. There is a real crisis in computer programming teaching literature. And no, online documentation is no teaching aid. There is no system to it, no linear flow that would naturally and easily take you from basic to expert.
Pretty much every job ever. Life is one problem after another. Hopefully we'll have what we need to solve it and getting paid to do it.
@@aceofswords1725Yea, it's not lineal, but if you need only a new piece of info (new component in Unity, for example, idk), then it will be good (if the doc has a good amount of info)
As a programmer, I love Zachtronics games because they test your logical thinking AND coding skills, particularly Shenzhen I/O. It's basically a simulation of building and programming microcontrollers where your physical space is limited, you can only use a small number of assembly-like instructions and you often have to think about how the blocks are running in parallel. Using the average example listed, there is a task that requires you to keep a running average of the last X values, you are limited to integers between -999 and 999 and you have no division instruction.
This video helped and freed me, definitely right on time. Thank you so much!!!! I'm implementing the steps like coding for an hour, teaching myself and simplifying. Thanks again, this rocks!
I learnt programming in the 80s. But at first I did not know that I am learning programming. I was interested in books about math and logic and I really liked to solve logical problems. Then I read about computers and I remember, how I basically asked people things like: "How you can make computer to do this?" and then I met my friend's father, who was professor of computer science and he gave me some more books about computers, algorithms and math to study. And then I've got to use real computer for the first time. It was ZX Spectrum+2 with Z80 CPU and 128K of RAM. It was very slow and had Basic in its ROM and then I have learned assembly, because that was the only way, how to get at least some speed from it. Later, I learned more languages and computers got much better too.
I work as software developer more than 25 years now and I am always learning new things. Computers, languages, and everything else have changed a lot in the past 40 years, but one thing remains the same: The problem solving. Analyzing the problem, breaking it down into blocks, functions and features. Deciding, how to address each of the problems and how to tie them back together later.
Programing is not that difficult, if you approach it from the right side.
Well put man, well put. Im a jr javascript dev and i studied JS like crazy and it did not prepare me for the logical thinking and how to use the things i learned to solve issues. Learned that the hard way.
This is a very valuable video for me. I have seen a lot of videos saying this but this video really open my eyes with its detailed explanation. Thank you, the coding sloth.
I believe i am well on my way to becoming a competent programmer. I feel like what really has helped is just doing projects that inspire me, often times things that solve a problem i have. I just wish i could land a job, feel like that is even harder than learning to program.
Valid points! And shout out to my fellow Web Dev Cody for his cameo! Haha.
I liked how you structured your points for the UNDERSTANDING of the coding and programming.
Great timing needed this right now ❤
This is really reassuring because I’m trying to learn JS and have a good understanding of troubleshooting and solving “the puzzle” of getting something how I want it. I started by writing down what every line of code did
Bro, your cooking analogy is awesome! Subbed.
I needed this. Thank you 🙏🏿
Funnily enough, this is what I was explaining yesterday to a first year student as a senior. I told him that it is more about solving problems and making practical solutions and less about the nemorizing the concepts.
As a software student, who feel lost and nearly give up on my major, thank you very much for this video
00:58
Man, I didn't keep watching your video when I saw this clip, I literally jumped into this awesome website and started making for my current project
It's awesome, and I'll watch the wep dev Cody video as well
Brilliant video! Thanks! Absolutely love your sense of humor haha
Thank you! I was just asking myself about ”the mindset” yesterday because I feel like I’m missing that
Love the video, thanks for creating it
stock videos with that leet speech bubbles are precious , make a series out of it !
Just started my journey with coding! Great info!
loved your edit man😂
I had completely given up on learning gamedev because it was so overwhelming, and I thought it just wasn't for me. But this has made me realize it is overwhelming for everyone. So I guess I'll keep going. Thank you.
Thanks, thats nice!🥰
Nice video man. Thanks for the explanation 🔥
Your videos gives me answers to the questions I have been wondering for too long.. it clears my confusion.. thank u so much ❤❤❤
This video deserves way more views. Sharing it with all my friends!
I think you are the best programming channel here in yt. Thanks a lot
thx for the video
I'm dealing with these issues as an average programmer right now, so from the bottom of my heart, thank you for making this video and for making me feel better 💚
Watching this while I am stuck at work with a problem and I feel stupid and thinking how my other developpers friends are just leagues ahead of me and how undeserving of the job I have, so yeah, it is hard
the best way to get out of tutorial hell imo is to find smaller and easier ideas that you want to do and that you think you can do and do them on your own. it also helps to do something like game modding or javascript, something where you dont have to worry about compilation, or making state control, or having to worry about rendering things on your own, etc. it helps massively simplify things so you can get just the basics of working through logic and only logic.
Thank you for this, especially that last part
Oh. You did give me an idea though regarding the learning aspect of problem solving. Thanks.
As someone who’s programming for 40 years now. I can say that I don’t know the syntax of most languages that I use. Because I use so many and they mangle in my brain. C and 6502 assembly I know by rote because I did if so much. The rest I just shamelessly lookup. Because I understand the concept of something I need to do and Google is great aid to find that. And learning to write without frameworks in the 80s on bare metal, really teaches you to think in a way most developers don’t anymore. I bet most developers don’t know off the cuff how to turn lowercase into uppercase or vice versa with only bit wise operations. Yet the ascii character set was designed for that! Or print a number to the screen, writing that conversion. Especially if you don’t have a division with remainder instruction.
If you want to understand programming fast, and actually love it,learn discrete math and DSA, programming will never be a problem, this is actually the foundation and meaning of a computer science degree.
What is DSA?
Data Structures and Algorithms
@@hoangcon4811 Ah, thank you, wasn't familiar with this abbreviation
Bro in my discrete math we ain't learning shit just like Jenn diagrams and what a set is and some weird arrows 😭
Venn? Genuinely checking.
loved this video! thank you
That was beautiful.. thank you, I've subscribed
The hardest thing for me to actually grasp at the moment is focusing too much on trying to get it right. Its like I spend hours on a task, then I hit a wall, can't figure out how to solve the problem I need to solve. I'll hit my head against the wall for hours wondering why I can't figure out such a simple task. Then I go play some games, or go to bed, and the next day, I look at the same code and the solution comes to me, then I might spend another hour or 2 implementing it. I guess I'm saying, its hard to know when to take a break, take a step back, refresh your mind. Maybe watch some CZcams videos on programming to see if something jumps out at you.
Even though 30 minutes seems like a very short block of time, I still think that it is a good amount of time. At least it helps you build consistency, something important when it comes to master a skill.
Thanks for your videos. They really help me.
been there, done that.. my advice, learn and understanding the concept, practice, and learn how to connect the dot.. lastly, never give up
The toxic environment was what threw me off. I know toxicity is in every field, but tech people can be truly built different.
Same, how am I supposed to get better with all this negativity around me, pulling me down.
@@icmedia6314 I wish you the best! I did pivot more to the business side to decrease the occurrences.
Where? There is no field like programming where everything is opensource and documented..
In my experience, it's not just programming. No pun intended when I say tech guys have a bug up their ass. I know guys who are into networking and configuration and they're the same way.. everything you say within a tech centric conversation will be put under a microscope and pessimistically analyzed
Toxicity and elitism in niche, difficult to learn/adopt tech centered communities? Couldn't be.
I went into a discord asking about how a tool worked because my hack job 30 min solution to creating a discord plugin didn't scale and reverse engineering discord from web pack ain't fun. I asked a question about my initial approach and got roasted for it. Hard. I laughed at how hard they flamed me for my approach. It's been years since that last happened. The best part was my question didn't even get answered. (I assumed the general answer was no you can't do that) Thankfully they did inform me somebody was already working on what I wanted so I copied that and built from there. Still took a solid ~6 hours to get things fully working due to my laughable typescript knowledge to the point where ai tools didn't make a meaningful difference in speeding things up. It's been 6 months and it appears there is so little demand for it, the plugin still hasn't been fixed.
Let me tell you, I would have probably spent a solid 50 hours and another 4 attempts before I could have come up with the solution I copied. I straight up missed 2 important things during my intense Ctrl + Shift + f searching. It's always a humbling experience learning you know nothing.
This really helped me. And also helped me feel better. Also glad you talk about imposter syndrome and failure because I feel like not many coders and programmers talk about itnat all.
Thank you!
So close to 100k! Just found this channel and i love it
been in tutorial hell my whole development journey. I’m suffering.
IMO the difficulty comes from the size of real-world apps: it's difficult to know where to jump in, or how to isolate only the parts you care about. A little app that you've written from the ground up - easy
Using cooking as an example is an interesting way of comparing them. In one example you replace the sugar with a different sweetener because you know sugar is a sweetener. By that logic it makes it would make sense that if you wanted to replace the title of something without using the data type you would just use a different method for a title. That doesn't seem like problem-solving to me that just seems like using the knowledge that you have through finding alternate ways of doing things you already know. Is it seems similar to Googling what are different sweeteners. Instead it's Googling what are different ways to code a title.
I used voice to speech and I'm also a beginner and I'm pretty sure isn't a data type
I experienced this (2:40) during University work with data structures and algorithms. We were given large complex sets of data and had to create our own sorting algorithms without using any imported libraries and extremely limited built in libraries. It was seriously tough, but I think it taught us a lot.
I've been watching prime for years now and I've never gotten the "buy my course and you'll be rich" bullshit from him, He's regularly streamed his content for free and it was very good quality. The message I've taken from prime is that
- programming is hard, and you have to work hard
- even if your at rock bottom in life you can turn your life around and succeed.
- getting a job in fang isn't always nice
- don't listen to twitter trends
- we're all dumb, so don't overcomplicate things
- be kind to people and give them grace
Seems a bit unfair to make him the face of the shitty side of programming. especially putting him beside techlead.
lol that's my fault for that and it wasn't my intention. It was intended solely for memes/entertainment. I love prime's content
He was certainly cited as someone with expertise
I think it's just the curse of the streamer. No matter how much he emphasizes how hard it is the format itself makes people think it'll be easy
I am literally sitting at a new job pouring over the database model to try and find out how to implement some functionality to delete some data when some related data gets deleted, but over like 10 joins.
Understanding a domain is so much harder than just typing some code.
Anyways, time to stop procrastinating and hit my head at the wall of the domain model some more.
I'm seven months into my dev job and I still don't understand the the code base.
@@chaserightnowdude 😂😂😂😂😂 i felt that deep in my heart
Yes I get that. Lately I've been getting better at solving coding problems. After 4 yrs of playing around in python. Got to make some bigger projects. The stock scanner I made this time solved the problem of finding stocks at the right time.
Great video! A lot of great analogies. Definitely that tip 1 is solid, the best programmers are masters of complexity management. The only way i know to get better at that is to keep trying
As someone who knows about 8 languages and can pretty much pick up any new language if I want to in a couple of days, I think programming is only hard until you understand the concept. You need to realise program itself is nothing but its a way you're interacting with the operating system which in turn interact with the cpu. So every statement you write, every loop, every function, they all goes back to talk with the machine. Now if you stop learning a language for the sake of learning and instead think how each command you write is interacting with the system, you'll feel a natural flow of logic, the funny thing is that you only need to be good in 1 programming language (preferably any object-oriented language) and every other language is almost same with some syntax difference. There might be some special features in each language but over the time, you understand that most of the language work in similar fashion and some special feature is only introduced to ease up/mess up developer's life. That being said, it's best to learn language with practical projects so you can test and realise what you did wrong or could be written in better ways.
Ok, how long does it take you to pick up Prolog?
A dude still stuck in oriented, programming and inheritance of C++ since 2 months 🙋🏻♀️
First yr of compsci degree. I will say, learning the simple stuff like arrays, loops, if/else, exceptions, objects and classes. Is easy. But applying it to a scenario is wayyyy harder. You can’t just write code. You have to design the system first. Then it gets even worse, with big O, hashing, linked list etc. it feels like you’re just constantly confused and you just learn stuff on the spot.
Very true. I remember bashing my head against the wall trying to figure out the logic to a homework question like 20 years ago. It was a modified binary search for reference and it felt impossible. 10 tries and probably 15 hours later and still couldn't do it.
Forgot about it and was reading a comment on a forum and for some reason my brain connected the dots and I went back to the problem. 3 lines of code later I felt like the biggest idiot that had ever lived.
Everything is "easy" when you know how to do it. It's absurdly difficult if not outright impossible when you don't. Building the foundation to ensure problems don't feel impossible is very hard and takes hundreds if not thousands of hours of practice. No exceptions. People who seem to pick it up in a fraction of the time generally speaking got practice doing something similar somewhere else for extended periods of time I've found. I've yet to run into someone who is an exception to this. I'm certain they exist as people will point out but I haven't run into them.
Thank you for this, I just finished the Google analyst course like today, and I felt like I barely retained much myself on SQL and R and felt stupid relying on help from good people on the internet that help me point out where I went wrong. But seeing that it’s part of the process gives me more confidence in failing and not to get too bogged down on it. I am a big believer in projects and portfolios as practice and evidencing for potential employers and I have my first project up on kaggle done in R, just wished I knew exactly every single line of code did lol. Next project I’ll focus more on SQL and go through the (e)motions on that.
The planning stage cannot be overstated. Make a block diagram of everything your program needs to do then go about building it. Also keep your mind open to possible "better ways" to do things.
Bro i code so slowwww. Whenever i find time and actually focus i end up barely making any progress on a project
The key is to never get comfortable, you have to embrace rapid change, complexity, software moves at the speed of electricity and soon it'll move at the speed of light, it's a rapid in a river, you can take a sip, take a swim(if you're bold enough) or stay dry and thirsty, there really is no inbetween here, give it your all chaotically or do nothing.
It really depends on your goal. I would argue this applies to a subset primarily.
This is the video i was searching for ❤
I Really liked the video. As a career programmer, I find I deal more with people than I do with actual coding, perhaps to the detriment of my own coding skills.
As a scratch engineer, I disagree
Loving your videos and editing style. Would love to know about how you edit it, what's your process? Edits, voice-over, stock footage, etc.
Thank you for this, I'm interested in this field and want to learn more about it and this video gave me exactly what i needed to pursue this 🙏 HOPE.
I often
Plan, code, delete code, plan again, code, plan, delete some code, plan, plan, delete all, plan code,
Repeate until feel happy with code
building logic is the basic thing that one should learn first
I made the CS50 Python course over the last 6 months. Whatever i did was without any tutorial. I needed for some problem sets days to solve them. But after solving them i have learned so much.
i also made my own projects inbetween and evolved them with new learned skills and technics.
Now i'm feeling like i have really solid base in python and that i have the basics for going into every direction i wanted with it (data scraping, cyber security, gamedevopment... whatever i can think of).
Honestly I think the best way to develop the "programmer's mindset", is with the one step nearly every tutorial I have seen skips. That of course is the planning stage. Learning to plan out a projects forces you to break problems down, consider possible issues, consider data structures, ect.. IMO that is how and where you develop the midset. To bad no one I have come across really covers this in a way that new programmer's can grasp.
Not sure about taking first step is "Solving Problem". Mostly, don't have problems that's the key element - "Generate Problems". You're a developer yet also an a bit analyst and architect because most of the time you know what technologies you are going to use. So how to generate problems and get out of tutorial hell and properly use them?
1. Start from simple idea or copy paste and idea. Let's say I choose to create Service Desk.
2. Analyze the topic to be familiar with, let's say I don't know what is Service Desk and I need to analyze this word - "Service Desk" first.
3. Okay, now I know what Service Desk means and how do I build it?
See? Now you have a problem! So now we need to know HOW to build this type of solution. So what you will do next?
1. Analyze familiar Service Desk systems and take out MVP's.
2. Let's say our MVP is: Create login page, Create roles and assign them, reroute authorized users to ether user page or "role" based page, create a ticket, assign ticket, resolve a ticket.
See? Now I generated ton of problems! Great! Let's now start from beginning:
Let's plan our database design. Unless you don't know what is database or how to design it, bingo! New problem, go and analyze it. Then draw class diagram or create database schema.
Great now you have database schema now implement it with Prisma or w/e. One problem gone.
Now you need to know what pages will look, how do I do that? Yep, again, new problem, solve it! You will start from framework and drew few screens how it should look and what it should consist of. But wait, firstly I need to create login page and roles right? Yep, sounds logical, do that...
See what I did? You're now a problem generator and solver! You ask a question, create a problem, solve it by searching for information how to do it.
It's easy to have clear TASK, but not clear GOAL. Most programmers get clear TASK, they do the task and they move on. I'm not sure if you want to focus on that part, because creativity is another motivation generator and solving problems by your own it's the key and learning path you should take. Don't learn what you don't need, learn and execute what you need for your solution.
Edit: I stopped video after he mentioned problem solving and moved to project based programming and probably what I wrote is exactly that lmao
I was also hard yesterday 🥺
👀
0_o
My experience as a developer is that writing code based on a well defined user story is like finding a golden egg.
Majority of a programmer's time will be spent on stuff like:
- Making sense of stupid user stories that written like a long business proposal
- Screwing around with configurations, access issues, compatibility hiccups
- Fixing problems with CI/CD pipelines which are suppose to make life easier except they never fully automated
- Digging logs in AWS or Azure and trying to figure out why the last 5 deployment failed
- Ending up on a project as a front end angular developer only to find yourselves migrating jenkins pipelines to github actions after your first week
Finally someone that doesn't tell people about magic tricks and how to "become a Senior Pro Coder with this technique" - thank you for making this video man. I've been working as a self-taught, full-time software developer for 20+ years. Learning new languages and technologies over the years and all of what you explain here literally applies all of the time. 👏
And the further you go in your career, the more important soft skills become.
At a big company you need to coordinate with many different people from different teams all with different deadlines, goals and pressures than you.
I agree, problem solving and writing codes are different.
Bro where have you been? I wanted to quit every day before I watched this video, like GAWD! Really inspirational.
This is exactly what I'm going through right now. I was given an already built project that I have to dissect. It's like learning an engine and it's parts
Great video! Fundamentals are key! Frameworks and libraries are great, you still need to understand the underlying languages and concepts.
Im in boot camp for SE. Working on ma psychology as well as finishing up. Books help articles and CZcams tutorials.
I'm a Junior Programmer and can code whole Web apps to completion and I still struggle to be a good programmer in the exact sense of this video, this is 100% accurate
I’m literally in the process of learning code, and this perfectly explains my problems as I’ll look for a video or online explanation rather than figuring it out myself. Using cooking as an example is another perfect representation as I’ve begun making my own recipes which makes me feel like I know more. Now I just need to be able to do the same with coding
Another method of explanation could be like subjects in school, I was amazing at math, I was capable of understanding topics immediately and I could find my own ways to solve the problems. But something like English I simple stuck to the guide
Tip I’d add. One way to git guud, as the kids say, is to choose a fairly large project as an end goal… say a personal website or a simple email client. Something that would be helpful to you. Try implementing that and along the way you’ll run into countless development problems that you’ll have to overcome.
The skills that I most value in programming are
1. Break down problems into pieces
2. In order to understand what's going on you have to get creative with the print function, everything is about visualization and experimentation
3. Acknowledge that most of the work when programming is just debugging code
4. Don't waste a lot of time in problems that you don’t know how to solve jump into the next problem and you will gain a different perspective even if the another problem wasn’t related to the hard one
This was exactly what I needed!
the best anology here is with filmmaking. its not the technical and the 3 act story structure, because that's easy to learn. what hard is what kind of story are you going to tell? what of movie are you going to make? who is your target audience. a lot of filmmaking students fail to make movies because they focus on the wrong thing. what matters is creativity, problem solving, starting something from "scratch". good video :)
Yup. It takes lots time and practice. I've been programming since the early 80s and doing so professionally since the early 90s after getting a CS degree. I love my work.
Wow this video perfectly sums everything up!
I started my first Software Dev job at a small company 2 weeks ago and feel so overwhelmed with everything. All I ever did was "program stuff in python" and now I have to learn 100 different tools on the fly because thats just how that works.. Its really fun but also frustrating and hard because I constantly have to ask for help since I don't even know WHAT I don't know..
how did bro get hired😭🤣🙏🙏
@@tezzla6358 I am german. I think the software dev problem is a lot worse in the UK and USA than in germany. But still.. i applied for like 30 jobs and got 2-4 job offers. I was quite surprised that they took me too but I talked to them about it and the thing is that I still study so 1. I am cheaper and 2. I study the exact topic that the work with (LLMs) and people that know stuff about LLMs are really rare since its a relatively new topic. =)
Thanks for saying that programming is hard. It gave me hope to continue learning!
You just wrinkled my smooth brain today, thank you. I completely changed my view from programming language=lumber to programming language=tools 😮 and just like that 🤯 it was also then I realized that’s a lot of tools to learn how to use to sculpt lumber ☹️😓