Reflections on Group Work for Milestone 1

Screen Shot 2015-04-12 at 8.02.52 PMThis week I was AFK in the Grand Canyon. I stayed in touch with my collaborators by checking my text messages for updates on the project and followed the updates that were being made online via the GitHub issues.

Before I left for the Grand Canyon I was assigned the task of transitioning the routines section of our mock up website to our Play Framework Application. I used the Play Framework applications we had created in class to learn how to transfer the simple mock up version of the site to a functioning in-memory database with forms and backing classes that functioned.

I ran into a few problems when I committed my changes and merged them back into the milestone-1 branch. I had to do some clean up. Now when I push changes, I always sync both branches with the repository before merging them. This has resulted in less surprises and a cleaner process.

I returned from the Grand Canyon to review the updates that had been made to the system. I tested the system on mobile devices. I found about 7 bugs and posted them as issues on GitHub with screenshots showing the bugs.

Play With Magic is an online repository of magic routines.

The most valuable part of this milestone was to seed the application with real information. We created an application that allows users to create, read, update, and delete routines and sets. The three components of the application are:

  • Users
  • Routines
  • Sets

The initial mock up of the application showed what our application would look like. Mark, Patrick, and I met many times over Skype with professional magicians Lee Asher and Wayne Houchin. Lee talked about how much he wanted to be able to learn more about magicians’ interests and influences. Wayne advised us to focus on the energy that a magician’s set is meant to create.

After Mark, Patrick, and I met to discuss the new things we had learned. I was guilty of wanting to pivot the application somewhat to support mentorship on the website. But I was happy that we were able to focus on completing milestone-1 by sticking to our initial goals.

Once we had these in the in-memory database functioning properly we started seeding the Routines database with professional routines we found on the following websites:

This first milestone showcases the basic functionality of the website. Our group came up with the initial idea of creating a website that allows magicians to create sets. As we talked to professional magicians many new ideas for the application came up.

Play With Magic could be updated to allow amateur magicians to request help with their routines and sets from professional magicians.

Meeting on Skype versus meeting in person has been very productive. Meeting in person and coordinating a physical location to meet was problematic. Meeting on Skype, on audio, has worked out well and provided us with a way to meet and ask questions to clarify the goals of the project. I found that tagging issues and assigning them on Github made the process of keeping our tasks manageable.

I would like to focus on the look of the website for the next milestone. We also need to focus on linking the related routines that each magician has created. For milestone 1 we focused on creating the CRUD capabilities for Users, Routines, and Sets. I’m happy we were able to create the system to add and edit new content for the site. I would like to focus on making the materials in our routines reusable. Tagging capabilities will also allow us to provide search functionality for our users.


Reflections on Testing and Templates

When I was a kid, my mom sewed all of our shorts. I remember looking at the patterns that she cut out from McCall’s pattern books and laid them out on the fabric. I used to enjoy going to the fabric shop and running my fingers over the different swaths of fabric. I could close my eyes and from the feel of the fabric on my finger tips I could almost tell what it was made from: cotton, rayon, etc.

Metaphors work really well for me. They help me relate the concepts in computer science to real world, tangible things. Once I can map a concept in computer science to a real thing that I can feel and touch I can create a complete mental model in my head.

If I can see a Scala template as a McCall’s pattern for making clothes, I can see it and understand it and get more fluidity with the material.

I would like to get as good at knowing the feel of Play Framework Templates. So much that I am able to write out things and know how the process goes from parts to a full whole.

I took a different approach this week. I am noticing a common thread in my WODs. That I get caught up in understanding all the small details and why things are the way they are and that keeps me from finishing things.

I understand that I can work on things and I have to get over my procrastination. That is a new thing to learn this week. I got into it and just dove straight into the WOD videos. Then once I had completed the WOD with the instructor I circled back and watched the videos over. I looped them in my apartment to study up on the concepts.

Digits Test

During this WOD I learned how to automate testing of my pages. In the past when I’ve coded up pages and put them online I’ve had to click through the forms myself and see if the forms submitted or if there were errors in the processing. With integration testing in play, I can actually code the behaviors that the user would do and have the computer automate the test and actually perform a significant function. I wish there were something like this for PHP.

  • First try: AV in 30 min 20 seconds.

Digits Text Template

In computer science there is a concept called DRY. DRY stands for Don’t Repeat Yourself. Another great feature of Play is the ability to swap out components by creating templates. These reusable pieces of code can be created once and used all over the application an infinite number of times.

