Noel Rappin

@noelrap

Noel Rappin is a Staff Engineer at Chime, and the author of Modern Front End Development for Rails and Rails 5 Test Prescriptions. . (He/Him)

Chicago IL
noelrappin.com
Liittynyt maaliskuu 2007
306 kuvaa tai videota Kuvat ja videot

Twiitit

Olet estänyt käyttäjän @noelrap

Haluatko varmasti nähdä nämä twiitit? Twiittien näyttäminen ei poista käyttäjän @noelrap estoa.

  1. Kiinnitetty twiitti
    3. heinäk.

    And finally, the full 2021 book club. Tailwind book available at and Modern Front-End available at at or . Thanks!

    A plush Lego Batman appears to read Modern Front-End Development for Rails accompanied by a plush monkey reading Modern CSS with Tailwind
    3 vastausta 3 uudelleentwiittausta 21 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa
  2. 8 tuntia sitten

    Is it coincidence or not that somebody just unsubscribed from my newsletter?

    Kumoa
  3. 8 tuntia sitten

    To be clear, I completely understand wanting to set the expectation that if you use this method, you are exposing yourself to something that might change. I just think that actually preventing people from using that method is a bigger step and one to take more rarely.

    Vastauksena käyttäjälle @noelrap
    "Enforcement" is a strong word for `private` in Ruby. 😄 There's a lot of `send` usage to bypass it in the wild. To me, it's more about managing expectations. If something is private, you use it at your own risk. If it's useful, definitely, give it a public interface.
    1 vastaus 1 tykkäys
    Kumoa
  4. 8 tuntia sitten

    I should say, I’m not a monster here, when I’m on teams that have established conventions of using private methods, I defer.

    1 tykkäys
    Kumoa
  5. 8 tuntia sitten

    But definitely part of my reluctance to make methods private has to do with testing.

    3 vastausta 2 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa
  6. 8 tuntia sitten

    This is a long standing testing debate. On one side the argument is that private methods are internal details and you test the public API On the other, the argument that private methods contain logic and should be tested. I feel like whatever makes you more confident is fine.

    Vastauksena käyttäjälle @noelrap
    From a unit testing perspective - how do you ensure coverage on private methods? Testing a private method by testing the public methods using it feels wrong.
    2 vastausta 1 uudelleentwiittaus 3 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa
  7. 8 tuntia sitten

    I think another way I’d phrase this is that we overrate the cost of not being able to refactor or change a public method and underrate the cost of not making a potentially useful concept available.

    Vastauksena käyttäjälle @noelrap
    A lot of my experience with private methods is that they are extractions/encapsulations for the sake of extraction, rather than to serve some other purpose (e.g. readability, safety, reusability). "This method is too long - I better pull some implementation details out"
    2 vastausta 1 tykkäys
    Kumoa
  8. 8 tuntia sitten

    This is why when I make this argument, I usually preface it by saying that lots of people smarter than me disagree.

    Vastauksena käyttäjälle @noelrap
    Having worked in a codebase where a big chunk had no private methods for the reasons you state…it was a nightmare. You could not effectively refactor anything because you'd have a ton of methods that may or may not be meaningful. So it just rotted.
    1 tykkäys
    Kumoa
  9. 9 tuntia sitten

    I understand why people say that private methods are good, I just don’t generally agree. In this analogy, where I’m the chef, I don’t think I always know enough to be able to tell in advance what the customers are going to want — so I don’t want to limit the menu.

    Vastauksena käyttäjälle @noelrap
    Private methods are tools in the kitchen. Public methods are what's on the menu.
    2 vastausta 7 tykkäystä
    Kumoa
  10. 18 tuntia sitten

    Let me start from this direction: if private methods didn't exist in Ruby (as they don't exist in, say, Smalltalk), what you you say would be the argument for adding them?

    Vastauksena käyttäjälle @noelrap
    why?
    2 vastausta 1 tykkäys
    Kumoa
  11. 18 tuntia sitten

    Actually, the thing about Ruby that I say most often and gets me weird looks is that you shouldn't have private methods unless it's actually dangerous for the method to be called externally.

    3 vastausta 3 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa
  12. 19 tuntia sitten

    I wanted to write a joke about how I thought the next tweet would be “and 10 years is enough, we’re shutting it down”, but I can’t make the tone work unless I screamingly call attention to “I’m just making a joke here”…

    Since 2011, we've said that we wanted to be a framework for 10 years. We did it! I love you Embereños 🥰🥰🥰
    Näytä tämä ketju
    Kumoa
  13. 19 tuntia sitten

    I wrote this about TDD advocacy today, and I like it enough to share:

    Quote: “To be fair, I think in general it's way, way better than things were when I first started advocating for TDD in organizations, which was in like 2003. People would look at me like I grew a second head then. Now they only look at me like I've grown a third eye. Progress!”
    1 vastaus 9 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa
  14. 7. jouluk.

    FWIW, there will be an official something updating Modern Front-End for Rails 7, but exactly what form it will take is not determined yet (might be a Medium article, might be a new appendix, might be a new book version).

    I just released Rails 7.0.0.rc1. The plan is to have the final version before Christmas. Please give it a try and report any issues you find so we can have a smooth final release
    6 tykkäystä
    Kumoa
  15. 7. jouluk.

    So they went from alpha 2 to rc1, or did I miss something?

    I just released Rails 7.0.0.rc1. The plan is to have the final version before Christmas. Please give it a try and report any issues you find so we can have a smooth final release
    1 vastaus
    Kumoa
  16. uudelleentwiittasi
    28. marrask.

    Here's a silly attempt at a plot synopsis for _Rogers: The Musical_. Nobody was clamoring for this. I just wanted to see if I could get something that hit the plot beats, and fit in songs that were as wonderfully cheesy as the one song we got /1

    2 vastausta 3 uudelleentwiittausta 6 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa
  17. 30. marrask.

    🕯🕯

    4 tykkäystä
    Kumoa
  18. 29. marrask.

    This sale ends tomorrow, lots of great books available.

    is ticking down! Use code turkeysale2021 at checkout to save 40% at
    1 tykkäys
    Kumoa
  19. uudelleentwiittasi
    29. marrask.

    is ticking down! Use code turkeysale2021 at checkout to save 40% at

    5 uudelleentwiittausta 3 tykkäystä
    Kumoa
  20. 29. marrask.

    🕯

    5 tykkäystä
    Kumoa
  21. 28. marrask.

    The battle is joined and the Avengers win (“Save The City (reprise)”), and Steve basks in the glow (“Star-Spangled Man 2012”). Curtain Call. /15

    4 tykkäystä
    Näytä tämä ketju
    Näytä tämä ketju
    Kumoa

@noelrap ei ole vielä twiitannut.

Lataaminen näyttää kestävän hetken.

Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.

    Saatat pitää myös

    ·