But you're talking about "Full Stack" as every technology ever and that's not accurate. When you talk about a FULL STACK (don't care if Junior, Senior, or whatever), you're talking about someone who manages at least one programming stack. For example, a MEAN Full Stack developer is someone who knows the FULL MEAN STACK (Mongo, Express, Angular, Node), or a LAMP Full Stack Developer is someone who knows the full LAMP STACK (Linux, Apache, MySQL, Php).
Specify it for tutorials - yes.
Specify it for your job title... I'd argue no.
I'm a full-stack developer. On my CV, in the description, I'll outline WHICH stack. But not in the title. "Fullstack developer" is still a valid title at any level. Most company's will only use 1 stack type, so having you specify your stack in your title would be unnecessarily convoluted.
But you're talking about "Full Stack" as every technology ever and that's not accurate. When you talk about a FULL STACK (don't care if Junior, Senior, or whatever), you're talking about someone who manages at least one programming stack. For example, a MEAN Full Stack developer is someone who knows the FULL MEAN STACK (Mongo, Express, Angular, Node), or a LAMP Full Stack Developer is someone who knows the full LAMP STACK (Linux, Apache, MySQL, Php).
You have a point: if you are proficient in one stack, then why donβt you specify it?
Specify it for tutorials - yes.
Specify it for your job title... I'd argue no.
I'm a full-stack developer. On my CV, in the description, I'll outline WHICH stack. But not in the title. "Fullstack developer" is still a valid title at any level. Most company's will only use 1 stack type, so having you specify your stack in your title would be unnecessarily convoluted.
Yeah, that's important! You should specify what stack you've been working on