News for hackers. Stuff that matters.
Re:Roadmap to becoming a web developer in 2017 by scriptkiddie95 on Monday March 27, 2017 @05:38PM (#13972031)
As a young developer, it really is intimidating. Hard to know where to even start these days, it's overwhelming.
Re:Roadmap to becoming a web developer in 2017 by gingerbread-man on Monday March 27, 2017 @05:43PM (#13972063)
It doesn't really matter very much where you start. Pick something and dive in. Once you feel very comfortable with that, add another skill.

Personally, I'd suggest learning a programming language first: Python, Javascript, and Ruby are all good choices. Find a book you really like in one of those languages and read it cover to cover.

PS: https://eloquentjavascript.net is great, and free.

Re:Roadmap to becoming a web developer in 2017 by afarrell on Monday March 27, 2017 @06:19PM (#13972340)
If you want to go with python, http://openbookproject.net/thinkcs/python/english3e/ followed by http://chimera.labs.oreilly.com/books/1234000000754 are both free and teach good habits on the way to backend web development.
Re:Roadmap to becoming a web developer in 2017 by sdfin on Monday March 27, 2017 @09:53PM (#13973397)
I think this is the link for the site of the last edition of the 2nd book you mention http://www.obeythetestinggoat.com/
Re:Roadmap to becoming a web developer in 2017 by gingerbread-man on Wednesday March 29, 2017 @05:20AM (#13984540)
What a wonderful name for a programming book.
Re:Roadmap to becoming a web developer in 2017 by afarrell on Wednesday March 29, 2017 @08:24PM (#13991893)
I actually bought a plushie goat and keep him on my desk.
Re:Roadmap to becoming a web developer in 2017 by voltagex_ on Monday March 27, 2017 @05:43PM (#13972061)
Does 28 still count as young? I've been doing some form of web programming for 8 or 9 years now and it's almost impossible to keep up with JS/Node/NPM/100 different poor re-implementations of 'make'. Luckily there are big enterprises that provide job security without chasing every new framework.
Re:Roadmap to becoming a web developer in 2017 by badosu on Monday March 27, 2017 @06:15PM (#13972311)
These days I made a project as a test for a job.

It required a SPA framework, I am pretty much used to Backbone but wanted to use this opportunity to check how are the new shiny things these days. So I picked up Vue.js

The architecture is pretty clean, minimalistic and well thought. Soon I realized how terrible documented most of the tools on js land are these days, it was very frustrating to see that most of the options are not well documented, so that you must find a suitable blog post or tutorial from someone that is used with all the quirks.

This is not to say that the issue is with JS itself or it's ecosystem, it may be or not, but this little anecdote is what I can share from this experience. I hope this is just an exception.

Re:Roadmap to becoming a web developer in 2017 by cholantesh on Monday March 27, 2017 @06:13PM (#13972301)
I'm 28 myself, with experience primarily in web and ETL. I'm finding that even the big orgs are doing buzzword fishing on their jobs descriptions. MV* frameworks for largely static sites and data sets, served up to small, internal audiences, etc.

Strongly weighing my options for moving into another space such as embedded systems or DSP, where the problems are a bit more tangible.

Re:Roadmap to becoming a web developer in 2017 by marknadal on Monday March 27, 2017 @06:01PM (#13972222)
I highly agree, and have strongly voiced "keeping things simple" with:

1. HTML4 (no special/new tags) Edit: CSS, of course (unfortunately, CSS is a pain to learn though, so get a lot of experience/experimenting)

2. Pure ES5 JavaScript (don't waste time with build-steps/compiling JS, that defeats the point/purpose - or if you want to, learn a language like ClojureScript or Elm/Haskell)

3. jQuery to manipulate the DOM (skip frameworks and stick to libraries, this will force you to actually understand JS rather than being a copy-paster. Once you have this down, build your own personalized framework to abstract things away, only then should you try experimenting with Angular/React, etc. others)

4. Notepad++ or Sublime (avoid using any terminal tools, including NodeJS, until you are comfortable with having a browser and an editor open side by side, and refreshing when making changes. Keep it simple: just files!)

5. NodeJS or PHP, GitHub for Desktop (learn basic command line use, but if something takes you more than 20 minutes to figure out, seek out a community/forum/help that is friendly and encouraging to newbs. Don't waste time on channels that make fun of you for not knowing command line.)

6. Heroku (for deploying, and having your page live to show your mom what you built)

I wrote a beginner's tutorial for the first 3 items, it takes between 5 minutes to 30 minutes for people who have only played with a little bit of HTML. It teaches you how to build a ToDo app: http://gun.js.org/think.html , let me know if there is anything I can do to improve it.

Re:Roadmap to becoming a web developer in 2017 by et-al on Monday March 27, 2017 @07:11PM (#13972642)
CSS needs to be included. CSS is the polish that changes a proof of concept into a presentable product.

There's a number of Show HN projects that I'm hesitant to invest much time in because they look like the author won't bother maintaining them months down the line. Even your nicely made tutorial has CSS. ;)

btw feedback:

* For some reason it wasn't evident to me that the left black box was editable and I actually interacted with the right-side wondering why nothing was happening. Perhaps use something that doesn't have an interaction so I don't try to click the button at first glance.

* Found myself scrolling up and an down a lot to read the next few instructions and updating the code. If things were side by side, this would be easier.

* It'd be nice to step backwards for the instructions

* The pre-formatted code in the instructions is a bit small. Might be hard to read for some people

Re:Roadmap to becoming a web developer in 2017 by gingerbread-man on Monday March 27, 2017 @08:51PM (#13973081)
I would happily pay a consultant $300 an hour to do the CSS for my websites. I imagine someone who specialized in CSS could do in 10 minutes what would take me several hours of googling and hair-pulling frustration.
Re:Roadmap to becoming a web developer in 2017 by doublerebel on Tuesday March 28, 2017 @11:37AM (#13977493)
I will do this for you in one-hour minimums. Just send me the list of wants and the git URL+creds or tarball/zip. Contact me through any channel, satisfaction guaranteed.
Re:Roadmap to becoming a web developer in 2017 by flukus on Tuesday March 28, 2017 @02:00AM (#13974459)
I wonder how many can work in CSS these days? The proliferation of CSS frameworks/compilers is nearly as bad as javascript.
Re:Roadmap to becoming a web developer in 2017 by namanyayg on Tuesday March 28, 2017 @05:04AM (#13975135)
How can I apply?
Re:Roadmap to becoming a web developer in 2017 by marknadal on Monday March 27, 2017 @07:29PM (#13972740)
Oh you are so right, my bad, CSS of course - updating my original post, I just blanked.

Those are good points - I need to figure out how to fit the instructions in while still having space for the editor and others. And yes to the others, I'll try to get them incorporated. Thank you!!!

Re:Roadmap to becoming a web developer in 2017 by devNoise on Monday March 27, 2017 @07:15PM (#13972667)
For #3, I say skip jQuery and go with Vanilla JavaScript ala https://javascript30.com

Every green browser have pretty good JavaScript support. document.getElementById will be your friend.

Re:Roadmap to becoming a web developer in 2017 by marknadal on Monday March 27, 2017 @07:34PM (#13972767)
This looks great!! Will have to peek at it more myself.

As you can tell, I'm a vanilla fan myself. Although I do think the DOM is still unnecessarily verbose - that aside, `innerText` still is not cross browser, so for that reason alone I recommend jQuery `$("#id").text("foo")` to discourage use of `.innerHTML` :( .

Re:Roadmap to becoming a web developer in 2017 by Rumudiez on Monday March 27, 2017 @11:07PM (#13973731)
Why is innerText not cross browser? According to caniuse it's been in every major version of every popular browser for over a year.[0]

[0] http://caniuse.com/#search=innerText

Re:Roadmap to becoming a web developer in 2017 by marknadal on Tuesday March 28, 2017 @03:33AM (#13974779)
Oh hmmm, I thought I tried it just the other month and it wasn't working. Maybe I hadn't updated IE, but I thought it was the whole Edge/11 split problem. Thanks for correcting me!
Re:Roadmap to becoming a web developer in 2017 by duderific on Monday March 27, 2017 @08:36PM (#13973004)
To my mind, using innerHTML is far better than including a 32K library just to avoid using it.
Re:Roadmap to becoming a web developer in 2017 by jhall1468 on Tuesday March 28, 2017 @12:13AM (#13974009)
This is especially true if you want to apply for a job some day. Programming interviews are going to expect plain old javascript, not a framework-oriented approach. More importantly, jQuery is a tool. Know what you're making before you bother with a tool that makes it easier.
Re:Roadmap to becoming a web developer in 2017 by lazyasciiart on Tuesday March 28, 2017 @05:38AM (#13975254)
Not the programming interviews I've been in (on both sides).
Re:Roadmap to becoming a web developer in 2017 by frik on Tuesday March 28, 2017 @05:12AM (#13975160)
I agree with you. Though, call it HTML5. CSS3 is OK, but so are Html tables. JS5 is lean and fine, I don't need the class syntactic sugar.
Re:Roadmap to becoming a web developer in 2017 by cm2187 on Monday March 27, 2017 @06:16PM (#13972324)
The most important skill is to brag about using a javascript framework that no one else has heard about in order to make everyone anxious that they are has-been already.
Re:Roadmap to becoming a web developer in 2017 by cblock811 on Monday March 27, 2017 @06:13PM (#13972302)
Echoing others here, definitely just pick somewhere and get started. Spending time worrying about making the "right" decision is the worst thing you can do. I made that mistake when I was teaching myself and it cost me a few weeks until I finally just picked a language and went with it.
Re:Roadmap to becoming a web developer in 2017 by dorian-graph on Monday March 27, 2017 @05:59PM (#13972211)
You don't need to learn everything on there. Also, while some company may use/follow x (especially CSS methodologies), from what I've seen it's usually a poor attempt making it a lot easier to pick up.