_swanson Profile Banner
matt swanson 😈 Profile
matt swanson 😈

@_swanson

Followers
13K
Following
4K
Media
1K
Statuses
15K

🎯 Building https://t.co/3G3n0iVnIn πŸ”₯ Ruby on Rails tips πŸ“» https://t.co/MMIvlQpzwD ✌️ All killer, no filler 🍊 Karl Pilkington is my spirit animal

Indianapolis, IN
Joined February 2010
Don't wanna be here? Send us removal request.
@_swanson
matt swanson 😈
3 years
I strongly identify as a Product Engineer. Not as: - Developer (I only like building user-facing things) - Full stack (I want to help with shaping, roll-out, strategy) - Entrepreneur (not interested in company building) - Indie hacker (like working with team, not into quick and
90
81
1K
@_swanson
matt swanson 😈
1 day
We do 6 week product cycles (5 build+1 cooldown) but twice a year we do a "double cooldown", including pretty much all of December So far we are on to track to do: - Major DB upgrade, vacuum, index cleanup during scheduled downtime - Move all background jobs to SLA queues w/
5
3
105
@_swanson
matt swanson 😈
3 days
Last week on the TL, I saw: - PR in Fizzy to upgrade the `data-turbo-confirm` dialog - Browser native dialog opening, light-dismiss, and animations So @fractaledmind and I mashed them to show the best way to build a beautiful Rails confirmation dialog https://t.co/xf6NJtMfC4
Tweet card summary image
boringrails.com
Upgrading the default data-turbo-confirm with a beautiful, native HTML dialog with animations
5
7
100
@_swanson
matt swanson 😈
8 days
@Judoscale The taste and specialized knowledge that a human provides is: - Knowing that we want to do this kind of infra change - Knowing what the best resources to share with the LLM are (instead of chatting for an hour trying to explain what I want) - Reviewing the plan to gut check
1
0
1
@NextDecadeLNG
NextDecade
16 days
Did you know? Rio Grande LNG has made ~$950,000 in charitable donations focused on community development and supporting 60+ local organizations.
0
4
15
@_swanson
matt swanson 😈
8 days
Free advice: a bunch of technical products should be doing a guided onboarding with LLMs I am implementing @Judoscale and moving to SLA-based queues in our app. I dumped all of our sidekiq queues/worker text into Claude. I asked it to read 2-3 blog posts (a great article from
2
1
17
@_swanson
matt swanson 😈
9 days
used claude to plan a large dns/infra migration today and it gave me a huge confidence boost and easily explained a bunch of platform questions we had tbd if the confidence is false!
4
0
25
@_swanson
matt swanson 😈
14 days
The lesson I hope to take from this: The Rails client-side optimistic UI story still has room to improve. Even the creators of Hotwire sometimes make the trade-off to do interactions server side at the cost of instant updates. (The actual product trade-off around sorting the
@wesbos
Wes Bos
15 days
Rails SSR causes this. Local first / optimistic updates gang rise up.
2
0
57
@_swanson
matt swanson 😈
16 days
Rails i18n remains undefeated... Sales team says "oh yeah we support Italian" (we dont) Ask Cursor to add it It's done in 3 minutes, opens PR, deployed Win the deal
4
3
137
@_swanson
matt swanson 😈
16 days
Fun to see a very similar `Event` system in fizzy to what we use for so much stuff at Arrows https://t.co/9f20DKDgSz https://t.co/Q95yDCoz9c https://t.co/rx8WH5vAzn
0
3
89
@_swanson
matt swanson 😈
24 days
🌢️The spicy version is 1) it's crazy to me that people think that reading the Rails tutorials in 2012 means they are done learning and 2) LiBrArY sUcKs, tHiS mUsT bE LiBrArY bUg bEcAuSe mY cOdE iS fInE
@_swanson
matt swanson 😈
24 days
The biggest "trouble" people get into with Hotwire are caused by bad habits that are hard to unlearn. The top two: - Not reading docs: most senior Rails developers have so much experience with Rails, that they skip docs and just "start using the thing" and think they will figure
2
1
36
@_swanson
matt swanson 😈
24 days
The biggest "trouble" people get into with Hotwire are caused by bad habits that are hard to unlearn. The top two: - Not reading docs: most senior Rails developers have so much experience with Rails, that they skip docs and just "start using the thing" and think they will figure
9
14
146
@jespr
Jesper Christiansen
29 days
The Ruby community is lucky to have this guy @marcoroth_
1
3
50
@_swanson
matt swanson 😈
28 days
https://t.co/fcRjWoY1OV (Again this is a great problem to have for dev-tools/chat, otherwise just wait! there is a thundering herd issue for new provider compute!)
@thdxr
dax
29 days
we passed 1B gemini 3 tokens in 2 hours we've been maxing out our per minute rate limit every minute since we launched i wonder what the number would be if that wasn't capped
0
0
0
@_swanson
matt swanson 😈
29 days
Would you rather have Gemini 2.5 pro (rock solid, stable) or Gemini 3 (SOTA but also rate-limits and outages every day)?
2
0
0
@_swanson
matt swanson 😈
29 days
PSA for those "building features that use LLMs" and not "building chat apps or coding tools", switching to a new model at release is going to be a bad time and not worth it I promise it will be fine to wait six weeks to bump your models as the infra providers ramp up servers
3
1
10
@_swanson
matt swanson 😈
1 month
Underrated perk of putting those annoying "AI Assistants" on your doc sites...converting sample code into languages without official SDKs
2
0
10
@_swanson
matt swanson 😈
1 month
Stuff I have learned so far: - there are tons of opportunities to put in LLM in a feature that aren't just "chat with my app" but it requires a big mental shift. I still have to force myself to brainstorm ideas - using structured output has gotten much better than 9 months ago -
@alexbaldwin
Alex Baldwin
1 month
@_swanson what have you learned so far? I think using LLMs to do evals is one of the most important ways to drive quality.
2
0
29
@_swanson
matt swanson 😈
1 month
I would love to read much more about using LLMs in product features and much less about using LLMs to code the features
3
3
28
@_swanson
matt swanson 😈
1 month
One of the unexpected thing about LLMs is that you end up writing huge chunks of text in your source code (this was not something we did much before). Ruby has like 5000 ways to write multi-line strings. What is your preferred method?
8
1
16