Owen Abbott

School started on Monday of this week. My IT course follows rudimentary web design with CSS, HTML, and some javascript. DePaul is for super rich kids so it’s no surprise to me that the material is exceedingly simple.

During my last class, we learned about some HTML tags.

<hr> creates a line break.

<br> creates a break.

<strong> is bold. You can also use the outdated <b> but that isn’t recommended.

<em> makes things italic.

<a> is for links.

At flatiron we only spent about a day on HTML, and at DePaul I’m going to be immersed in it for the next ten weeks. Who knows though, probably I’ll end up picking things up. It’s always good to take a close look at the deeper levels of things.

That about covers the code lesson for today.



I’m having trouble right now with my space invaders game. In order to Optimize the speed of the app, I changed all components to PureComponents.

We never really learned what ‘pureComponents’ actually *do* in the bootcamp, so I’ve been fiddling around myself to figure out how they work.

The tutorials on the internet vaguely say that they don’t re-render as often unless they detect a change. I’m not sure how that’s different from regular components — I guess they’re re-rendering each time the page refreshes? I don’t know. Will have to look into this later, I suppose.

So far, everything works except my Bunkers, which no longer register a change when a block is broken. I feel this is because they’re nested two layers deep in other components. Will fiddle around with that and report back at some point in the following blogs.



Say you have to write an if statement.

Typically, it might look something like this:

if (thing === thing2){     console.log(“sentence.”)}

That works, but you also have the option of writing a ternary statement.

Here’s what that looks like:

thing===thing2 ? console.log("sentence.") : null

Pretty neat, huh? Reduced everything to just one line.

That concludes our microlesson for today.