200 Days of Code: Day 3

I just realized it's almost midnight and I don't want to lose my streak so here we are.

Today I finished some more CSS lessons and then in the evening I had my meeting with my cohort lead, who is great. I hadn't started our Sinatra unit yet, so technically I was behind oops (vacation + a week of being sick will do that womp), but we were able to get through a lab pretty easily because I had done the Rack material.

What we're working on now is the most exciting part so far because we've learned enough to start to actually put things together. That being said, it's also been slow going because it's a lot of new material and new vocabulary. I always had a very simple idea of how the internet worked (clients talking to servers, making requests) but our current material is getting into the weeds so I have to make sure I move deliberately.

I really appreciate that we go through all of the foundations and basics for each piece that we learn before we move up a level of abstraction. In a college physics course I took, our professor taught us a formula and said the rest that we'd need for that semester could be derived from it. Don't ask me what they were - I ended up with a B.S. in political science - but I remember the idea: learning the fundamentals once, instead of learning a bunch of derivatives over and over. I'm okay with moving slowly now so that I appreciate how things like Rails work and so I have a better idea re: what I'm doing and how I want to do it in the future. Alternately: I suppose I'm okay doing these exercises now to make a marathon in the future less painful.

(Except I don't enjoy exercise and I assume a marathon will always be pretty painful.)