The best part of reusable code is that if it needs to be updated you just need to update that single instance of code and it will be updated across the entire web application.

The specific thing I learned in this WOD was how to update the variable at the top of the Scala page to map it to a specific Play component. When I compiled my project the first time I got a ton of errors and did not know why. Then I looked at the top of the time and realized I had not imported the bootstrap3 library.

  • First try: 14 min 30 seconds.

Digits Selection

It was good to finally start working with different types of form variables. In this WOD I added a play template form drop down box. This WOD taught me how to specifically target a form field and inspect it with firebug in Firefox. This allowed me to figure out exactly which class/id pertained to this form field so I could call it programmatically.

  • First try: DNF 1 hour 23 min 40 seconds.

Digits Custom Template

The purpose of this WOD was to combine a series of templates into a single template to display a text input and a drop down on a single row in a form. The best thing about this WOD was the ability to set form attributes inside of a row without having to specify the number of characters the form would accept so that the form would extend itself in a visually appealing manner. The combination of Play and Bootstrap makes forms look beautiful.

  • First try: 15 min 30 seconds.

Digits Init

This WOD taught me how to seed the in-memory database with content. I liked this WOD because it set up a very easy way to set global variables in the application. Although the WOD did not instruct us to do specific routines upon the end of the application, I was glad to see that there were programmatic hooks to enable behaviors to be triggered at the start and end of the application. Play seems extremely robust. I am excited to use the features I learned this week in our PlayWithMagic application.

  • First try: 9 min 32 seconds.

Lessons Learned

Two times already, I have merged my changes into the master branch without setting a commit on my branch in the code and when I merged it back into master, the updates have been lost. This happened when I finished the last WOD and the custom Scala template I create to contain both the telephone number and the telephone type in one Scala template were wiped out by the merge.

This is good to learn because I would hate to see this affecting the work done by my project peers. I like that I have an open source project that I can point to. I have open source experience now!

Github network graph of this week’s WODs

Screen Shot 2015-03-31 at 11.36.47 AM

Reflections on Group Work

When I was growing up I wanted to be either a magician or an inventor. With computers I get to do both. I’m excited to announce that I’m working on a new open source project called PlayWithMagic with two very capable software engineers Patrick Karjala and Mark Nelson.

We’re creating a web app that allows magicians to share and remix their routines. Users can create their own sets “automagically.”

Mark’s hosting our site on his Rasberry Pi server.

“Good programs aren’t written or built, they’re grown.” – Mike Muuss

How did you divide up the work?

This week we got together 4 times to discuss our initial ideas. We split up the mock up work and reconvened in a few days. Once we had mocked up the pages we researched our service by meeting with professional magician, Lee Asher, on Skype. Mark worked on the README for the project. Patrick worked on the homepage, the user login on the navigation bar, and I created pages to display the user’s profile, a page to show the routine, and the pages to create a new user and a new routine.

This slideshow requires JavaScript.

How did you coordinate development?

Before we met each of us came up with a list of questions and updates. When we met we set an agenda. The conversations were smooth and we were able to agree on what features to pursue.

We talked about the goal endlessly.

Github allowed us to keep up with each other’s progress. This helped to ensure that issues were taken care of. We used the issue tracker to determine what we wanted to focus on next. We talked for a while about the application. Then we mentioned some of the things that you have to consider at the beginning of any web project. There have to be log ins and user profiles. And we planned around our idea. Like a bottom up approach. I wrote up a bunch of user case scenarios. And Mark and Patrick drew up data models and program flows.

This slideshow requires JavaScript.

Once I knew what I was responsible for, I added them to github as issues and assigned them to myself.  I did all of my mockup coding over the course of 6 hours, from 7:41pm to 2:30am. Then I pushed all my changes to our repo on github and watched something on Netflix before I went to sleep. Looking at this gif and it looks funny. But the funny thing is, I can care so much about something that I can lose myself for 6 hours refining the code to make it beautiful and refined.

Was the group experience a positive one?

The group work was profoundly positive. We get along as a group and we all get our work done quickly. We communicate well and let each other explain our ideas completely before going forward. When we met at Patrick’s workplace for one of our meetings. He taught me and Mark how to use LESS.

This slideshow requires JavaScript.

What should your group change in order to work more effectively during the remainder of the semester?

