3 ms·

I self-describe as a full-stack web developer because I've worked on both the front-end and back-end without distinction, and have no particular preference to w

• Silhouette 13y ago
  Is this considered a bad thing? On the contrary, I would describe it as normal, in the sense that all of these web technologies are just tools and protocols. Any software developer with broad experience ought to be looking at general software architecture principles and programming techniques and testing strategies and all the rest and then choosing whatever tools help them get the result they need. "Front-end developer" and "back-end developer" always seem like "C programmer" or "Python programmer" to me: they're job titles you use when you don't have enough experience with different tools and techniques yet to drop the qualifiers and just call yourself a web developer or programmer. And those in turn are just titles you use until you realise it's all about building something useful and the job title doesn't actually matter at all except perhaps as a convenient shorthand for initially finding people you can talk with intelligently about getting stuff done.
  • pyre 13y ago
    | a convenient shorthand for initially finding people | you can talk with intelligently about getting stuff | done. I agree. I mostly use the term "full-stack web developer" to convey the idea that my experience isn't confined to a niche of solely "front-end" or solely "back-end" development.