Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
wycats's profile
Yehuda Katz 🥨
Yehuda Katz 🥨
Yehuda Katz  🥨
Verified account
@wycats

Tweets

Yehuda Katz  🥨Verified account

@wycats

Tilde Co-Founder, OSS enthusiast and world traveler.

Portland, OR
yehudakatz.com
Joined August 2007

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Daniel Ehrenberg‏ @littledan Mar 3

      I'm trying to model my participation in TC39 based on what I've been reading about maintainers of open-source projects, but having a hard time. When people file a bug, asking the reporter to make a PR can be sort of painful! But I am really happy with many recent contributions.

      2 replies 0 retweets 6 likes
    2. Allen Wirfs-Brock‏ @awbjs Mar 3
      Replying to @littledan

      It’s the wrong model. It’s the responsibility of a standards committee to fix identified issues, not to dump it back on users of the standard to propose a fix. It's fine to ask if a reporter wants to become more involved by submitting a PR. But it shouldn't be expected.

      2 replies 0 retweets 0 likes
    3. Yehuda Katz  🥨‏Verified account @wycats Mar 3
      Replying to @awbjs @littledan

      In all OSS projects, people should be able to file bugs without having to write the fix themselves. On the other hand, there are many, many people out there hungering to help. Unexpectedly, the most "boring" areas are the ones that are the most tractable for new contributors.

      1 reply 5 retweets 7 likes
    4. Yehuda Katz  🥨‏Verified account @wycats Mar 3
      Replying to @wycats @awbjs @littledan

      Believe it or not, grunt work like "update the spec to use ? instead of ReturnIfAbrupt" is the kind of work that is highly interesting to new contributors:

      1 reply 0 retweets 3 likes
    5. Yehuda Katz  🥨‏Verified account @wycats Mar 3
      Replying to @wycats @awbjs @littledan

      1. The new contributor gets satisfaction from adding value to the project, which they measure by how much the maintainers seem enthusiastic about getting the work done.

      1 reply 0 retweets 2 likes
    6. Yehuda Katz  🥨‏Verified account @wycats Mar 3
      Replying to @wycats @awbjs @littledan

      2. This kind of work is a good fit for detailed but rote instructions. The group of people working on it can help each other to get it right, and even improve the detailed instructions.

      1 reply 0 retweets 1 like
      Yehuda Katz  🥨‏Verified account @wycats Mar 3
      Replying to @wycats @awbjs @littledan

      Counterintuitively, they are more likely to get it right given good instructions than one or two overloaded maintainers trying to burn through a huge slog like this, and they ask good questions when the instructions aren't detailed enough.

      11:23 AM - 3 Mar 2018
      • 2 Likes
      • Daniel Ehrenberg Per Lundberg ن
      1 reply 0 retweets 2 likes
        1. New conversation
        2. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          3. Maintainers underestimate the work of just getting the "contributing environment" set up: tooling, GitHub workflow, CI, learning syntactic conventions, etc "Trivial" tasks still have all of those requirements, but have a quicker payoff to get something accepted.

          2 replies 0 retweets 3 likes
        3. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          For a new contributor, getting *anything* accepted is the best feeling in the world, and increasing the rate of success to "first accepted patch" is a huge input into the longer pipeline of more thorny contributions.

          1 reply 10 retweets 31 likes
        4. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          4. New contributors notice problems in tooling that people were "getting by" with, and want to fix them. Often, external contributors are in a better position to fix tooling or workflow issues than the maintainers, because of knowledge that comes from their coding experience.

          1 reply 0 retweets 1 like
        5. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          5. There is often more work needed on "un-specialized" aspects of a project than the time needed for the specialized part. Even in a spec, GitHub workflow, maintaining tooling, ops (hosting the latest version of the spec), etc take a lot of time.

          1 reply 0 retweets 1 like
        6. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          Increasing the pool of contributors who have skills and time to work on that kind of stuff unburdens the existing maintainers.

          1 reply 0 retweets 2 likes
        7. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          And people love roles like "keeping the spec up and up to date". They feel like they're contributing to something important, even though they aren't (yet) equipped to write spec text.

          1 reply 0 retweets 2 likes
        8. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          The same holds true with things like helping with explainers, writing Babel plugins, writing spec tests, etc. These are all things that a much wider group of people can do, and things that people are enthusiastic about doing.

          1 reply 0 retweets 1 like
        9. Yehuda Katz  🥨‏Verified account @wycats Mar 3
          Replying to @wycats @awbjs @littledan

          Done for now 😀

          1 reply 0 retweets 2 likes
        10. 1 more reply

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info