search

TIY-Durham / 2016-SPRING-FEE

Class Repository for Front End Engineering in Spring 2016 at The Iron Yard in Durham, NC
12 stars 1 forks source link

00 -- Travis Johnson #18

Open travis-johnson opened 8 years ago

travis-johnson commented 8 years ago

# Activities:

travis-johnson commented 8 years ago

1. What is the best way to ask a question? Be as clear and specific as possible. Break down a question into multiple parts if needed. Utilizing the convenience of Slack or email will help these questions get answered quickly.

2. How can you explicitly schedule time with your instructor to review a problem?
Requesting a meeting via Calendly.

3. Are there any other times that we're available? Meetings can be arranged outside of office hours but must be done so in a timely manner.

4. What are the three possible grades applied to every assignment? What do they mean Red, Orange and Green. Red is incomplete, Orange is "not yet" and Green is satisfactory.

5. What is the link to your GitHub profile? Your profile image? GitHub Profile GitHub Profile Image

6. In what week do we plan to review material? Just like the number of this question, the sixth week!

7. At what time does class begin? Is attendance mandatory? Class begins every morning at 9am. Attendance is mandatory.

8. After what amount of time are you counted late? I did not see an exact time. However, if you are late to a lecture and haven't informed the instructor prior.

9. When are you counted absent? Does that matter? When you acquire two tardies within a week, this is considered an absence.

10. What is the most common kind of mistake in programming? Typographic errors in your code such as misspelled words, missing punctuation or misuse of indentation.

11. What are some strategies you can use to work through a difficult problem? Work in short intervals on an assignment, such as 25 minutes on with a five minute break in between. If you're stuck on a problem, step away from it for a while and collect yourself. Come back to it with a refreshed mind.

12. What exactly is the ⌥ key, anyway? This is the "Option" key. It allows the user to input modifiers to text and other characters.

13. What do you think will be the biggest barrier to your success in this class? Getting back into the classroom mindset. I haven't taken any type of class like this in over ten years. This should be interesting but I'm looking forward to it.

14. How can you identify with the Growth and Fixed Mindsets? In what areas do you feel fixed? Where do you see the most potential for growth? The Growth Mindset is the one I can definitely say I identify with. As far back as I can recall I've always wanted to just know more, about anything. I have a mind full of random, albeit useful, knowledge and during my time working in both IT and retail I've explored almost every role within the company. There's always that drive in me to learn more about something when I have the smallest spark of curiosity. After doing some thinking, I can't really think of any part of me that would maintain a fixed mindset. I've had many challenges in life and having that kind of mindset would have lead me to nowhere so, I refuse to practice it. As for potential growth, I see this program as really showing me the true discipline my mind and life needs. This intense course is set to challenge me in a lot of ways but it's the gaining of knowledge and life lessons I can't wait to encounter.

15. Do you consider yourself a top-down or bottom-up thinker and why? I would consider myself a top down thinker with a touch of bottom-up. When it comes to piecing together a project, mapping out a plan seems so much more logical than to just go with the flow, so to say. If I am working either with a team or solo, I want to have a complete and clear understanding of the goal with the project. Once this is established it allows for the project to be pieced together easily and allow a bit of "bottom-down" improvisation along the way.

16. What do you think about your "learning style" and the debate about their validity? Which would you categorize yourself as and why? I believe finding a common ground of learning styles would benefit a lot of educators and students, saving them time and efficiently speeding up the learning process. If I had to choose between the two, I would say that I'm a visual learner. Growing up in the age of YouTube and other online media, the ability to learn something has become so easy. Having a major creative mindset has also enabled me to learn more efficiently by visualizing it instead of just having it explained.

travis-johnson commented 8 years ago

screen shot 2016-03-03 at 11 32 05 am

travis-johnson commented 8 years ago

screen shot 2016-03-03 at 11 34 21 am

travis-johnson commented 8 years ago

screen shot 2016-03-03 at 11 34 53 am

travis-johnson commented 8 years ago

screen shot 2016-03-03 at 11 35 18 am

travis-johnson commented 8 years ago

screen shot 2016-03-03 at 11 38 40 am

travis-johnson commented 8 years ago

@kellymurray I have attempted to install Homebrew. The "which doctor" command returned the correct result of "/usr/local/bin/brew" . However, when running "brew doctor" I have noticed the following errors. 


Warning: gettext files detected at a system prefix
These files can cause compilation and link failures, especially if they
are compiled with improper architectures. Consider removing these files:
    /usr/local/lib/libintl.dylib
    /usr/local/lib/libintl.dylib

Warning: You have leftover files from an older version of Xcode.
You should delete them using:
  /Developer/Library/uninstall-developer-folder

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
    /usr/local/lib/libatk-1.0.0.2209.1.dylib
    /usr/local/lib/libgdk-x11-2.0.0.1200.0.dylib
    /usr/local/lib/libgdk_pixbuf-2.0.0.1200.0.dylib
    /usr/local/lib/libgdk_pixbuf_xlib-2.0.0.1200.0.dylib
    /usr/local/lib/libgio-2.0.0.0.0.dylib
    /usr/local/lib/libGLEW.1.5.4.dylib
    /usr/local/lib/libglib-2.0.0.1600.0.dylib
    /usr/local/lib/libgmodule-2.0.0.1600.0.dylib
    /usr/local/lib/libgobject-2.0.0.1600.0.dylib
    /usr/local/lib/libgthread-2.0.0.1600.0.dylib
    /usr/local/lib/libgtk-x11-2.0.0.1200.0.dylib
    /usr/local/lib/libintl.8.0.2.dylib
    /usr/local/lib/libjpeg.62.dylib
    /usr/local/lib/libpango-1.0.0.2100.0.dylib
    /usr/local/lib/libpangocairo-1.0.0.2100.0.dylib
    /usr/local/lib/libpangoft2-1.0.0.2100.0.dylib
    /usr/local/lib/libpangox-1.0.0.2100.0.dylib
    /usr/local/lib/libpangoxft-1.0.0.2100.0.dylib
    /usr/local/lib/libportaudio.2.0.0.dylib
    /usr/local/lib/libSDL-1.2.0.dylib
    /usr/local/lib/libz.1.2.5.dylib

Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
    /usr/local/lib/libatk-1.0.la
    /usr/local/lib/libgdk-x11-2.0.la
    /usr/local/lib/libgdk_pixbuf-2.0.la
    /usr/local/lib/libgdk_pixbuf_xlib-2.0.la
    /usr/local/lib/libgio-2.0.la
    /usr/local/lib/libglib-2.0.la
    /usr/local/lib/libgmodule-2.0.la
    /usr/local/lib/libgobject-2.0.la
    /usr/local/lib/libgthread-2.0.la
    /usr/local/lib/libgtk-x11-2.0.la
    /usr/local/lib/libintl.la
    /usr/local/lib/libjpeg.la
    /usr/local/lib/libpango-1.0.la
    /usr/local/lib/libpangocairo-1.0.la
    /usr/local/lib/libpangoft2-1.0.la
    /usr/local/lib/libpangox-1.0.la
    /usr/local/lib/libpangoxft-1.0.la
    /usr/local/lib/libportaudio.la

Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
    /usr/local/lib/libGLEW.a
    /usr/local/lib/libintl.a
    /usr/local/lib/libjpeg.a
    /usr/local/lib/libportaudio.a
    /usr/local/lib/libz.a
kellymurray commented 8 years ago

Hi @travis-johnson! No worries -- we'll get this set up when you get here if it's still throwing errors. Thanks for reaching out!