I have been a back-end Java dev all my life and have been occasionally been thrown into the front-end side during a release or when "Huston, we have a problem" situation and I end up being a full stack dev for that project unofficially. Here are my 2 cents...
1) It takes me quite some time to understand the project structure depending on the front-end tech stack being used. 95% of the time, I end up questioning why is the structure different from the previous project.
2) Does not matter if you are a front-end dev. Big O matters. I have a hard time turning a blind eye to the monstrous O(n2) functions written when it can be done in O(n log n) or maybe even linearly. I finally end up spending late nights in the office optimizing the code. (This does not mean all front-end devs are like this... just my experience)
3) Every front-end team has their own code styling/formatting techniques. Call me a sucker on this, but I have been using Google Code style and their naming conventions for a long time. It freaks me the f*&k out when I see a variable being declared differently in different projects. I have seen user_name, userName, username and UserName being used. Pick one folks.
4) This is again got to do with me; when trying to help out in the "Houston, we have a problem situation" I have been told I need to be creative and productive at the same time. Excuse me, but last time I checked, you needed help. I may not have the best UI/UX sensibility as the front-end devs, but I am doing the best I can to help you out. A bit of "do it like this" would be more helpful , rather than "you should be more creative and productive".
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.
I have been a back-end Java dev all my life and have been occasionally been thrown into the front-end side during a release or when "Huston, we have a problem" situation and I end up being a full stack dev for that project unofficially. Here are my 2 cents...
1) It takes me quite some time to understand the project structure depending on the front-end tech stack being used. 95% of the time, I end up questioning why is the structure different from the previous project.
2) Does not matter if you are a front-end dev. Big O matters. I have a hard time turning a blind eye to the monstrous O(n2) functions written when it can be done in O(n log n) or maybe even linearly. I finally end up spending late nights in the office optimizing the code. (This does not mean all front-end devs are like this... just my experience)
3) Every front-end team has their own code styling/formatting techniques. Call me a sucker on this, but I have been using Google Code style and their naming conventions for a long time. It freaks me the f*&k out when I see a variable being declared differently in different projects. I have seen user_name, userName, username and UserName being used. Pick one folks.
4) This is again got to do with me; when trying to help out in the "Houston, we have a problem situation" I have been told I need to be creative and productive at the same time. Excuse me, but last time I checked, you needed help. I may not have the best UI/UX sensibility as the front-end devs, but I am doing the best I can to help you out. A bit of "do it like this" would be more helpful , rather than "you should be more creative and productive".