- What did you learn yesterday?
- What are you going to do today?
- What do you expect to learn?
Yesterday I ended up spending most of the day on the Agile Web Development with Rails 4 book; I didn’t actually realize it was a great big tutorial. I think that’s why it took me so long to pick up, 434 pages is lot when you’re reading about Rails. The tutorial is great, though! I haven’t hit anything totally unfamiliar, so it’s nice to know that I haven’t *forgotten* Rails, it’s more that that knowledge got buried under other stuff in the five months since code school. I may work on that a bit more this morning before Brandon and I get together to talk about the API stuff. Speaking of the API stuff, I got Kevin to explain some of it to me last night, and I think it’s making a bit more sense. He doesn’t know Rspec at all, though (finally a thing he doesn’t know!) so I didn’t write any tests, instead using an app we discovered at TIY, Postman, to run the code and make sure that I got the correct responses.
Today I think I’m going to work on the Rails 4 book until around 1, when Brandon and I are going to work on the API stuff. While I think I get it more than before, there’s still a lot going on that I don’t get, and testing is just basically a black box to me. I downloaded the slides from the Code School API course and have been trying to use them as a guide, but I’m never really sure what’s actually relevant and what’s overkill. For instance: are we doing integration testing? Or am I only specifically testing the code I wrote, which is in the controller and model? *Is* that integration testing? I understand the value of TDD, but the process itself is still vague. I think part of that is because the code itself is still vague, so hopefully someday I’ll have a big “AH HA!” moment and it will be glorious.
I expect to learn how to write tests for APIs, probably the difference between integration tests and model/controller tests and how the whole thing works together to form a cohesive whole.