you are on point!

if you don't put 100% of yourself AI will take over you at this pace

Yessir, a little at a time adds up. Soon you'll be designing million dollar ideas :D

Sure.

programming is a hobby

I went the same path. Now back coding C again, using man pages. Trying to use as few dependencies as possible. Stupid? Yes? But fun? Also yes!

Hey! Quit making fun of me

Why do you need to go off and build things yourself if you’re in school? Literally no other degree works like this.

if what you're programming on is free, then it can be learned for free

@@TheFrustratedProgrammer_ The problem is that there is a lot of people that are new to programming and don't know better, so they end up falling for these scams.

@TheFrustratedProgrammer_ I mean he had a point , so I can’t really argue abt it

Fireship is the only tech channel i enjoy

What. Do you offert yo me ,? Your comment doesn't mean something ,Keep scrolling body

what woudl you advice? I'm a beginner. I want to have tech skills as a backup currently pursuing my dreams of launching my own business. but I know I ave to be realistic it could work out it might not, might need to make some extra income, don't want to start from scratch (but also want to learn and use my brain to learn a new skill). Is there a career in tech that would be the best to train in?

In this field you either have all the money or none of it. 😂

same

Same lmaoo

No no bro 😅

It was getting in the way of his coding. Not aerodynamic enough

Cause it's his beard and he wanted to shave it. Wtf

Sideburns and goatee are bloatware. He simply optimized his (inter)face

The stache is the way brother

@@gringotico1759 no shit sherlock

But dont get me wrong, I do have major versions, such as o.5 or 1.2b etc. But I keep them as simply backups. Then the word version justifys itself.

holy shit this guy

@@zaid4708 yeah I know... But I always hear the same sentence "there are so many versions, we need to unit test" and seems like people get stuck.

Well, a huge chunk of our industry, and that of PC based software meant that many a developer lacked version control. However, I think front and center is seamless, easy, fast and some kind of version control that does not get in your way. So, WHEN it is super easy, super fast, then you find source control will not get in your way, but become your friend. So, while I use github all day long, I use it from Visual Studio, and thus I never even learned the command line stuff for git. Where Source Code Control (SCC) it comes in REALLY huge? Well, say you working on some code, and you have a issue or bug, and ask, gee, what was these few lines of code like before I changed them? Right click->git->compare with un-modified. Now, both sets of code are displayed side by side with the changes. Absolute super handy. And this means you free to try and change code, since you can always go back, or view previous code - and you don't have to leave the IDE to do this. So, this means you are free to make changes, and you don't have to say comment out a block of code that you want to keep in case some changes don't work, or you need to view/look at the previous code that was working. So, it takes a lot of stress off of trying changes and tweaking code. The other issue? Well, if that software already deployed live, and you working on the next great feature, what happens if a production bug needs to be fixed, but you 2 days into some new code? Now, you are in a pickle, since then: A) you have to go to previous saved version, fix the bug, then deploy, but that bug fix is now not in your latest build, and then you now have to copy over those code changes to the current v-next version you are working on. This can be a real pain. B) you comment out, or disable your new big feature you working on, and then fix the bug/issue in your current build. With SCC, you can branch that new feature, and thus are free to continue to work on that feature. But, you can also take master, fix the bug, and commit. And now you free in that branch to pull in that bug fix. Once again, this all comes down to convenance. The other big issue? Why of course when working with more then one developer. So, we are in the process of moving out a bunch of code from 2-4 applications that is common to those applications. So, we building a business object that has VERY important code such as creating a new project, approving a project etc. However, there are about 4 applications that need these features. So, that business object is now under SCC. So, any and all of the developers can make changes, add new features, and for our web portal, desktop software, and even some console software that needs that code base and business object? Well, there is only one copy of that object, and any developer can make updates to that shared library code. So, I can make updates, test, and then commit. Now, when every other developer working? They can just pull those changes, and when they build + deploy changes to say the web portal, or some console application? Those builds have the latest business object with changes. So, I like the freedom of being able to try, test, change code. I can with a simple mouse click then view the previous code. Or I can even just "dump" the code changes I made. In effect, using SCC means I have a built in super duper un-do system. This allows great freedom to try and make changes, and yet I can always view my previous code with ease - not having to go to some backup or previous version. This freedom means now I don't comment out a lot of code blocks, but just delete them, since I can always with great ease view the previous code before changes anyway. Same goes when you working with multiple developers. Exactly who, where is the latest build that currently deployed? It can't be sitting on some developers computer - as that will not work at all when you have multiple developers. So, with SCC, then any and all developers have a repository of the current and latest software builds for our software. So, once again, if you have say 5 different software systems being used, then on any developer computer, then any of the developers can pull that build and work local. So, must one use SCC? No, but it has boatloads of benefits. It all comes down to if you have multiple projects, and multiple developers. If you don't have multiple projects, and you don't have multiple developers, then SCC is not a must have, but even then, it still nice to try code changes, and not having to worry about how easy a un-do to those changes is. However, unless the SCC system is 100% seamless, and 100% integrated into the IDE you are using, then SC starts to get in your way. If you have a simple, easy to use GUI based SCC system, and a dead simple means to pull and push out your builds? Then even the most green of developers will enjoy and use SC, and SC will fast become your friend, and not something that gets in the way of development. So, much of this comes down to the scope and size of the project, and do you have multiple projects sharing some code, and that of more then one developer. In such cases, it becomes very difficult to work without a SCC system.

Don’t comment again