3 ms·

The UI/UX team that works on this likely aren't backend coders. They can either fire the team or put them to use, but reassigning them random C++/Rust tasks pro

by hajile 5y ago

The UI/UX team that works on this likely aren't backend coders. They can either fire the team or put them to use, but reassigning them random C++/Rust tasks probably isn't possible.

kevincox 5y ago
To be perfectly blunt it doesn't matter what a team is doing. They paid $X million to "design resources" and directed those resources at the redesign featured in this release. Instead they could have paid that to backend, other UX initiatives, the extension team, the privacy team... I understand that you can't swing resources around freely in the short term but you don't have a bunch of designers sitting around by accident. Someone decided that they should hire them.
- pseudalopex 5y ago
  You're right the money could be spent elsewhere. But calling people resources is rude to put it mildly.
  - kevincox 5y ago
    I said I was being blunt in the prefix. I definitely agree that we need to think about people, that was a large component of "you can't swing resources around freely". Firing people is not something that I would like to see. The point I was trying to emphasize is that it isn't as if Mozilla just happened to have X people with design skills and Y people with whatever other skills. There was planning to build the teams and planning to pick the projects. So while I agree that you can't just put people on random projects I wanted to point out that Mozilla had a lot of agency in the decisions that lead up to a team working on the redesign, it didn't happen just because they happened to have a bunch of designers available.
  - Zababa 5y ago
    > But calling people resources is rude to put it mildly. I don't think it's considered rude, since "Human Resources" is a widely accepted term.
    - pseudalopex 5y ago
      Human resources is just a depersonalizing term for personnel. Design resources is just a depersonalizing term for designers. Human resources is less bad because it doesn't refer to specific people. And most people can't choose what the department is called. But they can choose what they call other people.
- hajile 5y ago
  Good UI developers are incredibly hard to find. If they let them go, it will take a couple years to get a new team assembled and integrated into Mozilla. I agree with the idea of other UX initiatives though. They could definitely have the team work on other parts of Firefox even though that isn't as immediately visible to all users.
  - brotherofsteel 5y ago
    >Good UI developers are incredibly hard to find. Is that why the ones they do have keep messing up the UI?
- LargoLasskhyfv 5y ago
  Let them clean the restrooms.

by hajile 5y ago

The UI/UX team that works on this likely aren't backend coders. They can either fire the team or put them to use, but reassigning them random C++/Rust tasks probably isn't possible.

kevincox 5y ago

To be perfectly blunt it doesn't matter what a team is doing. They paid $X million to "design resources" and directed those resources at the redesign featured in this release. Instead they could have paid that to backend, other UX initiatives, the extension team, the privacy team... I understand that you can't swing resources around freely in the short term but you don't have a bunch of designers sitting around by accident. Someone decided that they should hire them.

pseudalopex 5y ago
You're right the money could be spent elsewhere. But calling people resources is rude to put it mildly.
- kevincox 5y ago
  I said I was being blunt in the prefix. I definitely agree that we need to think about people, that was a large component of "you can't swing resources around freely". Firing people is not something that I would like to see. The point I was trying to emphasize is that it isn't as if Mozilla just happened to have X people with design skills and Y people with whatever other skills. There was planning to build the teams and planning to pick the projects. So while I agree that you can't just put people on random projects I wanted to point out that Mozilla had a lot of agency in the decisions that lead up to a team working on the redesign, it didn't happen just because they happened to have a bunch of designers available.
- Zababa 5y ago
  > But calling people resources is rude to put it mildly. I don't think it's considered rude, since "Human Resources" is a widely accepted term.
  - pseudalopex 5y ago
    Human resources is just a depersonalizing term for personnel. Design resources is just a depersonalizing term for designers. Human resources is less bad because it doesn't refer to specific people. And most people can't choose what the department is called. But they can choose what they call other people.
hajile 5y ago
Good UI developers are incredibly hard to find. If they let them go, it will take a couple years to get a new team assembled and integrated into Mozilla. I agree with the idea of other UX initiatives though. They could definitely have the team work on other parts of Firefox even though that isn't as immediately visible to all users.
- brotherofsteel 5y ago
  >Good UI developers are incredibly hard to find. Is that why the ones they do have keep messing up the UI?
LargoLasskhyfv 5y ago
Let them clean the restrooms.