Any best advice for beginners as a Web developer.
keep up with last update and lots of works ^^ Also socialize is important
Always be coding projects on your own. Don’t do tutorials or walkthroughs unless you need to learn a concept for another project.
Five best tips for you:
## Don’t Give Up
If every developer gave up the first time they saved their project and things went completely wrong, there would be no developers. Heck, there would probably not even be an Internet with anything more than Hello World.
Failure is key to success in web development. The path between your idea and the webpage you want to build is a series of problems that have to be solved, and very rarely are they solved on the first try.
Even the best developers in the world regularly come across problems that require them to save, test, and debug repeatedly until they find the right solution. It’s in this that we find new and more efficient ways to get things done.
## Start Simple and Work Your Way Up
You can also take classes online to help you get started in an organized setting. We have outlined some of these online learning tools in our guide.
## Don’t Be Afraid to Learn New Things
You will never stop learning as a developer. There will always be a new process or a new codebase that changes anything and everything you knew before. If you want to keep up you have to constantly be open to new ideas and new methods, and be willing to learn and try new things.
The latest web technologies we are using today will be obsolete in no time, and you will need to be ready to pivot when that time comes.
## Find and Use Resources Regularly
There really is no such thing as a truly original piece of code. There are entire libraries of commands, filters, and functions that you can use to solve a problem, and you can generally find them very easily online.
For example, if you’re working with WordPress and want to know how to get started with developing your own theme, there is documentation for that.
Using tools that bring documentation together from several resources can also be helpful. One solution is an app called Dash which makes it easy to search for a specific command or solution in documentation for just about every major platform out there.
We have outlined a number of additional useful resources for developers in a previous blog post.
## Set Up Your Own Development Server and Play
Don’t worry about hopping in to doing professional web development work. This requires patience, and plenty of practice. You can practice to your hearts content using your own computer by setting up a development server. This server, usually hosted from the same system you’re using to code, is a small Web server that you can use to see the results of your work in a browser without having that work ever appear on the open Internet.
We outlined how we use MAMP 3.0 (now 3.5) as well as listed a number of alternatives for Windows and Linux users in a previous blog post. These solutions are inexpensive (often free) and offer you a fully functional development environment.
Once you have your development server up, then you have a virtual sandbox to play in, break things, and try out new ideas with. Practice is the best learning tool a developer can have, and a local development server is perfect for this.
Web development is a rewarding activity. It empowers you to create websites that are completely unique to your vision, and better prepares you for more advanced areas of programming.
I also observed that thing completely following a tutorial or projects not a good practice.
You SHOULD be learning from people smarter than you, that will be your richest source of information. Watching tutorials not only exposes you to the instructor’s thought process as a developer, it also can cover many things you might not have known or thought of.
Just maintain a good balance between drawing information and putting it into practice, you don’t want to rely only on tutorials, and you don’t want to avoid them completely. And pick a good instructor, don’t stick with watching people who are not contributing to your learning as much as you feel they should.
Thanks for the tips. Yeah I am doing practice the only problem I’m getting is I don’t understand the fallow of the project as now I am doing shopping cart project in codeigniter I am getting problem where will be that function, parameter, variable. If is there any suggestion about that then please.
Thanks for the informative lines really motivational lines I will definitely following. Can you please tell me which type of courses are you providing?
Actually, I take the opposite approach from @DanStockham above. Doing tutorials always leads me toward doing more involved projects on my own. Leave yourself open to that.
I think what holds majority of people back from becoming developers is the fact that they mistaken walkthroughs and tutorials as projects. The average new person does work required of them from the tutorial and they are done. They’re either lack the level of curiosity or are too intimidated to continue making a project after doing the tutorial. Hence, that’s why I recommended to immediately start building projects from the beginning. Even if it is small code snippets to demonstrate programming functionality.
I totally agree with your statement because myself do the same thing now its difficult to build a project without any tutorial or project guideline, but now I am trying to do without guideline.
Yes, there’s a lot of truth here. Employers can tell the difference.
Doing a tutorial is like copying someone else’s painting, be walked through it by the original creator. You may not even know why you’re doing some of the things you’re doing.
Doing your own project(s) is like conceiving the idea, sketching it out, revising it, working on it, making the tough decisions, and finishing it.
There is a big difference between these two. I’m not saying to not do projects - they can be an invaluable way to be exposed to new ideas and see how another coder thinks. But it is not the same as doing it all yourself. Hirers can tell the difference.
Can you please elaborate on this point.
Even I am a beginner.
When learning a new concept, I do use a tutorial to learn the basics, but then I’ll use what I already know to build the tutorial out even more, and as I learn new things, I return to old projects and build on them even more. I’m honest as well, in any of the projects that started out as a tutorial, I put attribution in my ReadMe, and not ever try to pass it off as something I built from scratch.
Other tips…Data structure and algorithms. Study them…but…dont lose track of your basics as you go along too. I just went through interviews, and I was so focused on studying data structure, that I was blind-sided by some really basic questions. All that studying and I wasnt even asked to traverse a binary tree or reverse a linked list…but I got a question about the virtual DOM and by brain darn near exploded. So yeah, make sure you keep up on the “easy” stuff as you progress.
Also, study up on Big O notation. And when you get to the part where they say stuff drops off cause it doesnt matter…ignore that!!! In both my interviews, I got side eye for saying my O(2n) solution was O(n). And then in the next interview, for saying my O(2n+3) was O(2n). They both stressed that everything keeps saying it doesnt matter, but in the real world, it does matter and when Im on the job, Im going to use that knowledge all the time to write efficient code.
Um, what else…study what is popular for the area where you are trying to get work. That way you are focusing on your employable skills… Thats all I can think of for now.
just like cndragn said ^^