14
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Feb 2024
14 points (100.0% liked)
CSCareerQuestions
943 readers
12 users here now
A community to ask questions about the tech industry!
Rules/Guidelines
- Follow the programming.dev site rules
- Please only post questions here, not articles to avoid the discussion being about the article instead of the question
Related Communities
- !programming@programming.dev - a general programming community
- !no_stupid_questions@programming.dev - general question community
- !ask_experienced_devs@programming.dev - for questions targeted towards experienced developers
Credits
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
Well yea, that's usually the point of full stack. If you want to do something like that, you probably want to work a smaller scale company... Like if you're in a team of 5 people, the situation arises of "Oh sysop thing needs to be done, who to ask? I guess @RonSijm (backend dev) is close enough..."
So to have a junior full stack is pretty counterintuitive. Otherwise the situation arises of "Oh xyz needs to be done, who to ask? - Well be have a dedicated senior backend engineer, a dedicated senior front-end engineer, dedicated senior sysops.... 'Oh let me ask @velox_vulnus@lemmy.ml, this junior full-stack'" - yea no.
Why are you aiming to be an intern/early-career full-stack engineer? The only kinda company I can think of where something like that would be something with barely any IT, where you're just the "jack of all trades" goto guy for IT stuff - so that you can be the one-man army that does everything
So honestly I'd focus on one area first - backend, frontend, dev/sys-ops - especially as you're mentioning
Yea that gets even worse when you have worry about the entire stack, and work with an entire stack of components you're not really familiar with. If you're at least somewhat senior in one part - lets say backend - at least you're in a position of "Ok, I have a backend that I'm comfortable about" - "Now lets see if I can make a frontend for it" - or - "Lets see if I can manage to dockerize this, and host it somewhere."
And if you know the fundamentals of one stack-part first (data-structures, design patterns, best practices) - you can apply that knowledge to other areas and expand from there
Because I'm applying to startups. The barrier to entry for corporate jobs is very high - what I mean is that there's too much of us. In such situations, people will ask recruiters who happen to be their blood relatives or neighbors to recommend them. But I do not have that privilege. And the problem with startup is poor pay, with too much skill requirement. The poor pay is still understandable, but what's understandable is the high skill requirement.
Yea, that's the problem with startups, they're poor, so by their logic "we only have money for 1 person" - "so if we hire a full stack that does everything, that's cheapest." - "What is the cheapest dev? An intern / junior." - "So what if we get a junior full stack :bigbrain: "
And then they create a vacancy for a CEO that can build their entire start-up and label it a junior-full-stack