How To Become A Coding Machine
Vložit
- čas přidán 18. 05. 2024
- Hey guys, this is a silly little theory I've had recently and it's paid dividends.
Felt good to make this kinda video after a long time.
Btw, wanna build cool stuff? app.codecrafters.io/join?via=...
Music
massobeats - glisten: • massobeats - glisten (...
I see some CZcamsrs doing this for seo, let me see if it works
How to keep coding, code, nonstop coding, code for fun, code and have fun, programming, make programming awesome, program for fun, unstoppable programming - Věda a technologie
Couldn't agree more. Part of the fear comes from losers on the Internet judging anyone who makes a mistake. Like mistakes are literally how everyone learns.
Goated NeetCode appearance
If you let "losers on the internet" influence what you do, even when they can't even see it. Then honestly that's on you.
haha exactly. you write anything, chances are there's at least 100 perpetually online people out there with ability to find faults in it in 100 ways.
hey neet! i
Hey neet!
This is also known as "analysis paralysis". The only way to get through it is to just start with something. Make it work, make it pretty, make it fast!
Yep. I've been stuck in analysis paralysis since i began. but also "What should i make" " i don't have anything im interested in making" "Am i allowed to google stuff" "But I want my code to be 100% original!"
@@ahmedameer104 Yeah, the surest way to never start. Think about it like this: dumber people that aren't obsessed about optimization can do this better than you can, because they don't have such limitations and just do the thing. Doesn't that piss you off?
How I can pass that ? I ´m stuck in that 🥲
@@pierremarcadet2474 Just think about all the dumber people than you that can do the thing, because they don't have the same analysis obsession. And how they will surpass you because of it. That should fix it.
@@Leonhart_93 I infact have thought about that before, And yes that does indeed piss me off. The curse of being more aware and smarter.
Remember folks, "Premature optimization is the root of all evil"
it's one of the enemies of good after all
L take. Better/easier to optimize from the beginning than later to rewrite the project.
Specially applicable to web sites (seo, page speed etc)
Tell that to Germans 😂
@@codingtostopprocrastinatio9748thats why he said before pushing to prod
@@codingtostopprocrastinatio9748
This is assuming you would need to "rewrite the project". Unless you are new at designing projects, this will hardly happen, and if it happens then your "optimized" code probably don't look any maintenable already.
if only i had a dollar for everytime he said "you can end the video right now."
I wonder if it has affected his watch time 🤔
@@RajdeepJadejadoubt. Its a 2 minute video.
@@RajdeepJadeja doubt. when you hear it from the youtuber, you feel comforted
congrats on your 3 dollars
Thank you bigbog
damnit
THE CHANNEL LORE DEEPENS
@@bigboxSWE cumArray ?
Big feels. I lost the spark for coding and currently starting to slowly hate it because the constant judgment you get from the community. It's always the "Oh you use X? Use Y, it's better" problem.
I let that perfectionism mindset get to me, it drains you from all enthusiasm after you waste tons of time learning various design patterns, languages and algorithms just to be told that your code is not good enough, there are better solutions or if you don't do something the "proper"/best way then you're just a bad developer.
i never tried to implement a best practice. i just do what i see fit and optimise and benchmark when its not preforment enough (even though thats usually very rare).i make it work first then i fix it later if any bugs are reported. i guess thats why im didnt give up on coding yet
The real skill issues were the form-over-function purists we met along the way.
Most “best practices” are just strong opinions, not facts. That thought helps me very much to handle all those over opinionated devs who always think their solution or code standard is superior in every possible way.
All these practices do is secure the person’s position at their organisation once they’re implemented.
It’s like asking someone to help you while they’re robbing you in broad daylight.
Meanwhile there does not come any software-product come to mind that works completely perfect. Or any product in fact. I try to remind myself of that when perfectionism gets to me. If million and billion dollar corporations can build bad products with stupid bugs and still be successful, its ok if i have some issues here and there.
"Quantity makes quality" that really made a lightbulb go on in my head. Thank you for giving me a whole new perspective.
Quantity brings quality - well said 👏
I really needed to hear this advice. I always feel more at ease after watching your videos. Love to see this type of content back on the channel!
Love this channel and the simplicity and realness
I love this video,
I tried something mentioned in the video since like my second month of coding, I saw I was rapidly improving my skills bc the first year is always the time period you learn the most, so I started a project, and I left it after I made it work I didn't try to make it faster things like that (no fancy thing, it wasn't good, it was working tho :>).
Then I rewatched it after 2 months, my eyes were bleeding, I recreated that from scratch using a "kinda similar" logic, but Better, because in those 2 months I became better, "for me", that was a huge victory, it meant I was actually improving, so I did it again, those project aren't my "big ideas", I just go to my "overthinking book" (I write down useless/useful thing I overthink about) and take a random page, I do a useless/useful project about it. If you never tried something like this and you are a new, give it a try :)
I love your channel, u sound like my inner voice regarding coding let’s get it! 💪🏼💪🏼
For a 2 min video, you give the answer in first frame
and your advices have been excellent
Thank you!
ive been following you for a while now, and i have to say thank you for all the advice, insights, and positive energy you share with the rest of us each and every video. You are a GOAT to me man, cant ever thank you enough :D
Big Guy always posts about the thing I am struggling with at the moment. Thank you Big Guy!
man I can so relate to this, thank you for this invaluable advice
I don't even code at all anymore but I still watch your videos and always get something out of it. Absolutely love your no-BS style and your perspective.
You sir, are a gem. I definitely needed to hear this.
Excellent piece of advice!! I'll take it into practice. I can't thank you enough
Man these really help me a lot. Appreciate it 🙏
I really really needed to hear this. Thank you.
Great video!
Thanks for the experiment and refactor branches idea I would definitely do it in my next project.
Man, you have no idea how much you helped me.
Your 1 commit/day rule is already showing its magic in my personal projects.
Will definitely give the experiment branch a shot.
I'm currently on a startup business, and since I'm on my own for everything, the "experiment branch" method is what got me pass my "block" on code, I'm amazed you described it exactly as I do it too. Cheers!
Please hire me
I needed this. Thanks for sharing ❤
Sir. Couldn't thank you more for encouraging my path to learning to code
I think this is also a great way to work on your personal projects. Many times, I see myself thinking much about structures, stacks and ideas and ended up I couldn't even start a project. Just start a project without the "perfect" plan then learn it actually, plans I initially thought are changing while working on the project, and I called it version v0.0.1. In this version, I used only that I'm used to use to develop it fast then later version, I will add some more. As a React developer, it could be additional configuration, design changing(it could be use another UI framework), structure changes, and stuff. It's been not so long but yes seems going well. Thanks for the video 👍
Yt recommendation is godly sometimes. I am in this loop of over thinking and best practices but it really holds me back from starting. I think I'll get better.
Thank you for your kind words. Just what i needed right now.
Another fantastic video, thanks for the content, big ox.
Learning to code and man that was very helpful. Thank you.
You are the best man keep producing
you got s sub bro
very relatable to me
and I try my best to start with good conventions and just make it work and then clean side by side
After 2 decades of programming I have a simple motto : « Code first, think and refactor after »
And don't be afraid to trash all previous code when refactoring. You're not writing the 9th symphony, it just has to pass the same unit tests suite
People like you are the reason why 99.9999% of code out there is an utter garbage.
Great video like always 😊
thankks for the daily boost bigBox
thank you, I needed to hear this today.
I've been stuck thinking about the right way of writing code for 5 years now, still stuck in the beginner phase.
Thank you, I needed this reminder.
This was marvelous... thanks, I do often stare into the wall just to come up with the solution...
One thing I only learnt recently after a 13 year engineering career, 10 of those coding, was to forget everything else and just write your idea into code. It sounds so obvious, but it's also easy to fall into the trap of trying to write "professional" code on the first go. Get it working, and then refactor.
Thanks, i needed this.
I'm starting a professional training for coding starting next week. So I'll take that advice to heart.
Every feature should really be made on a branch so you can scrap it if you make a mess. I think SVN may have scared a lot of people from branching as it wasn't good at merging, but that is git's killer feature.
People are afraid of branching? I thought it was one of the good practices.
I said good because there's probably something better than branching.
@@asagiai4965 it's probably a lot less so today, but around the time git was first released there was definitely a fear of branching
Love the video. I really needed to hear this XD
I kinda needed that.
thank you
This resonates with me on another level man😢
This channel feels like the calm version of Fireship
Very True🤣🤣
This is standard in test driven development companies and is called MVP (Minimal Viable Product). You get the smallest possible concept to work, without refactoring or clean code, and then iterate from there.
awesome, bro made it simple!
coding, Treat is as experiment.
this is true. i even got a job cause i said i did this intuitively.this was before i even knew of it. i love my brain for doing that.
personally i make minimal bare working version. and i do it multiple times with multiple designs architecture whatever. dont overthink just do it.
then i make the actual product. it more fun to start thinking seriously when i have a working version and can see progress.
just when i wanted to overthink "how to become a coding machine" the video ended... it would be stupid to continue thinking about it instead of doing it -- perfect video length
Wish u to continue creating such a contents! 🎉❤
I love how you made the comparison to music, as a long time music producer who's been coding seriously for a year now, we call it "tidying it in post" lol. But no seriously, finding your minimum viable prototype and then making it more performant/added elements after getting it to work is vital to navigating analysis paralysis or "writers block", or what music producers call it "beat block".
Nick Mira (a very successful producer) basically addressed it in this way also. Open up your program and put something down. Iterating an actualized idea is a lot easier than getting stuck in the details without a finished product.
DUDE! This is so helpful you have no idea. I've never considered that what I'm feeling is a 'coding block'. Gonna code some garbage til I collapse today tysm
Currently applying this to my electronics learning journey and its finally fun to suck at it :D
Bro thats so true, non of my projects is anywhere near good code for ppl to understand 😭
great Idea.. couldn't agree more on this.
Create an environment conducive to your objective. Minimize external distractions, like sound and interruptions. Minimize internal disruptions like positional pain and fatigue; manage your water and bowel movements through regularity. If you have a bad back, you are going to want a reclining setup with multiple monitors, Master your tools. Limit your research related tangents to less than 2 minutes or file them as optimization projects, block out some time and create tangible products like code snippets that can be used across projects. Understand the intent of the code. Master secure coding for your language. Master design patterns. Master architectural patterns. Improve your typing speed with particular emphasis on navigating the file system, adding comments, cutting and pasting, using code completion and shortcuts. Practice system administration basics: cyber hygiene, system backups, configuration backups, cybersecurity through system isolation. Choose tools that are likely to be around for a long time. Use templates and automation wherever possible.
This is actually a super-solid list, thanks for bringing the goods.
man's gonna make me cry
Thanks, I needed this
Your best advice so far. That was my biggest problem
that's very true. Thank you
This is also called Proof Of Concept in tech world, very useful when you are solving a unique and challenging problem.
Pro tip: when you are done with POC - add some unit/integration tests on top before refactoring - in this way you can always be sure that you did not break anything important during your refactoring and you can go crazy.
Thanks, I needed that
This is so true. Thinking you're going to write the best solution first time is like sitting down to right your first book and expecting Shakespeare
Always follow these three steps:
1. Make it work
2. Make it right
3. Make it fast
I've been coding for 30 years and I totally agree with this. You don't write good code because you follow best practices, you develop best practices from writing a lot of code.
Coding has 3 phases... exploring the problem space, finding a solution that works then discovering a better solution.
The only thing that changes with experience is how many problem and solution pairs you have in your experience bank.
I totally agree with that approach but with 2 different projects one is my project the second is the lab where i do all of my dirty work
I always start my project and divide to small tasks and every task i use bad approach, algorithm, not clean code, brute force if i have to just to make it work then i start use the logic after knowing it works by making refactoring using aspects of clean code and better architecture patterns knowing that i am only doing refactoring and not thinking about any logic which makes my life easier sometimes
This is such great advice.
This is like the saying, “first do it, then do it right, then do it better”
Had a lot too say but could not compile in a single line so just thanks for now.
Agree with your advice. Use git as your power tool. You want to validate your idea? no worries just create a new branch and start working on it. You can break things without worrying about it too much always knowing you have working code in a different branch. Once I had 6 different rails projects for the same app because I was constantly changing db schemas and it was too much work to revert changes and roll back. Instead I created diff projects based on elements name from periodic table. Aluminum, Carbon etc..
When programming follow this -> Make it work(core functioning), make it right(abstractions etc), make it fast(optimise for performance)
Only thing to add, 1:06 use an “experiment” feature flag… you really don’t want a bunch of branches or repos for maintenance hell.
can't wait for primegan to review this soon
As odd as this sounds, I’ve found that drawing or writing it out on a piece of paper helped me tremendously since I was able to physically see it. Embedded firmware is tough and always felt like I couldn’t get started if I just stared at a display and tried to think of the solution. To each is own I guess
The "searching the right way to write code" hits on every level. Damn, I've lost a couple of hours doing that before starting to solve a problem.
it was needed thank you
This is sctually useful even outside coding itself.
.
Thank you Bigballs
Yeah that's a problem with me too. I'm too preoccupied with creating the "best" solution before even implementing whatever "brute force" thing comes to mind first. Guess I care about best practices just too hard.
this channel is a good experiment
I used to code like this, no worries, just produce working code.
Then I switched my employer, and they needed to have all the best practices, design patterns, clean code, what not... It sucked (and still sucking) the life of my soul.
The problem is that I never learned to code with all these concepts. And I feel like a total junior... I lost the passion and fun in coding.
So, I advise all of you, don't stay comfortable for too long. Always learn the best practices, even if you don't need these right now. Practice all the time.
I needed this
Bro, I need to rewatch it again and again.
I need to create a lot of vad code😊
Instant sub, Kudos.
Make it work, make it right, make it fast
always starts with the mvp (minimal viable product)
this guy really is bigbox
I used to procrastinate with programming YT content for hours...
Now I just watch 1 bigboxSWE video and then actually get to work.
That is EXACTLY what I was doing for the past 1,5 year. I always thought it's me that is the problem, I'm not good enough, I'm writing terrible code, I don't know how to structure this, what method would be the best, what database would be the best for my use case, should I go serverless or docker, REST or tRPC, node or bun. I will FINALLY try to write. some. code.
I'm going through that phase of planning everything, thinking up the best ways, implement best practices, which means stalling more and more
Undertale dialog system is a 10k+ line switch statement, there's people who follow best practices and then there's people who ship
right, bad code is better than no code
just start with what first comes to mind, test it and see whether it does what you intended and learn from the tests what is actually needed, can be scrapped, streamlined etc
I got more productive once I accepted that perfect is the enemy of good.
Often the most basic solution is the best solution. You can make it more advanced later - once you have a clear case for it.
The bro gives you all the knowledge of the video in the very first second
Such golden words. I would rather have a terrible code that somehow works with console full of errors than nothing at all. This mindset of "alpha version" of your project is very important to avoid burnout, doesn't matter what you actually do.
Yep. Always write your code at least twice.
I my group project we did the experiment branch thing except we didn't call it "experiment" and didn't write better code after finding something that worked
what i needed 😮💨
Thanks for this