5 ms·

"Full stack engineer" is the new "Coding Ninja". It doesn't mean anything. It is most often used by non-technical founders who just want to hire one guy to do

by dudul 11y ago

"Full stack engineer" is the new "Coding Ninja". It doesn't mean anything. It is most often used by non-technical founders who just want to hire one guy to do the work of 3. As you said "How full is the stack?" Do you need to know how to setup and administer servers? Do you need DevOps skills? Do you need to be able to write backend/frontend code? Do you need to know how to design the UX as well? I systematically ignore all positions for "full stack engineer" because in my mind it translates to "we don't know computers but we have a Great Idea(tm) and we just want some nerdy guy to handle all these computer thingies for us".

dozzie 11y ago
> "Full stack engineer" is the new "Coding Ninja". It doesn't mean anything. > Do you need DevOps skills? Certainly, as the "DevOps skills" means the same as "full stack engineer": nothing.
- dudul 11y ago
  Well, DevOps is definitely an over-used buzzword, but I think it's a good term to use as an umbrella for technologies like Chef, Puppet, Ansible, etc. It is definitely a different skillset than the one required to write software. I think DevOps gets a bad reputation mostly because of companies who just use it to look cool without really embracing the "infrastructure-as-code" philosophy (a bit like Agile/Scrum "we do Scrum, but...")
  - dozzie 11y ago
    > I think it's a good term to use as an umbrella for technologies like Chef, Puppet, Ansible, etc. No. Those already have their umbrella term: infrastructure as a code. You even mention it yourself.
    - davelnewton 11y ago
      That clearly takes too long to say. DevOps covers more than just "infrastructure as code", though.
      - PaulHoule 11y ago
        I would say it is a viewpoint I attained from doing web projects for various "startups" and "internal startups" starting in 1999 or so. In these cases you have very small teams so you can't afford to have separate DBA, Sysadmin, Network Operations, and Development people -- at least not entirely. When you've had experience doing everything yourself I think that makes you a better team member. For instance I write very solid server code because I hate being woken up at 3AM.
        davelnewton 11y ago
        Sure, knowing all the things makes you a better team member. But all this is orthogonal to what was being discussed. DevOps is a thing, and the skillset(s) are not necessarily the same. Similarly anecdotal; I'm a pretty decent dev. I'm not a decent ops person for a variety of reasons, the biggest being a complete lack of interest. Would knowing more about ops make me a better team member? Maybe marginally, but we have devops people that don't have to concern themselves with application code, and apps people that don't have to concern themselves with (almost any) of deploy/ops details. That makes us more efficient, because we don't have to know all the things, and can actually have time to focus.
        dozzie 11y ago
        Oh, so you have devops people and dev people. How strange, given what's typically behind devops buzzword.

by dudul 11y ago

dozzie 11y ago

> "Full stack engineer" is the new "Coding Ninja". It doesn't mean anything. > Do you need DevOps skills? Certainly, as the "DevOps skills" means the same as "full stack engineer": nothing.

dudul 11y ago
Well, DevOps is definitely an over-used buzzword, but I think it's a good term to use as an umbrella for technologies like Chef, Puppet, Ansible, etc. It is definitely a different skillset than the one required to write software. I think DevOps gets a bad reputation mostly because of companies who just use it to look cool without really embracing the "infrastructure-as-code" philosophy (a bit like Agile/Scrum "we do Scrum, but...")
- dozzie 11y ago
  > I think it's a good term to use as an umbrella for technologies like Chef, Puppet, Ansible, etc. No. Those already have their umbrella term: infrastructure as a code. You even mention it yourself.
  - davelnewton 11y ago
    That clearly takes too long to say. DevOps covers more than just "infrastructure as code", though.
    - PaulHoule 11y ago
      I would say it is a viewpoint I attained from doing web projects for various "startups" and "internal startups" starting in 1999 or so. In these cases you have very small teams so you can't afford to have separate DBA, Sysadmin, Network Operations, and Development people -- at least not entirely. When you've had experience doing everything yourself I think that makes you a better team member. For instance I write very solid server code because I hate being woken up at 3AM.
      - davelnewton 11y ago
        Sure, knowing all the things makes you a better team member. But all this is orthogonal to what was being discussed. DevOps is a thing, and the skillset(s) are not necessarily the same. Similarly anecdotal; I'm a pretty decent dev. I'm not a decent ops person for a variety of reasons, the biggest being a complete lack of interest. Would knowing more about ops make me a better team member? Maybe marginally, but we have devops people that don't have to concern themselves with application code, and apps people that don't have to concern themselves with (almost any) of deploy/ops details. That makes us more efficient, because we don't have to know all the things, and can actually have time to focus.
        dozzie 11y ago
        Oh, so you have devops people and dev people. How strange, given what's typically behind devops buzzword.