We’re hitting all the goals. Issues are divided evenly. And the project is moving so fast that we are literally at the edge of our understanding. We’re adding form validation and database support as soon as we learn how it’s applied in the Play Application framework. We are right on track to get this application finished on time.

Reflections on MVC

images.duckduckgo.comMVC is a design pattern that allows coders to keep unrelated portions of their code separated into logical chunks so that the implementation remains as loosely coupled as possible. We use MVC to make our designs scalable, reusable, and clean.

This week was really rough.

There were so many things to incorporate into my understanding of the Play Framework. The CRUD update WOD was by far the most difficult. Toward the end of the week I was kind of wondering what I was doing as I was doing it.

I understand, on a very basic level, how MVC works, but getting good with doing it by default and in some kind of flow state seems impossible at this point.

I understand the concepts we covered this week but the break-neck speed of the material is daunting. I need to plan for more time to focus on redoing the final two WODs. Adding a model that allows for persistent data across the application is encouraging. I’m proud of myself for sticking with a persistent bug I encountered. I checked my code line by line 3 times and still my application would not retain form data. Only after restarting my computer, taking a walk around campus, and running ‘activator clean’ did my form data finally start working.

The concepts at this point are falling into place extremely slowly.

I’m anticipating more time with the material will make the concepts much clearer. Surprisingly, I am not daunted by Scala expressions intermixed with HTML and Java code. Maybe it’s because I’ve been using Objective-C for 5 years and I’m used to the overabundance of brackets.

This slideshow requires JavaScript.

Digits Mockup

I am consistently amazed by how beautiful my web applications are now that I am using Twitter Bootstrap.

The integration of fonts, and solidly positioned (don’t forget responsive) divs makes me happy. During this WOD I quickly set up a bootstrap application and added a ‘zebra type’ form. Just last year, I remember coding my web forms in PHP and having to check the modulus of the returned content from the database to determine which row to shade off-color. I love Twitter Bootstrap.

I did not finish this WOD the first time through because I spent a lot of time with Bootswatch picking out my favorite theme. I did learn how to include my theme dynamically with a relative stylesheet. I have that code saved for later when I want to swap out the standard twitter bootstrap CSS with a customized theme from Bootswatch.

  • First try: DNF at 39 min 35 sec
  • Second try: AV at 21 min 16 sec

Digits Form

For the process of updating forms to use the Play Framework I created a list for myself in TextEdit on my desktop. The four steps to update web forms from HTML to the Play Framework are as follows:

  1. Create a backing class for form.
  2. Make view dynamic.
  3. Handle form in controller.
  4. Add POST request to routes.

I’m not quite at the point of translating this list to code but it helps to know the list or have a crib sheet to make the updates faster and faster. I will continue working to commit these words to memory. Even more to work through this process and immediately be able to code it up fast.

I did not finish this WOD within the time allotted. Before I attempted the WOD again, I reviewed the Play Form Screencast and took notes on exactly what was updated and in what order. I am learning that the order of the updates matters. Not only do I get code completion in IntelliJ if I do the updates in a particular order, but wear grooves where my feet have gone before. I can code faster if I code in the same manner over and over.

  • First try: DNF at 43 min 55 sec
  • Second try: AV at 23 min 14 sec

Digits Form Validation

The form validation WOD was my favorite this week. Everything with form validation is straightforward. I understand it and I was able to complete this WOD on the first try. As with the first WOD this week, I am just amazed by Twitter Bootstrap. The ability to style up the forms themselves to show the status of the input is beautiful in its simplicity and calm presentation.

  • First try: Rx in 17 min 33 sec

Digits Model

I did not feel as prepared for this module as I did for the previous WODs this week. I did not feel that the screencasts that led up to this WOD made the application possible. Perhaps I missed some of the supplemental information in the readings.

I had a very hard time conceptualizing the updates I was making in this WOD. I will have to redo this WOD many more times to first get the understanding of the material, then many more times to get the fluidity needed to complete it in under 18 minutes.

  • First try: DNF in 28 min 50 sec
  • Second try: DNF in 32 min 14 sec (Could not complete this WOD on my own. Had to rely on the screencast.)

Digits CRUD

I tried my best to do this WOD on my own the first time but I did not feel prepared for the material. I believe that I need to devote more time to reading the supplemental material. Rather than rely on the screencasts leading up to the WODs I should have devoted more time to finding supplemental material.

