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.)

200 Days of Code: Day 2

The last few days, I've been working my way through the HTML/CSS/Rack "bonus" material, since I know I need to know it one way or another.

I went through FreeCodeCamp's HTML/CSS course last summer when I was deciding whether this is something I enjoyed or not, so luckily a lot of the HTML/CSS is review. (But really - FreeCodeCamp is delightful.)

The Rack portions were challenging since it's the first time I've learned how a website is made from scratch and made to talk to the user. I'm currently exhausted but it's probably a good idea for me to write down what I learned at some point.

We've been working through the lessons with a code-along for a real-estate website. Some portions are really a code-along, and some are done with labs and local tests. I'm actually really enjoying it; it's been satisfying to see how it's growing and to learn how to add pieces properly.

My dad's an engineer and growing up I heard pretty often: "proper preparation prevents piss poor performance." I want to make sure that I continue to learn to do things correctly, even though at first it's going slowly.

Right now I am ready for bed. I didn't get much sleep last night and tomorrow is going to be a long day at work. Sometimes you have to know when it's time to give up for the day. But! This is my first time actually following through on my "write a note each day" plan so that's exciting.

One day at a time.