I get one system test working for generating the todo file and almost get the second test working. The second test that actually tests the bug we fixed. Went down a bit of rabbit hole trying to get the optimal Ruby file/directory manipulation code.
I also spent some time trying out JetBrains new coding AI. It has some issues but also lots of promise.
[Read More]Similar to the previous episode I fail at adding a system test. Should I be live coding all these failures? I think so. Maybe? Do they make boring videos? Probably. Should I say “ummm” less? Most definitely.
I think there are enough highly edited videos of success already it’s good to see some failures. To remind everyone that success takes work and often wrong paths. At least that sounds better then I don’t enjoy video editing so I just post what I record with minimal changes/edits.
[Read More]A client has an online store that is powered by an older version of Spree. I’m in the process of upgrading it and adding features to it at the same time. It’s a slow process as upgrading to newer versions of Spree, which also requires upgrading Ruby and Rails, is no easy task.
One customization the customer has is a delayed job that fires when a order is complete. The delayed job preforms some tasks that can take a while hence why they are done in a separate process after the order is completed.
[Read More]The older I get the more I appreciate code linters. Something that can detect and often correct my formatting errors? Great! One less thing I have to worry about. Then I can spend my time on more important tasks such fixing the bug, adding a new feature, or uniting/conquering the world.
The default linter for Ruby is Rubocop. It works great but I find it’s default rules to restrictive. You can change the defaults but that is time consuming and confusing. At least confusing to me. While searching for a Rubocop config that I liked I came across Standard.
[Read More]