Lucian Ghinda
@lucianghinda.com
1.8K followers 760 following 1.9K posts
Product Engineer, Ruby on Rails Developer ‣ Curator of newsletter.shortruby.com ‣ Helping #Ruby developers design better test cases at https://goodenoughtesting.com
Posts Media Videos Starter Packs
Pinned
lucianghinda.com
Only 7 spots are still available for the #GoodEnoughWorkshop happening on 12 December at 15:00 UTC. Last days for getting the tickets with discounts!

You can buy a ticket here lu.ma/533zg5zq
Reposted by Lucian Ghinda
okuramasafumi.com
github.com/sponsors/ok...

I just setup my GitHub Sponsor page. I hope my work helps you in some ways, and I'd be so happy if you support me (or more specifically, my coffee!)
Sponsor @okuramasafumi on GitHub Sponsors
I'm OKURA Masafumi, the creator of Alba gem. Alba is the fastest JSON serializer for Ruby.
github.com
Reposted by Lucian Ghinda
st0012.dev
🎉 Incredibly honored to be a Ruby Prize 2025 finalist! Thank you to everyone who has supported my work on IRB, RDoc, debug, ZJIT, and other Ruby projects.
See you in Matsue!

rubyprize.jp
Ruby Prize 2025 | 最終ノミネート者決定 | RubyPrize
rubyprize.jp
lucianghinda.com
2️⃣ Discussing their work environment, they seem to hint to a concept I've mentioned before: the necessity of slack time (not time spent on Slack) to experiment and innovate without the constant pressure of immediate productivity.
lucianghinda.com
I reviewed a paper titled "A Model of Creativity and Innovation in Organizations" by Teresa Amabile from 1988.
Here are two quotes from 1 person part of the research (remember, this is from 1988):

1️⃣ A good reminder that ideas can be found in "variations" or "deviations"
A screenshot of a text saying: "I think of myself as someone who generally thinks along different directions than the average person. I'm always looking for the interesting twist that something might have. I'm not interested in the normal direction that a given piece of work might progress into; I am more interested in the variations, the deviations that might result."
Reposted by Lucian Ghinda
joel.drapper.me
YAML is weird. And not in a good way

That’s why I maintain Ruby Schema, a collection of config schemas for the Ruby community.

Our i18n schema prevents this boolean problem, helping the YAML LSP show errors.

github.com/yippee-fun/r...
lucianghinda.com
Ruby on Rails uses the gem psych to load the YAML files for locales transforming values like Yes/No, yes/no, YES/NO, On/Off, on/off, ON/OFF to be converted to booleans as defined in YAML v1.1
Ruby on Rails uses the gem psych to load the YAML files for locales transforming values like Yes/No, yes/no, YES/NO, On/Off, on/off, ON/OFF to be converted to booleans as defined in YAML v1.1
lucianghinda.com
The difference is documented in psych gem test suite for example:
The difference is documented in psych gem test suite for example:
lucianghinda.com
But there is a difference between Psych and YAML 1.1 with regards of how to parse Y, y, N, n:
Screenshot showing the difference between Psych and YAML
lucianghinda.com
Ruby `psych` gem implements YAML version 1.1 that defines a Boolean like this:
Ruby `psych` gem implements YAML version 1.1 that defines a Boolean like this:
lucianghinda.com
The following values will be converted to FalseClass:
The following values will be converted to FalseClass:
lucianghinda.com
Ruby on Rails used through i18n gem the psych gem for loading YAML and here is how it loads values for TrueClass boolean:
Ruby on Rails used through i18n gem the psych gem for loading YAML and here is how it loads values for TrueClass boolean:
lucianghinda.com
Ruby on Rails uses the gem psych to load the YAML files for locales transforming values like Yes/No, yes/no, YES/NO, On/Off, on/off, ON/OFF to be converted to booleans as defined in YAML v1.1
Ruby on Rails uses the gem psych to load the YAML files for locales transforming values like Yes/No, yes/no, YES/NO, On/Off, on/off, ON/OFF to be converted to booleans as defined in YAML v1.1
Reposted by Lucian Ghinda
pragprog.com
“Rails is an opinionated framework, and this is an opinionated book.” ~Introduction

One of today's Pragmatic Picks - 40% off with code PragPicks
pragprog.com/titles/...
@noelrappin.com
Reposted by Lucian Ghinda
lucianghinda.com
And I think this part here is a normal expectation for any AI code contributed to a serious project:
In a perfect world, AI assistance would produce equal or higher quality work than any human. That isn't the world we live in today, and in most cases it's generating slop. I say this despite being a fan of and using them successfully myself (with heavy supervision)!  When using AI assistance, we expect contributors to understand the code that is produced and be able to answer critical questions about it. It isn't a maintainers job to review a PR so broken that it requires significant rework to be acceptable.
lucianghinda.com
We might start to see this kind of request to disclose use of AI when contributing to open-source:
github.com/ghostty-org...
An image of a text saying something like: "If you are using any kind of AI assistance while contributing to Ghostty, this must be disclosed in the pull request, along with the extent to which AI assistance was used (e.g. docs only vs. code generation). If PR responses are being generated by an AI, disclose that as well. As a small exception, trivial tab-completion doesn't need to be disclosed, so long as it is limited to single keywords or short phrases."