Scott Watermasysk
@scottw.com
Husband, Father, & purveyor of fine Ruby on Rails apps. Always building something.
An example: we use the Strict gem (which is fantastic). However if you default to an array or hash, you will end up with a hidden scope bug that is not obvious at first.
We have a custom rule that will warn you to use a lambda and autocorrect it.
We have a custom rule that will warn you to use a lambda and autocorrect it.
November 24, 2025 at 2:23 PM
An example: we use the Strict gem (which is fantastic). However if you default to an array or hash, you will end up with a hidden scope bug that is not obvious at first.
We have a custom rule that will warn you to use a lambda and autocorrect it.
We have a custom rule that will warn you to use a lambda and autocorrect it.
Capitalism is the worst, except for everything else.
November 24, 2025 at 1:22 PM
Capitalism is the worst, except for everything else.
One of my favorite things to do with AI is generate new rules that help keep the team in sync with our conventions.
This would have been hard to justify the time in the past, but now in 10 minutes or so we can make great progress.
Plus we can then let AI fix previous work.
This would have been hard to justify the time in the past, but now in 10 minutes or so we can make great progress.
Plus we can then let AI fix previous work.
November 24, 2025 at 1:19 PM
One of my favorite things to do with AI is generate new rules that help keep the team in sync with our conventions.
This would have been hard to justify the time in the past, but now in 10 minutes or so we can make great progress.
Plus we can then let AI fix previous work.
This would have been hard to justify the time in the past, but now in 10 minutes or so we can make great progress.
Plus we can then let AI fix previous work.
For Zed and Claude, I use its integration for small tweaks or things like “explain this selection“, for anything larger I just use Claude in the terminal. History/etc is much nicer.
For tips, I like that you can launch cli apps (like lazygit) using the spawn feature.
For tips, I like that you can launch cli apps (like lazygit) using the spawn feature.
November 17, 2025 at 11:52 PM
For Zed and Claude, I use its integration for small tweaks or things like “explain this selection“, for anything larger I just use Claude in the terminal. History/etc is much nicer.
For tips, I like that you can launch cli apps (like lazygit) using the spawn feature.
For tips, I like that you can launch cli apps (like lazygit) using the spawn feature.
Such a joy to watch, especially after what they put is through last year.
October 28, 2025 at 11:29 PM
Such a joy to watch, especially after what they put is through last year.
Everything we do is immediately consistent.
We are event sourcing all the data, but in hindsight we should have only gone this route with some of the data. The history aspect is nice, but end users only care about the current state.
We are event sourcing all the data, but in hindsight we should have only gone this route with some of the data. The history aspect is nice, but end users only care about the current state.
October 24, 2025 at 8:54 PM
Everything we do is immediately consistent.
We are event sourcing all the data, but in hindsight we should have only gone this route with some of the data. The history aspect is nice, but end users only care about the current state.
We are event sourcing all the data, but in hindsight we should have only gone this route with some of the data. The history aspect is nice, but end users only care about the current state.
It appears there used to be a way to override themes in a config file per project, but I have not been able to make it work.
This makes having multiple worktrees open at the same time a bit more challenging, but the other benefits make up for this.
This makes having multiple worktrees open at the same time a bit more challenging, but the other benefits make up for this.
October 24, 2025 at 12:35 AM
It appears there used to be a way to override themes in a config file per project, but I have not been able to make it work.
This makes having multiple worktrees open at the same time a bit more challenging, but the other benefits make up for this.
This makes having multiple worktrees open at the same time a bit more challenging, but the other benefits make up for this.
We took a lot of inspiration from your writings (commands and deciders are core components).
We ultimately wrote our own event sourcing layer.
We ultimately wrote our own event sourcing layer.
October 24, 2025 at 12:22 AM
We took a lot of inspiration from your writings (commands and deciders are core components).
We ultimately wrote our own event sourcing layer.
We ultimately wrote our own event sourcing layer.
Sure. It is an application for managing medical coder schedules. Hard to explain in a toot, but the event sourcing is primarily applied to managing (recurring) schedule changes and overrides.
October 24, 2025 at 12:22 AM
Sure. It is an application for managing medical coder schedules. Hard to explain in a toot, but the event sourcing is primarily applied to managing (recurring) schedule changes and overrides.
This looks great. I have been using Strict (looks very similar) for an Event Sourced app the year and it has been fantastic- github.com/kylekthompso...
Have you guys seen/checked that gem out as well? cc @fractaledmind.bsky.social
Have you guys seen/checked that gem out as well? cc @fractaledmind.bsky.social
GitHub - kylekthompson/strict: Strictly define a contract for your objects and methods
Strictly define a contract for your objects and methods - kylekthompson/strict
github.com
October 23, 2025 at 11:47 AM
This looks great. I have been using Strict (looks very similar) for an Event Sourced app the year and it has been fantastic- github.com/kylekthompso...
Have you guys seen/checked that gem out as well? cc @fractaledmind.bsky.social
Have you guys seen/checked that gem out as well? cc @fractaledmind.bsky.social