Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Relative units are fine till they are not. If you want something to display at 40px size, the client device will scale this depending on it's own ppi even setting the measurements in pixels and most of the time using relative units will enforce you to add extra media queries that wouldn't be needed if using pixels instead. It just depends on the place and the expected behavior you want to achieve so please, don't use the fallacy "use relative units" for all. As I need to remember most of the time in this platform, there are nice tech out there, but none of them are meant to rule them all.
Is the default behavior of any text element, nothing to do here. For the layout it will be weird at the point of having more than a single block element, you can simply use flexbox to state something like flex-basis: 50%, max-width: 50%. The browser interpreter will do the rest.
and 5. are for designers, not developers, while 6 is mixed. I've enough things to do as senior dev and tech lead, don't really want to get involved in a totally different job (in which you need to learn many things such color theory, form and composition, design meaningfulness and a big bunch of other things).
By the way, the design life-cycle, along with UX is:
UX: do low quality wireframes, test them, update them while ensuring the expected functionalities are covered,
Design: apply design to this wireframes according to the product.
UX + Design: test the whole and start again if needed.
This is done for EACH view or component in the application.
needs analysis to really know if this is needed. Chrome console/dev tools is great for testing responsiveness as well without the need of a third party and also includes lighthouse.
That's my quick insight on this, hope it helps adding some criticism on what is told since 10 years ago like a mantra.
Relative units are fine till they are not. If you want something to display at 40px size, the client device will scale this depending on it's own ppi even setting the measurements in pixels and most of the time using relative units will enforce you to add extra media queries that wouldn't be needed if using pixels instead. It just depends on the place and the expected behavior you want to achieve so please, don't use the fallacy "use relative units" for all. As I need to remember most of the time in this platform, there are nice tech out there, but none of them are meant to rule them all.
Is the default behavior of any text element, nothing to do here. For the layout it will be weird at the point of having more than a single block element, you can simply use flexbox to state something like flex-basis: 50%, max-width: 50%. The browser interpreter will do the rest.
and 5. are for designers, not developers, while 6 is mixed. I've enough things to do as senior dev and tech lead, don't really want to get involved in a totally different job (in which you need to learn many things such color theory, form and composition, design meaningfulness and a big bunch of other things).
By the way, the design life-cycle, along with UX is:
UX: do low quality wireframes, test them, update them while ensuring the expected functionalities are covered,
Design: apply design to this wireframes according to the product.
UX + Design: test the whole and start again if needed.
This is done for EACH view or component in the application.
That's my quick insight on this, hope it helps adding some criticism on what is told since 10 years ago like a mantra.
Always good to have constructive criticism and multiple views. Thanks for sharing these!