home.social

#specificity — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #specificity, aggregated by home.social.

  1. Got to hear #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beat vague generality. #ActingCoach #ActingCoaching #actors #voice #specificity

  2. Got to hear #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beat vague generality. #ActingCoach #ActingCoaching #actors #voice #specificity

  3. Got to hear #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beat vague generality. #ActingCoach #ActingCoaching #actors #voice #specificity

  4. Got to hear #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beat vague generality. #ActingCoach #ActingCoaching #actors #voice #specificity

  5. Got to hear #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beat vague generality. #ActingCoach #ActingCoaching #actors #voice #specificity

  6. Got to hear an #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beats vague generality.

    #ActingCoach #ActingCoaching #actors #voice #specificity

  7. Got to hear an #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beats vague generality.

    #ActingCoach #ActingCoaching #actors #voice #specificity

  8. Got to hear an #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beats vague generality.

    #ActingCoach #ActingCoaching #actors #voice #specificity

  9. Got to hear an #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beats vague generality.

    #ActingCoach #ActingCoaching #actors #voice #specificity

  10. Got to hear an #acting #coaching client's voice almost quaver just as they hit a key piece in the material because they got more specific with it, and the depth there was beautiful to encounter. Specificity almost always beats vague generality.

    #ActingCoach #ActingCoaching #actors #voice #specificity

  11. Re: Affordances and Lean CSS

    Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]

    kerrick.blog/posts/2025/re-aff

  12. Re: Affordances and Lean CSS

    Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]

    kerrick.blog/posts/2025/re-aff

  13. Re: Affordances and Lean CSS

    Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]

    kerrick.blog/posts/2025/re-aff

  14. Re: Affordances and Lean CSS

    Stephen Margheim (fractaledmind) wrote Affordances: The Missing Layer in Frontend Architecture this month. This quick post is my reply to his great article. I hear the objection already: “Isn’t this just… semantic CSS classes? We tried that.” You’re right that we tried it. But “it didn’t work” deserves unpacking. I was indeed objecting that in my mind. But I was not thinking, "it didn't work." I was thinking, "and it has kept working for decades. Obviously the utility-only workflow described is terrible; it's why I refuse to choose Tailwind. How are affordances better than what's worked for a decade?" […]

    kerrick.blog/posts/2025/re-aff

  15. I'm of the opinion that the #cascade was a mistake, for the same reason that #OOP was a mistake; #inheritance is too implicit. How much time have we wasted with things like #CSS resets, !important, #BEM, etc just faffing about with #specificity trying to make styles apply? For what? A few bytes of duplication?

    #webdev #styling #shadowDom

  16. I'm of the opinion that the #cascade was a mistake, for the same reason that #OOP was a mistake; #inheritance is too implicit. How much time have we wasted with things like #CSS resets, !important, #BEM, etc just faffing about with #specificity trying to make styles apply? For what? A few bytes of duplication?

    #webdev #styling #shadowDom

  17. I'm of the opinion that the #cascade was a mistake, for the same reason that #OOP was a mistake; #inheritance is too implicit. How much time have we wasted with things like #CSS resets, !important, #BEM, etc just faffing about with #specificity trying to make styles apply? For what? A few bytes of duplication?

    #webdev #styling #shadowDom

  18. I'm of the opinion that the #cascade was a mistake, for the same reason that #OOP was a mistake; #inheritance is too implicit. How much time have we wasted with things like #CSS resets, !important, #BEM, etc just faffing about with #specificity trying to make styles apply? For what? A few bytes of duplication?

    #webdev #styling #shadowDom

  19. I'm of the opinion that the #cascade was a mistake, for the same reason that #OOP was a mistake; #inheritance is too implicit. How much time have we wasted with things like #CSS resets, !important, #BEM, etc just faffing about with #specificity trying to make styles apply? For what? A few bytes of duplication?

    #webdev #styling #shadowDom