Skip to main content
21 events
when toggle format what by license comment
May 25, 2020 at 6:00 history tweeted twitter.com/StackWorkplace/status/1264798356955635713
May 22, 2020 at 2:05 comment added Nelson @Damouse I think I can be considered a full-stack developer, but I wouldn't take on a full-stack position without major research. The biggest problem is whether the manager has even the slightest clue on what you are suppose to be doing, and at what point you need help. Full-stack roles are frequently mismanaged and higher-ups expect FULL expertise on ALL the roles, not a jack-of-all-trades with support. That is the main reason why I see "full-stack" roles as red flags because they expect one guy to fully perform all the roles, and somehow work 30 hours a day.
May 21, 2020 at 22:32 comment added Damouse @Nelson I mean, I know and work with people who can do this. Perhaps their depth is not the same as a specialist of the same ability, but generally they are highly capable across the stack, and that integrated skillset has its own advantages. Perhaps you think its unreasonable to hire for this kind of skillset, but my experience is that these people do exist.
May 21, 2020 at 2:14 comment added Nelson @Damouse They're very worth using, but they are complex enough to be a full-time position all by itself. You cannot realistically understand the nuances of the entire umbrella of JS (now both front-end and back-end with NodeJS), and all 200+ flavors of NoSQL. You can't possibly memorize everything about the entire "full-stack" ecosystem without scrambling things up in your head.
May 21, 2020 at 0:15 comment added Damouse @Luaan I'm not sure I understand your comment-- are you implying the complexity of the frontend frameworks are too high to be able to cross-train into something else, or that they're not worth using?
May 20, 2020 at 13:35 answer added bob timeline score: 3
May 20, 2020 at 12:31 history removed from network questions Neo
May 20, 2020 at 7:59 comment added Luaan @Nelson Yeah. If the "full-stack" position mentions anything about React, Angular and such, run away. If it's old-school full-stack, where the front-end is just a pretty thin shell for the back-end on some in-house inventory system, that's fine - if you don't mind working on such a project.
May 20, 2020 at 7:14 comment added Thomas I do not fully agree with this matrix, but it can be a starting point to understand what some people consider experienced: sijinjoseph.com/programmer-competency-matrix
May 20, 2020 at 2:38 comment added Nelson And "full-stack" developer positions are now becoming a red flag for me. They're cramming in at least 3 roles. With all the front-end frameworks and back-end frameworks, I find it is almost 4 positions before I even do anything related to DB access. Throw in Cloud DBs, and NoSQL, and we're talking easily 6-7 roles.
May 19, 2020 at 17:31 history became hot network question
May 19, 2020 at 13:35 answer added Philipp timeline score: 8
May 19, 2020 at 10:52 answer added gnasher729 timeline score: 25
May 19, 2020 at 10:30 vote accept blindShrug
May 19, 2020 at 10:28 history edited blindShrug CC BY-SA 4.0
deleted 3 characters in body
May 19, 2020 at 10:27 comment added Solar Mike Less than 2.5 years experience... and "experience" varies...
May 19, 2020 at 10:05 review Close votes
May 23, 2020 at 4:56
May 19, 2020 at 10:02 comment added Philip Kendall "I started my career as a Software Engineer back in February 2018". Even given my comments on how years of experience are meaningless, you do not have three years of experience. The very worst thing you can do is to lie about it.
May 19, 2020 at 9:52 answer added Philip Kendall timeline score: 81
May 19, 2020 at 9:38 answer added virolino timeline score: 0
May 19, 2020 at 9:30 history asked blindShrug CC BY-SA 4.0