![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ironymaideni stayed up late several nights this week to finish the homework i was complaining about on Monday. as it was, there was a point where i gave up on getting 100% test coverage and just turned the damn thing in. (there were three fucking lines that i couldn't seem to exercise.) i asked for any advice on how to actually get that last bit in the comment on my pull request.
so yeah...i got full points on the assignment and teared up a little at getting praise for it.
this week is all about debugging - we have a buggy script that runs the functions we wrote for the previous assignment and we need to use logging and debugging techniques to understand what's going wrong and fix things. this is much more intuitive and fun for me - scratches the same itch as untangling knotted yarn or solving a maze. banging my head against all those objects really does seem to have embedded some OOP understanding; i'm looking at the script and seeing things that are subtly wrong just reading it, which is a nice feeling.
Excellent work! I always think that 100% coverage is a questionable goal in practice; however, here is a command you will find really useful to see more details of coverage issues...
so yeah...i got full points on the assignment and teared up a little at getting praise for it.
this week is all about debugging - we have a buggy script that runs the functions we wrote for the previous assignment and we need to use logging and debugging techniques to understand what's going wrong and fix things. this is much more intuitive and fun for me - scratches the same itch as untangling knotted yarn or solving a maze. banging my head against all those objects really does seem to have embedded some OOP understanding; i'm looking at the script and seeing things that are subtly wrong just reading it, which is a nice feeling.
