| Short Ruby Newsletter | https://shortruby.com |
| Website | https://allaboutcoding.ghinda.com |
I can access it with `read_attribute_before_type_cast` but I would like an easier way to access it.
So my current solution is to write something like:
Rails developers help me with naming and maybe a solution:
When creating a `time` column in Rails using PostgreSQL it correctly sets the time without date type on Postgres part but when accessing the attribute when doing typecasting Rails will load it as DateTime
There are already five participants registered for the next #GoodEnoughTesting workshop, which will take place next week.
There are 15 places in total, but I might close the registration at 10 people because this is a new version of the workshop, and I want to have time for feedback.
Just refactored the 404 and 500 pages of #GoodEnoughTesting website to be a bit more in line with the topic :)
The beauty of listening to a #Rails podcast about a Rails feature with @Rosa Gutierrez on a platform @Buzzsprout that is built with @Rails !
https://onrails.buzzsprout.com/2462975/episodes/17305252-rosa-gutierrez-solid-queue?t=0
In this episode of ‘On Rails’, host Robby Russell (@planetargon) chats with Rosa Gutiérrez, Principal Programmer at 37signals, about the technical decisions behind Solid Queue - a database-backed job queue replacing Resque in their Rails apps.Rosa...
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:
What kind of methods should *not* be converted into endless methods? Methods that call `puts`? Methods include `==`? Methods with many args? How complex can a single-line method get before it should not be converted into an endless method?
Personally I think that methods who's body is a single equals comparison (ex: `@foo == 42`) look confusing when converted into an endless method due to the combination of `=` symbols.
def forty_two? = @foo == 42
vs.
def forty_two?
@foo == 42
end
I am working this weekend to finalise the content for the upcoming #GoodEnoughTesting workshop:
- I am trimming a lot of the previous content to keep it to only the essential
- Rethinking the code and exercises I previously used
Testing isn’t about doing everything. It’s about doing the right things and doing enough of them to sleep well at night.
If you're trying to balance quality, speed, and complexity, risk gives structure to your thinking and clarity to your priorities.
Use risk as a spotlight.
Just refactored the 404 and 500 pages of #GoodEnoughTesting website to be a bit more in line with the topic :)
Matheus Richard
postmodern