This practice WOD had me going all over the application to update the file with a file. I understood the updates we were making but the dependencies within the code to sustain the updates was jarring. I feel very off balance with the material in this practice WOD. I am planning to get up early tomorrow and get in as many redos with this practice WOD as possible before class.

  • First try: DNF in 1 hour 15 min 7 seconds

Lingering Questions

What’s the best way to handle authentication inside of a Play Framework application? Patrick found a third-party framework called SecureSocial that handles authentication. I haven’t had a chance to look into it deeply. But from my research online, there are a number of simple tweaks we can do the application to require simple page-based authentication.

I want to find something that has as few dependencies as possible. I also want to find something that is easy to upgrade. I feel that the PlayWithMagic code we are working on will be used in the future by Mark and I want to be sure that it ages well.

Reflections on Web Application Frameworks

playEl Dorado, the “mystical city of gold,” never existed. The Fountain of Youth was a joke. But people talked like it was true.

Things that sound too good to be true usually are. That’s why I was skeptical when I heard about Play.

First, if you’re not acquainted with the latest Web Application Framework, Play is a “lightweight, stateless, web-friendly architecture.”

The Play Framework combines HTML, Javascript, CSS, and databases into a single stack. I love it. But I’m hesitant to sing its praises too soon. I haven’t even interacted with its database. I’m hoping it’s a flat file database. If it performs like the rest of the Play Framework I may become a true believer. More interaction with the framework is necessary.

Progressively moving toward web authoring singularity

This week I completed four WODs. I wasn’t able to finish all of them in before my timer went off. There were a few things that did not work the first time through that I will list out as I go through all of them. You need to write out references to static elements like images and css files with routes. I was not used to this.

Integration and Application tests validate the code. Play enables me to check the validity of the code by running tests to ensure that everything’s working as it should.

The WODs I worked on this week used the following technologies:

WODs I worked on this week

Clean Play Java

For this WOD I downloaded the Play Framework and compiled a new project on my computer. I ran the code, ran the unit tests, and started up a local instance of a Play-Java application on my computer. Once I set up a new repo on GitHub I accidentally created a .gitignore file and the Play Framework did not like that I had created my own .gitignore file and the IntelliJ would not allow me to push my changes to my repo. It was confused by the two .gitignore files in my directory. I ended up created the repo from scratch and I did not set a .gitignore file in Github.

  • DNF on the first try in 1 hour and 12 minutes.
  • Finished on the second try in 14 minutes and 36 seconds.

Play Bootstrap Browser History

For this WOD, I created a website that simple fetched a repository that had been created earlier. This repository creates a Play application and integrates Bootstrap. I added this repo as an upstream master and merged the repo with mine. I compiled and ran the code with Activator and the application loaded on at localhost:9000 on my machine. Then I ran the code through CheckStyle to make sure it passed all of the tests.

  • Finished on the first try in 26 minutes and 23 seconds.
  • Finished on the second try in 21 minutes and 4 seconds.

Multi-Page Play Bootstrap Browser history

For this WOD I updated my Play Bootstrap Browser History project. Instead of serving all of the content on a single page, I updated the code and split the content from the index page onto multiple separate pages. I updated the navigation to point to the new pages and wrote some unit tests to ensure that the new pages were being rendered by the Play Framework properly. Once I finished updating the file, updated the routes, and wrote the unit tests I tested out the application and it worked wonderfully.

  • Finished on the first try in 14 minutes 23 seconds.
  • Finished on the second try in 7 minutes and 37 seconds.

Play Responsive Kamanu

This WOD was very much like the previous WOD. The only difference in this WOD was that I had to update the navigation in the header. This one took much longer than I expected because I did not heed the advice to update the image files in the Play Application Framework to look for images along the route. Once I learned that I needed to update the file paths in the play application with relative computed locations I was able to update my code and complete the WOD successfully on the second time through. This one was basically updating the Twitter Bootstrap navigation bar with custom images and formatting.

  • DNF on the first try in 30 minutes and 11 seconds.
  • Finished on the second try in 12 minutes and 10 seconds.

Things I learned this week:

  • Command + Alt + L is to refactor the code. (Make sure optimize imports is checked so it can be taken care of too.)
  • Command + Alt + Shift + I, type CheckStyle. Click Enter.
  • Click on File Inspector to select the file to move. Press F6 to move the file into a package.

Lingering questions

  • How does not having compiled pages affect SEO?
  • How does security work in this framework?
  • How do we sanitize our input?
  • How do we add e-commerce to a Play application?
  • Are there special requirements to look for when finding a hosting service for a play application?

