Weekly bookmarks - Issue #19
"Wait, you all don't use user stories?"
"No. What for?"
"To have stories. How do you break stuff down?"
"The team meets, talks about it, maybe sketches, and then we build it"
"Without stories?"
"We might take notes. Or diagrams"
"And make them stories?"
"No. No stories"
Really digging this pattern for organizing different 'features' of a model.
Keeps related methods together and makes it easier to find relevant code as the codebase grows. Plus I can separate out test files by feature. https://t.co/qasbU3FMUv
Did you know pattern matching in Ruby could help you to enforce types on any Ruby data structure? 😲
This is what we'll learn Today on our Pattern matching in Ruby adventure 💎⛏
👇 Check it out (or as a gist: https://t.co/qMOmZpTtKC ) https://t.co/3p22tmPffa
Demystify the complexity of the Rails 7 asset pipeline and navigate its wide menu of options.
🚨 Some news 🚨
Earlier this year I published a book on Ruby on Rails.
Today, I'm making that book free for everyone:
https://t.co/hRrFVxZcSA
One possible way of rendering a simple calendar control
a dead simple way to add some motion to your apps. apply this stimulus controller to a <ul>, for example.
https://t.co/O68q7dFzJc
How using this popular RSpec technique can sometimes do more harm than good.
After using AWS for ~14 years, I've internalised a handful of design patterns that I try to apply to my own software. I'm keen to know if it's the same for other folks.
Roughly: tags, IDs (thrice), limits, pagination.
(I'm not going to use the thread emoji)
Want to become an outstanding engineering leader? Keep a daily journal.
Design System Checklist, a @trello board to track design system elements by @RahulJero: https://t.co/AxHpxq1A8E (via @smashingmag)
Working in small chunks is one of the most impactful things we can do as developers.