3 ms·

You jump around jobs and see where it gets you. Eventually, you realize how to pick and choose your tech. I got real burn out with front end, with emberjs, ang

You jump around jobs and see where it gets you. Eventually, you realize how to pick and choose your tech. I got real burn out with front end, with emberjs, angularjs, and now react. I'm going to just wait this out until ES6 come about and see where that go. I think in general I moved toward back end with all the big data and data science is going to be at. And now I'm going back to school to become a data science practicioner. The trick is to have enough experiences and understanding overall concepts. I've done a variety of MVC in different languages and was thrust upon to do frontend and all that jazz. Those experiences will help you solve problem easier and hone your skill set in finding solutions. I've seen people talking about how full stack is unicorn. I'm a full stack, I'm experienced in many technologies, master of none but a very small subset. I am constantly surprise how I am way more qualified than some of those frontend programmers or architecturers out there. The deal is just continue to gain experiences on variety and you'll hone your problem solving skill. You might also be under selling yourself too. There are very few engineers out there and there are tons of pretenders. I've worked with two "front end" and a "acting cto" that specialized in architecture. They were anything but the position they claim to be but they sure do have a purrty linkedin profile with tons of people writing good things about them.

eropple 12y ago
> I've seen people talking about how full stack is unicorn. I'm a full stack but I'm experienced in many technologies Can you debug your runtime (Ruby, Python, the JVM, whatever) in gdb? I can, and I still don't consider myself "full-stack"--both because I leave JavaScript to JavaScript people, but also because if you asked me to debug a kernel I'd look at you and just shrug. The stack goes down past your application.
- richthegeek 12y ago
  Full stack to me means "Given a design and a brief, can turn it into a reality with no external help". So for me that's HTML, CSS (Less/Sass), JS (React, Angular, jQ), on the frontend and then a choice between Node, PHP, Ruby, or Python plus DBMS on the backend depending on the requirements / my mood. The only bits that really extend beyond that are interfacing with external libraries such as ffmpeg, imagemagick etc. I've not seen any instances of full-stack implying heavy dev-ps experience for example. And that's in 12 years of pissing my life away being a "full-stack" developer. Heck, right now I'm employed as a "front-end web developer" and spent last week writing an API-only Node app and configuring TC/Azure deployments and NginX. Anyway, got a bit off track here... my original point was that "full stack" is pretty well defined and has been for a long time.
  - eropple 12y ago
    If you think running gdb when something breaks is "devops", we may simply not have compatible vocabularies. I consider it a fairly foundational part of making a product that works.
    - richthegeek 12y ago
      I wasn't saying gdb was devops, I meant stuff to do with administering server clusters for high traffic sites or otherwise-complex setups. The line generally gets drawn at "Does it run on one server?", in my experience. I suspect if Docker pans out like it wants to that will change though, but perhaps that's my naiivety showing through
- mtbcoder 12y ago
  True, but then really no one could be considered a "full stack" developer. Personally, I consider "full stack" to be just a blanket statement to mean people who have no problems wearing different hats and can figure things out to get the job done. Unless they've been pigeon-holed their entire careers due to enterprise specialization or are just that closed-minded to learning new things, I think most good developers end up becoming "full stack" after enough time.
  - eropple 12y ago
    I think "full-stack" means, when translated out of marketspeak, "you won't get any support or help from anyone else, so you'd better be self-sufficient at all things." But I am a cynic.

eropple 12y ago

> I've seen people talking about how full stack is unicorn. I'm a full stack but I'm experienced in many technologies Can you debug your runtime (Ruby, Python, the JVM, whatever) in gdb? I can, and I still don't consider myself "full-stack"--both because I leave JavaScript to JavaScript people, but also because if you asked me to debug a kernel I'd look at you and just shrug. The stack goes down past your application.

richthegeek 12y ago
Full stack to me means "Given a design and a brief, can turn it into a reality with no external help". So for me that's HTML, CSS (Less/Sass), JS (React, Angular, jQ), on the frontend and then a choice between Node, PHP, Ruby, or Python plus DBMS on the backend depending on the requirements / my mood. The only bits that really extend beyond that are interfacing with external libraries such as ffmpeg, imagemagick etc. I've not seen any instances of full-stack implying heavy dev-ps experience for example. And that's in 12 years of pissing my life away being a "full-stack" developer. Heck, right now I'm employed as a "front-end web developer" and spent last week writing an API-only Node app and configuring TC/Azure deployments and NginX. Anyway, got a bit off track here... my original point was that "full stack" is pretty well defined and has been for a long time.
- eropple 12y ago
  If you think running gdb when something breaks is "devops", we may simply not have compatible vocabularies. I consider it a fairly foundational part of making a product that works.
  - richthegeek 12y ago
    I wasn't saying gdb was devops, I meant stuff to do with administering server clusters for high traffic sites or otherwise-complex setups. The line generally gets drawn at "Does it run on one server?", in my experience. I suspect if Docker pans out like it wants to that will change though, but perhaps that's my naiivety showing through
mtbcoder 12y ago
True, but then really no one could be considered a "full stack" developer. Personally, I consider "full stack" to be just a blanket statement to mean people who have no problems wearing different hats and can figure things out to get the job done. Unless they've been pigeon-holed their entire careers due to enterprise specialization or are just that closed-minded to learning new things, I think most good developers end up becoming "full stack" after enough time.
- eropple 12y ago
  I think "full-stack" means, when translated out of marketspeak, "you won't get any support or help from anyone else, so you'd better be self-sufficient at all things." But I am a cynic.