11–20 of 108 posts
I think you're confusing Javascript Developer and Front End Web Developer. The two are mutually exclusive.
Though I do agree the subject of this article would be more suitable if it were Front End Web Developer as opposed to JS Developer.
He mentions using (1) vi or emacs instead of (2) Textmate or notepad. I wasn't aware that one could use (2) in place of (1). How is that done? Does one need to SFTP a text file from the server to a client GUI OS, modify it, and then SFTP it back?
Textmate has some kind of support for automatic remote editing, I don't know the details.
Cyberduck + Textmate is a joy.
He mentions using (1) vi or emacs instead of (2) Textmate or notepad. I wasn't aware that one could use (2) in place of (1). How is that done? Does one need to SFTP a text file from the server to a client GUI OS, modify it, and then SFTP it back?
However, editing live is bloody idiotic. Use git locally and live-deploy based on tags/branches.
I think you're confusing Javascript Developer and Front End Web Developer. The two are mutually exclusive.
They tested me on front end shit. And thinks that javascript is only front end.
While there are many down falls with node.js it still pay the bill, interest tech, and I wish people would realized that just cause you program js you doesn't imply that you want to do front end.
I hate front end. It's just not for me.
Did I misunderstand something, or does this article just list all the reasons it's a bad idea to be a JavaScript developer? (apart from the 99 reasons that is JavaScript itself) basically: you use a language that is the envy of noone, to work with things like web browsers, the DOM and CSS. Anyone would want good money to do that...
To get to the level the author is talking about is quite daunting. I feel that JS is sort of a second class citizen to most back-end developers. Web projects which are touched by an HTML / CSS developer, a designer and a back-end developer are common (not always a team, maybe they are all contracted to do their bits as needed and don't work closely together.) Often the heavy lifting with the JS goes to the back-end dev because the HTML / CSS dev isn't really a programmer beyond Googling for Jquery snippets. The problem is, the back-end developer usually isn't a JS wizard either. A lot of developers I come across make a mess of copy and paste in the JS. And I don't spend enough time in JS for it to feel natural to me. If I could add one superpower to make my life way easier, it would be the things the author is talking about.
I see a lot of threads with people asking what to learn. If you are going to be a web developer, then JS is always a damn good answer (or if you already know JS, go back and level up.) I really love to spend time on the server side. I want to put my time into Linux, spend a lot of time in Go and learning other languages. But that doesn't make a lot of sense for a freelance web developer.
ETA: Actually, high in demand is probably the wrong way to put it. You don't have to be in high demand. Small markets can be as lucrative or better than much larger markets. And then there the fact that there is a lot more to being a successful web developer than being a code-monkey. But the things the author described is certainly a super power in web development.
I think I'm a solid frontend developer, but I'm a few years professional experience away from the level he describes here. I know my way around HTML, CSS and the various browser quirks - though I'm still learning the idiosyncrasies he describes here. I've written a ~10000-line app in Angular.js, but my Javascript code is still sloppy, and is nowhere close to my knowledge of Ruby. I'm gradually picking up the basics of design and UI as I go, but that's a whole other mountain which I could climb for years.
"That guy I offered that car to (not really) took a job at a startup and he’s the guy. He’s THE front end developer for their product which doesn’t exist yet. He gets to point to that thing, a year or two from now when it’s worth a bazillion dollars (I do wish him luck, after all) and say, “I did that.” There are people out there, right now, who get to point at Twitter, Facebook, Gmail and Google Maps, at the Iphone’s UI, at Github, at the YouTube player – stuff used by millions upon millions of people – and say, “I did that.”"
Thing is, few products are built by one superhero. I'm wondering if, rather than transform yourself into a magical-unicorn designer/hacker - it might be better to get solid at development, solid at design, but aim to only get good enough that you can manage people who are better at you in those areas?
I think you're confusing Javascript Developer and Front End Web Developer. The two are mutually exclusive.
I applied for a backend and told them I did node.js and does javascript dev (which they were looking for). They tested me on front end shit. And thinks that javascript is only front end. While there are many down falls with node.js it still pay the bill, interest tech, and I wish people would realized that just cause you program js you doesn't imply that you want to do front end. I hate front end. It's just not for m…
I think you're confusing Javascript Developer and Front End Web Developer. The two are mutually exclusive.
Both require their own specializations. I wouldn't say they're mutually exclusive, just that while the constant is Javascript the language, the environments are widely different.
Stay away from any job posting that asks for ninjas, rock stars or bad asses.