4 ms·

Can some front-enders and UX devs answer these questions (this isn't a criticism - genuine datamining here): 1. How are your javascript test suits organised? D

Can some front-enders and UX devs answer these questions (this isn't a criticism - genuine datamining here): 1. How are your javascript test suits organised? Do you measure code coverage the same way? 2. Are there any standardised terms that you can use to convey stylistic concepts to other (front end)devs (excluding framework specific terms and html elements)? i.e. Software Design Patterns for code 3. Do you personally feel your field is more artistic or rigorous? 4. Do you personally think it should be artistic or rigorous? 5. (For reference) What is your job title? 6. Would you say you work more closely with the Tech Lead (or organisational equivalent) or Artistic Director (or organisational equivalent)? 7. What is your direct report's job title? 8. Are you able to suggest/implement global style changes on the basis of your own authority? 9. Do you maintain/contribute to any (front-end dev) documentation?

otras 8y ago
I'm a software engineer working mostly on the front end at a large tech company. For context, we have a separate UX team that works on design. Happy to give these my best. 1. Tests are organized around their component. This includes unit tests for any logic (though often we prefer to keep as much logic out of FE as possible) and screenshot tests for components. We also have larger-scale integration tests. 2. You mean like MVC (model-view-controller)? That's a pretty common one. 3. I'm not sure artistic is the antonym of rigorous. For example, math proofs are often both. I think it's better to characterize it as a craft. It's like being an electrician; sometimes your wires line up nicely, but sometimes you have to find a way (aka a hack) to be up to code while still having the microwave's fan button turn on a fan on the building's roof. 4. I think it should be as rigorous as possible, but as another user mentioned, it's not realistic to own the environment in which your code runs. I would love to have a small set of environments/browsers/screen sizes to develop for, but that's not an option in 2019 at scale. 5. Software Engineer 6. Definitely tech lead 7. Senior software engineer 8. I can definitely suggest them, and everyone is open to ideas and discussion. Design and software is a team effort. 9. I write a lot of documentation. This includes writing/updating comments, writing design documents for new FE features, updating wikis etc.

otras 8y ago

I'm a software engineer working mostly on the front end at a large tech company. For context, we have a separate UX team that works on design. Happy to give these my best. 1. Tests are organized around their component. This includes unit tests for any logic (though often we prefer to keep as much logic out of FE as possible) and screenshot tests for components. We also have larger-scale integration tests. 2. You mean like MVC (model-view-controller)? That's a pretty common one. 3. I'm not sure artistic is the antonym of rigorous. For example, math proofs are often both. I think it's better to characterize it as a craft. It's like being an electrician; sometimes your wires line up nicely, but sometimes you have to find a way (aka a hack) to be up to code while still having the microwave's fan button turn on a fan on the building's roof. 4. I think it should be as rigorous as possible, but as another user mentioned, it's not realistic to own the environment in which your code runs. I would love to have a small set of environments/browsers/screen sizes to develop for, but that's not an option in 2019 at scale. 5. Software Engineer 6. Definitely tech lead 7. Senior software engineer 8. I can definitely suggest them, and everyone is open to ideas and discussion. Design and software is a team effort. 9. I write a lot of documentation. This includes writing/updating comments, writing design documents for new FE features, updating wikis etc.