Reflections on Twitter Bootstrap 3.0

twitterBootstrapAsk anyone who’s been working with HTML and CSS since the late nineties about vertically aligning content with CSS. And they’ll tell you it has always been quite a challenge on one browser. Getting consistent results on many different browsers was nearly impossible. That’s why I was so excited to try out Twitter Bootstrap.

This framework is a god send.

Having to have the ability to center-align things is fantastic. The ability to programmatically create buttons is also fantastic. I used to spend hours and hours tracking down an implementation that I liked. Then I would have to research it and find out how it was made by either looking at the code or by finding a tutorial online. Now I can just import the framework and use the CSS classes right out of the box to create a three columned layout that automatically scales to different screen resolutions.

I’m also happy to start adopting this framework because it is open source. There is no possibility of it going out of date as browsers change over time. There is a huge community of developers working on updating Twitter Bootstrap.

I like that I don’t have to worry about browser specific implementations. Twitter Bootstrap is really easy to use. And I’m going to start using it professionally with my installation of WordPress. I used it to easily mock up a quick survey intro page for work. I am looking forward to using this technology to create a carousel that shows not only pictures but videos too.

Summary of WOD experiences

Bootstrap browser history – This exercise was my first experience using Bootstrap. We created a simple website on the history of surfing. A simple website with four floating divs that held the images and names of four famous surfers. Then we applied Bootstrap and suddenly all the old CSS was not necessary. It still pays to know CSS, but with Bootstrap setting up responsive columns is ridiculously easy.

  • I completed this WOD in 25 minutes and 56 seconds.

Responsive Kamanu – During this exercise I recreated the Kamanu Composites website with Bootstrap. The navigation was easy to update with Bootstrap. And I was also able to style the site with an easy starter design from Bootswatch. I laid out the basic elements of the site I and it looked like something from 1999. Then I added Bootstrap and Bootswatch and the navigation came to life.

  • I completed this WOD in 40 minutes and 22 seconds.

Responsive Castle High School – I updated the Castle High School website to take advantage of the responsive design that comes with Bootstrap. This was the first time I’ve seen a class applied to a div to make it hide itself when the page is resized. Now that I have finished these three experiences with Bootstrap that is simply no going back. Bootstrap gives me confidence to build a site and not worry about how it looks on specific browsers at specific sizes. I can code up a site and be content that it will look beautiful and consistent on any device running any browser.

  • I completed this WOD in 33 minutes and 55 seconds.

Most helpful tool for debugging CSS

The most helpful tool in finding out why certain CSS rules were not being applied was Firebug for Firefox. I got stuck for a good 10 minutes trying to update the color of the navigation bar in CSS. Once I inspected the navigation element with Firebug I was able to determine that the color was being set but the gradiated image was being applied over the background color. Once I removed the gradient the background color shone through.

Reflections on UI Design Basics

Impossible-TeapotEveryone is a designer these days. I remember back in the 90’s when animated gifs of flames and fireworks were the real way to show that you were “in the know” when it came to webdesign.

I was a self taught/professed web designer back in the 90’s. I had grand ideas of double majoring in graphic design and computer science. My friends in the computer science department warned me against taking too many graphic design courses. And my friends in graphic design cheered me on. Either way I knew I would be indispensable if I could speak both languages: Computers and Design.

Computers require deep specialization. There’s a saying that blares in the back of my head. It yells in an irritatingly sing-song loop, “Jack of all trades. Master of none.”

10 years later and I’m happy that I chose to specialize in computers. But I don’t regret my time learning graphic design. I feel so much richer for knowing 2 disciplines versus a single one. Now a new song loops in my head, “Don’t put all your eggs in one basket.” Sure I could be further along with computers if I focused on one discipline but I wouldn’t have the liberal arts education that allows me to see things both from the visual point of view and the purely mechanical point of view. I wear 2 hats. I have 2 perspectives.

Check out my post on Programming for Visual Designers.

Computers require us to specialize. Technology keeps changing and requiring more and more of us. Not only do we have to be able to code, we need to be aware of how to present our ideas in pleasing designs. As technology advances our aesthetics are almost always called into question. As the medium changes, the visual layout requires that we change with it.

What I don’t understand is how all of these changes in design affect usability. I’ll be honest, I am tired of learning new things all of the time. I wish some things would just stay the same. Stasis in Technology? Never! I learned that at an early age. If you want to be in this racket, you need to be willing to constantly change.

