Saturdaymp-Show

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.

I, Chris, try to add a system test for the todo bug fix in episode 5 but run into some issues. I find out I stupidly hard coded the todo file name when he first added the ability to generate a todo file in Standard. When recording this video I think that is why his system test doesn’t work but upon re-watching this video I have my doubts. Only time will tell if my doubts are correct or not.

I add a unit test for the Standard Ruby linter bug fix done in the last episode. When adding the unit test I find out someone has improved the todo generation logic. Thank you. I also find a remove a redundant test.

Read about the bug being fixed here.

I duplicate a todo file generation bug in the Standard (Ruby linter) and come up with a possible fix but don’t actually get to the fix.

Read about the bug here.

See episode #1 where I create a Docker development environment for Standard:

As a bonus at the beginning of the video I upgrade RubyMine to fix the bug we encountered in episode 2:

I, Chris, spend a lot longer then I anticipated filling out the JetBrains Developer Ecosystem Survey 2023. Thought it would be a quick half-hour but turned into 2 hours. Sorry in advance for the long video.

If you use the link below to take the survey I might win a prize: