this post was submitted on 26 Apr 2024
61 points (89.6% liked)
Asklemmy
43138 readers
1313 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That is a compliment. The separation of front end developer and back end developer is obsolete and untrue. Either you are a developer or not. If you work on web, then you must, now or in the future, know how web browsers work, how APIs work, how to write and consume them, etc. The browser is just an API we consume from JS. There are many others.
I'm not going to write .Net, you can't make me do it. I'm not going to write Python, you can't make me do it.
Is your backend Node?!? Let's go baby, I'm a full stack dev.
If you're not being sarcastic, why limit yourself to only one thing? If you're working on some amazing UI with tons of CSS animations and a full audiovisual experience, and it takes intimate knowledge of everything frontend, I guess it would make sense. But if you're just making internal CRUD apps, I don't see a reason why a given domain is special enough to have its own job title.