Email and Outreach for an hour in the morning.
Research companies for an hour in the morning.
Code for three to four hours in the afternoon (10am-12pm, break, 1pm-2pm)
Look to see if any intersting Meet Ups are happening. Go to Meet Up if interested. I will be living in Golden so there will be more opportunities with Boulder closer than it is now.
I talked for an hour on the phone with the founder and lead developer at FluentStream. We discussed Turing, my projects and his company and dev team. There was no technical interview perse, but we talked about the take home assignment he used to give and why he stopped using it. He told me that since they were a bootstrapped start up he wasn't able to offer as much money as other companies, but if I could make it work, the next step would be to come in to meet the dev team. He made me an offer, but unfortunately I wasn't able to accept it.
I reached out to a warm contact in Boston for two reasons. I'm still not 100% positive that I'm staying in Denver after Turing and I wanted at least one more conversation going with a company in Boston (I currently have one more conversation going with another company there). The other reason is I know someone in 1608 applied to Wayfair recently and I wanted to reach out to the person I know and let them know that a person from my program applied.
Outcome: My contact said he would keep an eye out for Graham's application and that it sounded like he'd be a good fit.
####First Half of Mod4 Be talking to one or two companies about job opportunities.
Try to have one mock interview / do one white boarding question a week.
Deliver projects that I am proud of and wouldn't be embarrassed to show a future employer.
#####Strategy To Achieve Goals: Spend the first hour of the morning reading emails and drafting responses to companies I've reached out to.
#Three goals based around accessibility:
I would like to make sure that all elements in my projects are clearly those elements. No buttons or links that look like they could be something else, or are not clearly established, etc.
I would like to write clean and semantic HTML and CSS from the start, rather than doing what I already know and going back and having to refactor later.
I'm big on color choices and design and I would like to put more thought into color for accessibility reasons rather than picking colors just because I like them or they go well together.
side note: I used to help and run accessibility worksthops at Apple. It's insane how many features Apple has built into their products that no one knows about, including people who need it. I was really excited to get involved in the accessibility community at Apple (though I've forgotten most of it now) and am really excited to get involved with accessibility in development.
display all divs as inline block.
wrap div2/3 in its own container.
float div2/3 right.
I grouped div2 and div3 together in their own section. I used inline-block to get the initial format and then floated div1 to the left and the grouped div2 and div3 to the right.
I left div1 alone after giving it the color and size properties. Div2 has a margin of auto and a position of center to get it to the middle of the page. Div3 has a float right to get it to the bottom of the page.