Matheus Richard

@matheusrich
40 Followers
63 Following
63 Posts

🇧🇷 Senior developer @ thoughtbot.

📝 Blogging @ https://tbot.io/blog/matheus

💎 Organizer of http://rubydf.com

@myrialux What you've described sounds like https://railsbytes.com/
Rails Bytes

TIL about the name_of_person gem. Pretty cool!

https://github.com/basecamp/name_of_person

GitHub - basecamp/name_of_person: Presenting names of people in full, familiar, abbreviated, and initialized forms (but without titulation etc)

Presenting names of people in full, familiar, abbreviated, and initialized forms (but without titulation etc) - basecamp/name_of_person

GitHub

If you're building a PWA with Rails don't forget to ensure that you're rendering valid JSON on routes like /manifest.json.

I've added a test for that:

@hschne that said, Matz said that he has a higher level API in mind that will use Namespace. I'm interested in seeing where it goes and I'm happy to change my opinion.

@hschne I just never ran into any problems like that. I think the community has been good with managing the global namespace.

Also, the idea of multiple versions of a library being used seems like a nightmare to me.

@hschne Why do you think it's exciting? I fail to see the benefit, honestly.
accent-color is so easy and useful. CSS gets better everyday!
The Ruby dev iceberg

There has been a push towards fixtures for a while, but this global shared state is hurting me. It's hard to know which records are available for any given test, or if I should just modify a particular record for the current test. You change one thing, it breaks a test elsewhere.

How are y'all managing that? It seems messy.

@getajobmike Probably extracted from 37signals