4 ms·

That seems like a huge waste of time to have designers do all that work. There should be a component library and a design language established in the company th

by notus 8y ago

That seems like a huge waste of time to have designers do all that work. There should be a component library and a design language established in the company that the designers use to derive new applications. With how things are coupled in modern javascript frameworks I think you would get minimal re-use out of html and css that a designer made.

pixelbath 8y ago
This is exactly what Bootstrap does and why most Bootstrap-built sites end up looking very similar. If all you're after is functionality, that's easy enough to achieve, but you're going to need designers at some point if you want to differentiate yourself visually.
- notus 8y ago
  I didn't say you don't need designers. The designers need to create the design language and help with the component library. It should be unique to your company, but once it is done once there is no reason to do it again unless you want to change branding or update the design for all your companies applications. However, having the designers code out prototypes is a waste of time IMO. They are not likely going to be proficient enough in a modern framework to ship the prototype like the author was saying they do. Design is a full time job and so is front end and at least at the companies I've worked at designing requires full attention of the designers and FE requires full attention of the FE developers.
naniwaduni 8y ago
It's not clear to me whether the costs of lower specialization from having designers do a larger chunk of the work are necessarily worse than communication overhead. Having a component library is great when it'll already do everything you need it to (e.g. because in the course of your organizational history you've gone through a lot of designers and a lot of designs), but the failure mode can be a huge drain.

4 ms·

That seems like a huge waste of time to have designers do all that work. There should be a component library and a design language established in the company th

by notus 8y ago

pixelbath 8y ago
This is exactly what Bootstrap does and why most Bootstrap-built sites end up looking very similar. If all you're after is functionality, that's easy enough to achieve, but you're going to need designers at some point if you want to differentiate yourself visually.
- notus 8y ago
  I didn't say you don't need designers. The designers need to create the design language and help with the component library. It should be unique to your company, but once it is done once there is no reason to do it again unless you want to change branding or update the design for all your companies applications. However, having the designers code out prototypes is a waste of time IMO. They are not likely going to be proficient enough in a modern framework to ship the prototype like the author was saying they do. Design is a full time job and so is front end and at least at the companies I've worked at designing requires full attention of the designers and FE requires full attention of the FE developers.
naniwaduni 8y ago
It's not clear to me whether the costs of lower specialization from having designers do a larger chunk of the work are necessarily worse than communication overhead. Having a component library is great when it'll already do everything you need it to (e.g. because in the course of your organizational history you've gone through a lot of designers and a lot of designs), but the failure mode can be a huge drain.