Related Posts
I'll be joining tw as UI Lead, soon.
I'm a javascript/react developer since inception of my career & haven't worked much on CICD/JENKINS and similar technology.
Should I be worried that as a lead I don't know these and will it affect by job security?
Ps- I'm good at UI,js, react etc.
Thoughtworks
Experts please help.
Best (non-agency) company to work at in Boston??
Additional Posts in UX and UI designers 🚀
Did you know that Harvard has free Resume, CV and Cover Letter resources - including action verbs, templates and samples?
I've compiled a list of them
1. This document contains:
- Tips
- Resume Samples
- Resume Template
- Action Verbs
- Cover Letter Tips
https://hwpi.harvard.edu/files/ocs/files/undergrad_resumes_and_cover_letters.pdf
2. Document on CVs and Cover Letters
https://hwpi.harvard.edu/files/ocs/files/gsas-cvs-and-cover-letters.pdf
3. Youtube Video on "How to write a Resume" by Harvard University
https://www.youtube.com/watch?v=lcgS0kaIgng&t=1s
New to Fishbowl?
unlock all discussions on Fishbowl.





Since you have devs focusing on different platforms, I think the way you're doing it now should work fine. But I wouldn't bother making separate pages for different parts of the app. Make an assets page separate from everything else where you can put global components to reference elsewhere, and make a separate page for each platform (desktop, phone, tablet, etc). Then keep all of the screens in their respective page, making sure that you group them in sections based on each user flow. Not only is this better for doing prototypes but it also makes the pages less cluttered and easier to digest when the developers come in and do their thing.