Hello! I want to become a professional development. First, i want to learn code for free. Where can i get free cource to learn? Thank!
My answer would be:
I would recommend FreeCodeCamp 'coz they also offer free certifications (which really worth to get ones).
As Jason said there are lots of way to learn the code.
"Web Development" is a HUGE topic encompassing many sub-components, so I think what you really need is a learning "roadmap" -- an organized plan of what to start with and where to progress.
I would suggest you start with a decent HTML tutorial, from HTML move on to CSS and at the same time start studying usability and accessibility. Then (and only then) learn JavaScript.
The online tutorials at MDN are probably the most reputable you're going to find.
developer.mozilla.org/en-US/docs/Learn/HTML
Avoid nube-predator scam-bait like what the dishonest snake oil peddlers over at W3Schools dupe people into thinking is legitimate.
AVOID FRAMEWORKS as a beginner. Until you know how to build things top to bottom without a framework you will be unqualified to know if said tools are doing anything of value for you are even if they are any good! Once you learn to use HTML, CSS, and JavaScript correctly you'll find that most all of them -- bootstrap, w3.css, jQuery, etc, etc -- are utter and complete nonsense rooted in bad practices, and based entirely in ignorance and misinformation.
There's a LOT of junk being peddled out there, and a LOT of "bandwagon" mentality making media darlings out of complete and utter chazerei. Part of the learning process is getting a grasp on separating the wheat from the chaff -- when in doubt? Go to the ACTUAL official specifications, references, and more reputable sources like MDN. Mozilla Developer Network -- the folks behind the Firefox browser and Gecko rendering engine on which it is based -- you might expect them to know what they're talking about!
You'll be surprised how often something in a sloppy tutorial (video tutorials are amongst the worst for this) by some fly-by-night nobody are riddled with disinformation and misunderstandings DIRECTLY contradicted by the specifications and/or official documentation! It's so bad sometimes they make "The Verge"'s tutorial on building a gaming PC look good.
But let's give you your first lesson. Something a LOT of tutorials are going to gloss over.
HTML is for saying what things ARE -- grammatically, structurally, semantically. It's where the term "semantic markup" comes from and is the entire reason HTML even exists. This is so ALL user-agents -- software that turns HTML into something a user can use -- can convey those meanings. Be it for perfectly sighted users on a screen media browser, someone on the other end of a TTY connection, or even the non-sighted and visually impaired!
A browser is a user-agent but a UA isn't always a browser.
Hence the saying:
If you choose any of your base semantic markup based on what you want things to look like, you're choosing all the wrong tags for all the wrong reasons!
Hence if anyone tells you that the purpose of H1 through H6 are for "fonts in different weights and sizes", HR is for "drawing a line across the screen", or that P is for "a double-break after this text" they're basically talking out their arse.
CSS is for saying what things look like for specific media targets. A media target is basically a device. This way the appearance can be customized for specific targets based on the underlying semantics and needs of a designer. Be it for big screens, small screens, print... there's even CSS for non-visual such as "aural" / "speech".
JavaScript is SUPPOSED to be for enhancing already working pages with helpful behaviors. Sadly people have used and abused it to the point a LOT of pages are so reliant upon it they tell users with accessibility needs to sod off. You will need to learn it, and learning it properly should mean that the majority of what you do with it also needs to be certain the page is at least usable when JavaScript is not present. Think of it as the bells and whistles, the final wax and buff. There are exceptions for specific applications -- Google Maps being a good example of this where the utility would be greatly limited scripting off -- but for the majority of 'normal' content on a website it's best to "keep it in your pants" as it were.
You also have to watch out for the trap of using JavaScript to do HTML or CSS' job. This is even more true given the powerful animation features present in CSS3 that in a few lines can replicate what used to take dozens of lines of JavaScript. This is part of why I say learn to do as much as possible in HTML and CSS before you dive for the JS. Yes, it's shiny, alluring, tempting... it can also tell visitors to your page to go plow themselves if you use it wrong; and boy do people use it wrong.
SO many things that we used to have to use JavaScript for are simply no longer its job -- collapsible sections, drop-down menus, animations, modal dialogs -- make the sections useful with HTML first without the fancy stuff as if CSS and JavaScript never even existed, and in most cases let CSS do the heavy lifting when it comes time to make it fancy!
Only once you have a handle on building standalone fully functional pages client-side should you put any effort into learning a server-side language. I would suggest starting with PHP since it's the easiest to set up (since it comes with nearly every web hosting plan out there) and has the best documentation and communities of knowledgeable people. It integrates well to SQL databases and is overall one of the simplest and easiest approaches.
From there you can branch out into other languages.
Again it's a massive topic and there's a LOT to learn, and no matter how much you learn you will need to keep researching, studying, and learning your entire career. This is simply not a field you can "learn once and be set for life" as it is in constant flux. Changing, growing, expanding. This too is an aspect that is often glossed over and I really think you need to understand that before you get too deep into it.
As I was told some thirty to thirty-five years ago when I was still a rookie programmer:
The day you stop learning is the day the rest of the world leaves you behind.
I've been programming for forty years having started out when I was still in grade school., doing websites for a little under half that; and I'm still learning new things every day. There is always something new, some radical new change, some better way of doing things -- AND old mistakes being dredged up as the latest hotness. Be prepared for that.
Hell, just keeping up with the fact they keep assigning new names to existing concepts and practices, or dragging old outdated "professional educator" concepts out of retirement and shoe-horning them into new systems as the latest flavor of disco pants could be a full time job unto itself.
Freecodecamp and youtube muh dude. Freecodecamp also has a youtube channel with a ton of free courses that are even more valuable than some paid courses.
Get an internship with any startup. Ask them to do the work for least pay provided they teach you stuff.
Kishan Bhatt
Web Developer
"Traversy Media" - YouTube Channel.
youtube.com/user/TechGuyWeb/playlists