Menu
Community /Pin to ProfileBookmark
@NogDogAug 19.2016 — #Becoming a "web developer" is a rather fuzzy goal. At one end of the spectrum you have people working from home "building" web sites with Wordpress and 3rd-party templates, with maybe just enough know-how to tweak some of their favorite templates to customize them a bit. At the other end you have developers with advanced degrees in computer science doing very complex things with high performance requirements. Then there are the rest of us sitting somewhere in between. Where you hope to end up (short term and long term) on that scale will be a major factor in determining how long it will take you to get there.
As Jedaisoul mentioned, HTML and CSS are probably the easy part (though some advanced CSS concepts take some digging to learn). Once you get into actual programming languages (HTML and CSS are [i]not[/i] programming), there's more to learn than just syntax. You need to learn general programming concepts that are largely universal to any programming language, and you need to learn essentially how to think like a programmer and work like one. You probably won't learn much of that by just learning the syntax and commonly used functions of the languages you're interested in. I'm pretty sure you won't measure that learning in weeks -- and realistically, of course, you never finish learning it. ?
Instead of a waterfall approach of learn this, then that, then that... I might suggest a more agile approach (as per agile software development methodology). Set yourself a goal for something you want to create (hobby site, personal blog, whatever). Figure out what the first, simplest, most basic MVP (minimal viable product) would be, and try to build that. You'll likely find you want to break even that MVP into pieces you can address individually (and start learning about modularity). Then whatever piece you're working on, figure out what you need to know to do it, and start focusing on learning those bits. As things start to come together, think about how to flesh out the MVP with additional features, and look at how you could improve things you already created (a.k.a. re-factoring) with better techniques you've encountered in your studies and Googling.
And read a few good books on general programming concepts. ?
This is my plan to become a web developer. What do you think??
Hi Gang, I want to start off by Introducing myself. My Name is Dan and I want to be a web developer. I tried becoming a web developer a few years ago but unfortunately, I could not give it my full attention and time that is required.
I recently bought a web developer course from udemy,it’s a great course and I love the way the instructor explains and breaks things down. With that said, After going through the HTML and CSS section, I noticed theres a lot of information that needs to be learned and realistically even if I go throught the whole course there is no way I could remember everything. After doing some research and speaking to a few programmers at meet up groups. I’ve come to realize that you only need to know about 20 to 25 percent maybe less of any language to proficent enough to start taking on clients.
With this in mind I’ve come up with my syllabus and i would like to know what you think.
Week 1-2
Html & Html5 this includes going through the Udemy Html section and doing any projects in the section. On week 2 I would practice 2-3 hours a day doing some forms,blogs,any very basic website that allow me to practice html.
Week 3-4
CSS & CSS3 this includes going through the Udemy CSS section and doing any projects in the section. On week 2 I would practice 2-3 hour a day create new forms,blogs and basic web page from scratch but i would also style them.
Week 4-5
Javascript this includes going through the Udemy Javascript section and doing any projects in the section. On week 2 I would practice 2-3 hour a day what I learned in the course along with stacking and doing some forms,blog,and simple websites from scratch not only practice javascript but also to keep my knowledge on CSS and Html fresh.
This would continue Jquery.PHP,MYSql,and bootstrap
Sign in
to post a comment2 Comments(s) ↴
0
@NogDogAug 19.2016 — #Becoming a "web developer" is a rather fuzzy goal. At one end of the spectrum you have people working from home "building" web sites with Wordpress and 3rd-party templates, with maybe just enough know-how to tweak some of their favorite templates to customize them a bit. At the other end you have developers with advanced degrees in computer science doing very complex things with high performance requirements. Then there are the rest of us sitting somewhere in between. Where you hope to end up (short term and long term) on that scale will be a major factor in determining how long it will take you to get there.As Jedaisoul mentioned, HTML and CSS are probably the easy part (though some advanced CSS concepts take some digging to learn). Once you get into actual programming languages (HTML and CSS are [i]not[/i] programming), there's more to learn than just syntax. You need to learn general programming concepts that are largely universal to any programming language, and you need to learn essentially how to think like a programmer and work like one. You probably won't learn much of that by just learning the syntax and commonly used functions of the languages you're interested in. I'm pretty sure you won't measure that learning in weeks -- and realistically, of course, you never finish learning it. ?
Instead of a waterfall approach of learn this, then that, then that... I might suggest a more agile approach (as per agile software development methodology). Set yourself a goal for something you want to create (hobby site, personal blog, whatever). Figure out what the first, simplest, most basic MVP (minimal viable product) would be, and try to build that. You'll likely find you want to break even that MVP into pieces you can address individually (and start learning about modularity). Then whatever piece you're working on, figure out what you need to know to do it, and start focusing on learning those bits. As things start to come together, think about how to flesh out the MVP with additional features, and look at how you could improve things you already created (a.k.a. re-factoring) with better techniques you've encountered in your studies and Googling.
And read a few good books on general programming concepts. ?