200 Days of Code: 6 - 10

This past weekend I finished up the first part of our Sinatra material, working with Sinatra and forms and getting the files to all talk to each other correctly.

Tonight I worked with my technical coach to practice what our next project will look like. I AM EXCITED TBH.

I was scared of our first project. It was kind of like the first time you ride a bike without training wheels: could be fun, could be death. And then you smack into the side of your dad's truck and fall down and it's fine.

And by you I mean me. I definitely did that.

Read More

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.

200 Days of Code: Day 1

So obviously my new year's resolution has been a fail. I keep thinking about writing, and then I don't, either because I get busy doing something else or I don't feel like what I have is worth sharing.

But, I know that's wrong and also not good if I am supposed to be in the habit of explaining my work and talking about what I'm learning.

I follow the #100DaysofCode hashtag on twitter and it occurred to me: maybe I'll just count the days between now and when I'm done with school and do X days of code.

So, assuming I'm done 10 months from when I started, today happens to make it exactly 200 days until we're done (not including the last day).

If all else fails, I can at least write about what I worked on during the day and what I learned. BABY STEPS.

We can do this.

My First Project!

I am exhausted. My brain is toast. I would come home from work, eat a quick dinner, and go to my study spot where I'd work until midnight or so. This worked a lot better when I was 21 and full of YOUTH. Right now I am very excited to get a good night's sleep.

But, I'm really, really glad we did this. I learned so much so quickly, and to be honest I am still surprised by just how much information I've absorbed since we started at the end of November. THE BRAIN IS AMAZING.

Now that we've made one, I think I could figure out how to make another one. Maybe. But I am definitely (1) still excited about learning to code, (2) still having fun even when it's hard, and (3) so grateful for everything.

Read More

Stringing Us Along

Today we are going to talk about strings, specifically in Ruby: What are they? How do I make them? What can I do with them? By the end, both of us should have a lot of good information in one place so we don’t have to hunt for it later.

What is a string?
A string, at its most fundamental level, is a collection of bits and bytes. At a people-level, it’s the letters and other characters we use to make sentences. When I think of strings, I think of sentences first. Strings can be a lot of things: a letter, a punctuation mark, a space, jibberish — but it’s code that doesn’t represent something else, unlike a variable or a class.

For example:

Read More