I don't know about Go, but Django is relatively popular. It's a stretch, but I could see it being useful there. But we might as well include any language that has a Web framework then.
Don't like seeing a bullet point like "MySQL and NoSQL" after "Postgres" and "MongoDB". This kind of thing breaks the category pattern, and makes me wonder if the author knows what NoSQL is.
As a working full stack developer, I can definitely say that to my employer, that is what makes the difference between me being a full stack developer and a web developer.
They seem to have removed Go from the frontend list, but they have PHP and Node in the list too. If I was doing purely frontend dev, I wouldn't expect to have to use Node or PHP.
The idea of being a full stack developer has been around for a while. It's good but it only covers one dimension - the vertical.
The real win is to go horizontal. The same people do market analysis, design coding, testing, and prod support. We can't all be experts, but most of us can develop enough skill to do this. The elimination of hand-offs removes delay and miscommunication.
The article is horrible, don't bother clicking through.
But the 'full-stack developer' is an interesting beast. Web development is obscenely complex, that inherent complexity is compounded by developers that don't take the domain seriously and designers that should probably just stick to Photoshop.
My feet-first introduction to 'real' front-end was fixing a designer's awful HTML / CSS over the objections of the client who wanted me to just let him do his job. I had to redo the layout and re-style the whole project, because it wouldn't work at all with IE's box model. Took a whole day and at the end of it the client admitted I was right and we were able to move on. There was no way the designer was ever going to fix his broken code.
I feel like "full-stack" is this year's "rockstar", "ninja", "10x" programmer. Weasel words that employers use in the sole aim of short-staffing their departments.
21 comments
[ 4.3 ms ] story [ 56.9 ms ] threadWait. Hold the phone. What's SASD? Styles And Stuff, Dog?
Million-dollar idea.
Should You Even Read This?
Frontend:
* CSS, CSS3, and SASD # I assume that is supposed to be SASS?
* Go # Why for a front end engineer? It's not even on the backend list.
* Python # Why? It's a nice to have for general scripting but not required for frontend work
Backend:
* C and C++ # Not generally important for full stack web dev
* Ruby on Rails # Why is Rails in the middle of a list of languages? The language is Ruby
* Perl # Why? may be useful but not a must know
* MySQL and NoSQL # Why is MySQL contrasted with NoSQL?
As a working full stack developer, I can definitely say that to my employer, that is what makes the difference between me being a full stack developer and a web developer.
The real win is to go horizontal. The same people do market analysis, design coding, testing, and prod support. We can't all be experts, but most of us can develop enough skill to do this. The elimination of hand-offs removes delay and miscommunication.
But the 'full-stack developer' is an interesting beast. Web development is obscenely complex, that inherent complexity is compounded by developers that don't take the domain seriously and designers that should probably just stick to Photoshop.
My feet-first introduction to 'real' front-end was fixing a designer's awful HTML / CSS over the objections of the client who wanted me to just let him do his job. I had to redo the layout and re-style the whole project, because it wouldn't work at all with IE's box model. Took a whole day and at the end of it the client admitted I was right and we were able to move on. There was no way the designer was ever going to fix his broken code.
I feel like "full-stack" is this year's "rockstar", "ninja", "10x" programmer. Weasel words that employers use in the sole aim of short-staffing their departments.
What about concepts? Like distributed systems? Big-O? thread safety?