Empty your mind, be formless, shapeless — like water. Now you put water in a cup, it becomes the cup; You put water into a bottle it becomes the bottle; You put it in a teapot it becomes the teapot. Now water can flow or it can crash. Be water, my friend. – Bruce Lee

I get it Bruce. But I’m tired. I miss the days of links underlined in blue. My images don’t need to parallax scroll when I read a blog post. I don’t care about the extra niceties. Give me plain HTML with no fancy in-line images and I’m very happy. Do aesthetics have to change with the times? I know technology makes old tech obsolete. But it’s sad to think that new tech also makes old aesthetics obsolete.

End of rant.

This week I worked on 3 WODs

The first WOD required me to create a simple History of Modern Browsers HTML page. I got the content from Wikipedia and laid out the page easy enough. I added some images and created some links to present options to learn more about the creators of each browser. When I had to create a table of contents for the page I got caught up on named anchors and had to look them up online.

  • Time taken on first try: 14 min 50 sec
  • Time taken on second try: 7 min 30 sec

The second WOD required me to update my History of Modern Browsers HTML page to link to a CSS page to make my boring HTML page look better with some Web 2.0 style. I do love the ability to request fonts from Google. No need to purchase fonts. No need to download a local copy to my server. I also updated the body margins and colors to personalize the page.

  • Time taken on first try: 13 min 51 sec
  • Time taken on second try: 10 min 33 sec

The third and final WOD I completed this week was the easiest. I updated my History of Modern Browsers CSS styles to format the contents into a centered page with a three column layout. This was accomplished easy enough with the same float: left tags I used to display the images inline with the paragraph text.

  • Time taken on first try: 5 min 6 sec

Reflections on Completed WODs

The first WOD was the most difficult to complete in time. What I’m learning through the process of coding in a “dumb” IDE is that I rely on code completion a lot. When I don’t have code completion to link to a relative style sheet all progress stops. I have to google “<link rel=” and it takes up serious seconds. Also, linking to fonts hosted on the Google servers is not second nature.

The second WOD presented some problems for me. Without the assistance of Dreamweaver, my web-coding IDE of choice, I had to waste precious time googling how to link to fonts on Google’s servers.

The third WOD was the easiest for me. I completed it in a little over 5 minutes. Once I had warmed up with the previous 2 WODs doing the few updates required to center the content in a div and create a three column layout was easy. I’ve been working with CSS for a little over 10 years and I feel very confident in floating a few. I should study more about relative positioning in CSS.

Reflections on Repeated WODs

Most of the problems I encountered in finishing these WODs this week was that I don’t have a good handle on git branching without using IntelliJ or the GitHub application. It frustrates me to no end when I am trying to push a branch to my repo only to see the option to push it to master. I did learn that I could type in the name of the branch that I wanted to push the updates to.

After I finished my first attempt on the second WOD I reverted my changes to the master. I expected it to reload in IntelliJ but I still had my style.css file. In order to finish the WOD in a reasonable amount of time, I went in and copied the index.html file and ended up deleting the old repo and creating a new one. I pasted the index.html file in again pulled a local copy from the repo.

This method of copying files from the local repo and recreating the repo on GitHub works for these small projects. But I can see that as the projects get larger and larger I am hurting myself by not fully exploring the reasons why IntelliJ and GitHub seem hellbent on frustrating me with errors.

I made the following notes during my repeated attempts at the first WOD:

  • Had to search for named anchors.
  • Setting up a project in IntelliJ was different because it’s not a java file!
  • It’s like the tools IntelliJ and Github but they are not fucking working well together.

I made notes during my repeated attempts at the second WOD:

  • Gotta remember this bit of code: <LINK REL=StyleSheet HREF=”style.css” TYPE=”text/css” MEDIA=screen>
  • How do I do all headers instead of just h1 or h2?
  • How do I set images to be inline with text?
  • Switching back to the master branch gives me to the same style.css file. This should be gone when I switch back to the master branch.
  • Committing my push always goes to my master. I want to find out how to do it to the branch. That is where it needs to go.

And I made the following notes when I repeated the third WOD:

  • The instructions for this WOD do not specify all the necessary padding that is involved in getting these things to show up correctly. There are considerations for padding that are not addressed in the write up.
  • How do you center a div in the middle of the screen?
  • How about centering the thing vertically?
  • Also the links in the example are stylized with the rest of the text on the screen.

Suggested Reading