added a div to the user show - their profile essentially - page.  in this div rendered the microposts using the render @microposts.  at this point not sure how this was auto associated with the user.  Added in test framework to see that the profile page displays the content of the posts associated with that user and also that it displays the count of posts
had trouble with the tests for microposts, could not figure out why it wouldn't work, hoping that it is a problem with testing framework and not code, so going forward with code.  If code breaks, then I'll know..
so I found the bug.  lol.  a whole 1.5 hours wasted because i misspelled micropost - micrpost.  stupid p looks like an op.... wow
added routes for microposts.  Only using the create and destroy options.  to create you post at /microposts, to delete you destroy at /microposts/[id of micropost]
removed the signed in user methed from users controller to sessionshelper so that it is available to all the controllers.  then called this in the micropost controller, which i created, to filter and make sure only signed in users can create and destroy posts.  then created a micropost pages spec which crets a user, signs them in, and then tries to submit a micropost at the root path with invalid and valid information.  with invalid information it should then display an error message.  with valid information, the micropost count should change by 1.
implemented teh create method to get the current user and build a micropost passing in the params[:micropost] to the .build method on the current_user.microposts object - it assigns this to a variable, and if it can save it, it flashe's success and redirects to teh root_url.  otehrwise, it goes to static_pages/home.
added an if else clause to the home page using <% if signed_in? %> to see if they were signed in.  If they are signed in, then render pages from the shared directory, which I'm assuming we'll move shortly from the profile pages in a cool little refactoring.  Otherwise, display the home page as normal
created a _user_info.html.erb partial that grabs the gravatar for the current user, their name, a link to their profile, and a pluralize that I'm not quite sure what it will do
added the form to submit microposts, renders shared error_messages partial - if it's blank for instsance - also has placeholder text
defined the @micropost variable for the home page of the staticpagescontroller and checked if they were signed in adn if so then @ microposts becomes the current_user.microposts.build function.  This can be seen in the _micropost_form partial where form_for(@micropost) is called.  I'm not sure how this works in its entirety.  Also updated teh _error_messages partial so that it would accept any object and if that object has errors display them accordingly.  to use this error messages partial we have to pass the object parameter object: f.object to the render of the partial.  also made the spec to test the micropost_pages.
edited the users/edit.html.erb and users/new.html.erb files so that they used teh new more general error partial.  this meant i had to pass the object to the render called with object: f.object where f was the variabel in the form_for
created a test to check if a user has a feed method and then to see if this feed included the users posts
corrected some spelling errors in the test for the feed method on the user model
adding a feed method to teh users model that sets teh feed to the microposts where the user_id is equal to the id of the current signed in user
edited the static pages test suite so taht on the home page if a user is signed in and has microposts each of his posts should be displayed.
use the signed_in? method of teh sessions helper in the static pages controller to build the microposts and feed_items - i think these are both arrays, but not sure...
on a failed attempt had to add an empty @feed_items array to the microposts controller to get it to pass.  Created the partial _feed.html.erb in the shared directory to be rendered by the home page.  It in turn rendered another partial _feed_item.html.erb by passing a collection, the feed items array, which was added to teh static pages controller and created from teh current user using it's feed method, which was defined in the model, which is simply the array of microposts with the same id as the user id.  Then added the partials to the home page
added delete links to the microposts by adding in link_to delete tags in the micropost and feed_item partials.  both of these methods are similiar.  Not sure how they are passed around yet.
added a test for micropost destruction.  before it creates a micropost using a user and the factorygirl.create method.  then it { visit root_path } and expects to {click_link 'delete'}.to change(Micropost, :count).by(-1)
updated the micropost controller with a before_filter that called the correct_user private function to check if the micropost was owned by the current user before a destroy action was sent.  also corrected a bug in the microposts html partial.