DHH now being a full-blown Linux nerd, I expect the hair to become a ponytail (and the 37signals T-shirt to acquire some stains) by the next #RailsWorld
I recently built a `cmd+k` search modal (like the ones you can see on the Bootstrap or Tailwind CSS websites) and it was really easy to do thanks to Hotwire!
I wrote an article about it if you want to have a look:
https://t.co/YW6EKPJakq
One of my top 3 hosts of the @SlateGabfest, @jdickerson, has a new podcast, which is basically essays read aloud, and his writing is brilliant. Deep, articulated, elegant, but also funny, and a bit nerdy. Highly recommended: https://t.co/paLPUvJRH7
A new version of @GitUpApp dropped! This is one of my most-used apps, so an update feels like a surprise present. Bonus: the new icon is great. (To be fair, the old one always felt like a bad placeholder.)
Everybody is amazed to see that Ripper Owen’s voice is still as mind blowing as it was 25 years ago, but nobody mentions the fact that time seems to actually flow backwards for him: he’s losing weight and growing his hairline.
I learned something about object-oriented programming vs functional programming when I briefly taught at a bootcamp:
When someone's first programming language is object-oriented, in the beginning you really have to push them to create objects, store instance data in them, and operate on that data with local methods.
They do not want to do this.
Instead, what they naturally tend to do instead is pass data between class methods. No objects. No instance data. Just functions.
And honestly, I can't blame them. I felt kinda guilty making them write OO properly.
Having been a young and inexperienced manager, in my long dark past, who perpetrated the first two of that triplet, I can attest that I did not know at the time, and did later experience, the dire consequences of my actions.
Having said that, I can also attest to the fact that adding manpower _early enough_, and requesting moderate short term overtime to achieve a nearby, realistic, and imperative goal, are sometimes the right things to do.
Testing is an essential part of delivering. Shirking it is suicide. Delivering an inadequately tested product is irresponsible and incompetent.
However, testing cannot be an open ended process. It must have an endpoint defined by concrete criteria — not a date. Open-ended or date driven “stability testing” is just as irresponsible and incompetent as insufficient testing.
As tech coaches, we have to remind participants to stick to baby steps. Yet, 1) It's exhausting to be the killjoy all the time; 2) We cannot keep an eye on everyone at the same time. #tcr#technical#agileCoaching#evolutionaryDesign#codingDojo https://t.co/yIvFmeeCHL
I think mocks are a powerful tool when you want to test implementation as opposed to results. Of course testing implementation is a form of coupling that comes with costs. Those tests break when implementations change for the better. So mocks should be used with discretion and wisdom. But they should not be entirely abandoned.
@gregnavis Did it a lot. Loved it, but like all methods, it's easier than you think to misuse it and then get frustrated. I advise to focus on the core principles (fixed time investment, ownership and communication) and refrain from customizing until you've practiced a lot.
At #HelveticRuby a couple a weeks ago, I found myself disagreeing with parts of a talk, as good as it was. It's about onboarding junior developers. So I wrote my own addendum to it: https://t.co/SRnwFAFszr
Loving #HelveticRuby. The 2 talks we’ve had so far were so good that I couldn’t take 30 seconds to live-toot them. And @AbiodunAjibade3’s deserves a special mention or two for being extra educational on a complex and unfairly neglected topic, Ractors.
Awesome first evening at #HelveticRuby, but I had to leave when @nicoerlichman started talking about Rails + Next over GraphQL. There are some things too profane even for me.