home.social

Search

74 results for “jyasskin”

  1. @lauren @dangoodin #AWU has won NLRB elections for some bargaining units, but we still have a long way to go to cover all ~200k employees and TVCs. We even got Google recognized as a joint employer for a couple of the units, although Google's likely to drag that through as many courts as they can: theverge.com/2024/1/4/24026025

  2. @lauren @dangoodin has won NLRB elections for some bargaining units, but we still have a long way to go to cover all ~200k employees and TVCs. We even got Google recognized as a joint employer for a couple of the units, although Google's likely to drag that through as many courts as they can: theverge.com/2024/1/4/24026025

  3. @lauren @dangoodin #AWU has won NLRB elections for some bargaining units, but we still have a long way to go to cover all ~200k employees and TVCs. We even got Google recognized as a joint employer for a couple of the units, although Google's likely to drag that through as many courts as they can: theverge.com/2024/1/4/24026025

  4. @lauren @dangoodin #AWU has won NLRB elections for some bargaining units, but we still have a long way to go to cover all ~200k employees and TVCs. We even got Google recognized as a joint employer for a couple of the units, although Google's likely to drag that through as many courts as they can: theverge.com/2024/1/4/24026025

  5. I've been thinking of #RACI as the framework for being clear about who's a reviewer vs who's an approver ... but actually the "A" is "Accountable", not "approver".

    en.wikipedia.org/wiki/Responsi does list "approver" as another possible expansion, but I think the "PACSI" acronym fits better. The Accountable person is often a common management root, and for web platform changes they've delegated Control to people like the #BlinkApiOwners, a security review team, etc.

  6. I've been thinking of #RACI as the framework for being clear about who's a reviewer vs who's an approver ... but actually the "A" is "Accountable", not "approver".

    en.wikipedia.org/wiki/Responsi does list "approver" as another possible expansion, but I think the "PACSI" acronym fits better. The Accountable person is often a common management root, and for web platform changes they've delegated Control to people like the #BlinkApiOwners, a security review team, etc.

  7. I've been thinking of as the framework for being clear about who's a reviewer vs who's an approver ... but actually the "A" is "Accountable", not "approver".

    en.wikipedia.org/wiki/Responsi does list "approver" as another possible expansion, but I think the "PACSI" acronym fits better. The Accountable person is often a common management root, and for web platform changes they've delegated Control to people like the , a security review team, etc.

  8. I've been thinking of #RACI as the framework for being clear about who's a reviewer vs who's an approver ... but actually the "A" is "Accountable", not "approver".

    en.wikipedia.org/wiki/Responsi does list "approver" as another possible expansion, but I think the "PACSI" acronym fits better. The Accountable person is often a common management root, and for web platform changes they've delegated Control to people like the #BlinkApiOwners, a security review team, etc.

  9. I have an 8yo #BlackAndDecker drill whose battery just died. I don't use it super heavily, and it's only a so-so drill, so I was thinking about just getting a different drill instead of replacing the battery. This was compounded by the fact that B&D charges $50 for both the whole drill, and for a replacement battery!

    But I tried complaining to their support website, and they gave me the "one-time courtesy" of sending a replacement battery for free.

  10. Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

    @slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

  11. Has anyone gotten and to play nicely together? does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the it's contained in, which defeats the purpose of framework-independent components.

    @slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

  12. Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

    @slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.

  13. Has anyone gotten #WebComponents and #ServerSideRendering to play nicely together? #Astro does a good job of rendering on the server, but it can only do that for a web component if the component's written in the same framework as the #AstroIsland it's contained in, which defeats the purpose of framework-independent components.

    @slightlyoff, this seems like something you'd have an answer for, since you've championed both parts.