Personally, I like "backend," but it breaks down like this:
Frontend involves a lot of UX/UI design, heavy user-oriented thinking, and a love of making things "pretty," practical, effective, and easy-to-use. It's as much art as it is programming (which I argue is an art anyway, but I digress.) In other words, Frontend is user-first orientation.
Backend involves significant work with data storage and processing, file IO, system integration, performance, and stability. It's the nuts and bolts. Or, to put it briefly, Backend is data-first orientation.
In either case, you have to be comfortable with designing around BOTH users and data, but each is definitely heavier on one than the other.
NOTE: This is coming from a desktop application and library developer, not a web developer (usually), but IME, it's the same in both realms.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Personally, I like "backend," but it breaks down like this:
Frontend involves a lot of UX/UI design, heavy user-oriented thinking, and a love of making things "pretty," practical, effective, and easy-to-use. It's as much art as it is programming (which I argue is an art anyway, but I digress.) In other words, Frontend is user-first orientation.
Backend involves significant work with data storage and processing, file IO, system integration, performance, and stability. It's the nuts and bolts. Or, to put it briefly, Backend is data-first orientation.
In either case, you have to be comfortable with designing around BOTH users and data, but each is definitely heavier on one than the other.
NOTE: This is coming from a desktop application and library developer, not a web developer (usually), but IME, it's the same in both realms.