@Michael_Cherry2 I had to go back and look at the archives because I didn’t believe you. You’re the only one wearing a beanie and sunglasses in your picture. How did you get on that list?
@Jarsen@atomkirk The contrast is startling to me. We went from Web3 evangelists talking about how it was going to change the world. I’d look for one use case and would find some incomprehensible word salad.
Every day I see a concrete example of AI doing something and think “holy shit.”
@GeePawHill Discovering and following you on here was perhaps the single greatest value I got from this app. You won’t lose my readership if you decide to move.
@Jarsen Even if the object you are naming is an instance of Class, there’s likely some more specific role it’s playing and you can name it after that.
If the role of “Class” really is as specific as you can get, yes, rethink your choices
@davetron5000 @jgarber Doesn’t help with RSpec but I discovered https://t.co/iDQR1kkZZC this weekend. An example of what’s possible. It’d be nice to see a similar tool in Ruby.
@JasonSwett Less indirection can make the test more readable. The most obvious example to me is string literals. I find it more readable to repeat a string literal in a test over extracting it to a variable. This would be pretty smelly in non-test code.
@JasonSwett Or two tests that are testing the same duplicated behavior that’s implemented in two places. Extract that behavior to one place and then maybe a test can go away.
@modernserf Especially interesting that functional front end frameworks at one point claimed the MVC pattern was fine for web servers but didn’t work for UIs, when in fact MVC arose out of Smalltalk GUIs
Something I didn’t appreciate enough about pair programming: it’s an instant trip to Flow Zone. I didn’t realize how distracting the modern (virtual) workplace had become when I had a pair keeping me focused.
@atomkirk Everything going through React really hurts testability and reusability.
I think hooks allow this to appear less painful on the surface without actually addressing the tight coupling between the view layer and the rest of the code.
@atomkirk My view (hope?) is that state in components (either via hooks or otherwise) will be seen, if not as an anti pattern, at least with a little more nuance than the current approach of putting all state in React.
@Jarsen Yeah it’s probably usually like that. There’s something about just getting the clay into your hands so-to-speak. “I want to collapse this inheritance hierarchy but I don’t know where to start, maybe I’ll just extract these three lines into a method…”