remosu.bsky.social
@remosu.bsky.social
Reposted by remosu.bsky.social
Another technique that is not as effective as this, but can be done w/out gems is to do 2 things: 1) stop using strings & hashes as params, and 2) use keyword arguments for every method and initializer.
it causes bugs that normally result in nil references to be surfaced at their source, during dev
it causes bugs that normally result in nil references to be surfaced at their source, during dev
Ruby is an inherently dynamic language. Statically type checking Ruby is impossible even if you can statically type check some parts. However, I think you can get ~60% of the benefits of type checking at runtime for ~10% of the effort. At the same time you can make your code easier to navigate.
November 13, 2024 at 7:08 PM
Another technique that is not as effective as this, but can be done w/out gems is to do 2 things: 1) stop using strings & hashes as params, and 2) use keyword arguments for every method and initializer.
it causes bugs that normally result in nil references to be surfaced at their source, during dev
it causes bugs that normally result in nil references to be surfaced at their source, during dev
Reposted by remosu.bsky.social
Hey folks you don't need to hear this from me but anyway go vote Kamala and put an end to this shameful period in US politics.
I hope the rest of us will do the equivalent in our respective countries as we get our turn.
I hope the rest of us will do the equivalent in our respective countries as we get our turn.
November 4, 2024 at 8:27 PM
Hey folks you don't need to hear this from me but anyway go vote Kamala and put an end to this shameful period in US politics.
I hope the rest of us will do the equivalent in our respective countries as we get our turn.
I hope the rest of us will do the equivalent in our respective countries as we get our turn.