As a full stack developer, the patience to finish a screen on the frontend is the toughest part in my opinion. Finishing implementing a design can be tedious and require detailed thinking / patience. Whereas on the backend, it's much easier to get things done and move onto the next objective. It's also less subjective, frontend is subject to more opinions on design. While there can be architecture debates on the backend, frontend design can be more of a slough. The payoff to nail a workflow or have a user go through a delightful interface that solves their problems is worth it though.
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.
As a full stack developer, the patience to finish a screen on the frontend is the toughest part in my opinion. Finishing implementing a design can be tedious and require detailed thinking / patience. Whereas on the backend, it's much easier to get things done and move onto the next objective. It's also less subjective, frontend is subject to more opinions on design. While there can be architecture debates on the backend, frontend design can be more of a slough. The payoff to nail a workflow or have a user go through a delightful interface that solves their problems is worth it though.