What exactly is Full Stack these days?
21–30 of 45 posts
Re: What exactly is Full Stack these days?
#22Re: What exactly is Full Stack these days?
#23Re: What exactly is Full Stack these days?
#24I've used every one of those technologies with the exception of Salt (Nothing against it, just have not used it). I don't think I am that much of a rare breed. Some of the AWS technologies many would not be exposed too, but learning an AWS build pipeline is not difficult if you have used competitors.
I don't think that is that crazy of a job description. If someone has focused on breadth of skill over depth, you are going to run across most of those technologies (With the exception of some of the AWS services I don't see that much).
Ive mostly worked for startups and its not uncommon for me to write front end modern javascript, build backends, orchestrate deployment pipelines and be involved in a sales call all in a single day.
I am very far from superman. Its pretty easy to be "Ok" at many technologies. Its pretty hard to be truly great at a single technology. I admire those who truly master a specific technology but I learned that my strength is breadth over depth. I am sure if a truly seasoned JS developer saw some of my frontend code they would have lots of suggestions for improvement, but that is fine by me. I can build stuff which meets the intended goals and generally everyone is happy.
Re: What exactly is Full Stack these days?
#25But I agree that the job requirements you gave as an example are insane, you can't be an expert in every stack of a product. At least not with the current implicit age requirement of the industry.
Re: What exactly is Full Stack these days?
#26Is that the job description for senior level+? It honestly doesn't sound unreasonable to assume a senior+ engineer to have experience with all of these technologies in this day and age. Software development tools have come a long way in the past decade and it's become possible for a generalist full stack dev to learn about and use every part of this (not having to be an expert in any, of course). I'd say the more pro…
So true re: binary search trees, merge sorts, and the like. I think web dev's need to realize their real world work has more to do with plumbing than it does dealing with programming puzzles.
Unless you're FB or operating at web scale.
Re: What exactly is Full Stack these days?
#27I fail to see the issue with this post. Frankly, if you are learning and willing to try new technologies across areas of the web dev stack you should have a grasp on 80% of these things at least (I didn't say expertise). What I am more surprised by is the unwillingness by many - indicated in the comments - to explore things outside their domain.
=========================================================
* Deep understanding of front-end JavaScript development using libraries such as React, Angular, etc.
Deep understanding of means you know these frameworks and libraries well. If you know these libraries well, you're a front end developer. The title front end developer exists solely because people need to focus exclusively in this area because the job is both challenging and complex.
* Expert in CSS/HTML5
Ok, not too crazy. But I wouldn't expect the Bootstrap guys to know sysadmin tools.
* Deep understanding of development using either Python, Node, or Ruby
So in addition to deep understanding of the front end, we also want someone deeply skilled in a general purpose programming language. AFAIK you can't have a deep understanding without being deeply skilled.
* Desire to pursue AWS Development Certifications toward expert-level achievement
Ok, so sysadmin/devops guy.
* Experience with orchestration tools such as Ansible, Salt, Chef, or Puppet
Sysadmin/devops guy.
* A balance of technical, business, and social/emotional intelligence
Basically we want someone that can do it all. Don't let all those requirements break your confidence. Leave that imposter syndrome at home!
========================================================
I wouldn't say it's an unwillingness. It's just not realistic. There's a reason cardiology and neurology are separate fields.
This job description to me doesn't read as "we're looking for someone who's handy". They want three people for one job. To me it's a bit appalling.
Re: What exactly is Full Stack these days?
#28What do you expect from a job these days? "Has skills in a single area"? To be honest, it's not that hard to gain a bit of familiarity with all this tech.
Re: What exactly is Full Stack these days?
#29Earlier quoted context omitted.
You need them to clarify deep understanding? If someone said they wanted a candidate to have a deep understanding of jet engines, I'd expect they know every single thing there is to know about them.
except we're not talking about jet engines - I was asking at what point does basic become deep, hence the next remark referring to 'years of experience' as a benchmark
Re: What exactly is Full Stack these days?
#30Lol idk if you’ve been doing this stuff for 20 years you’ll have those skills ¯\_(ツ)_/¯
More than likely someone with this sort of technical capacity doesn't score well in other areas.