Skip to content

Instantly share code, notes, and snippets.

@Sh1pley

Sh1pley/reflection.md

Forked from case-eee/reflection.md
Last active March 13, 2017 20:41
Show Gist options
  • Save Sh1pley/f558f79725b46da02b910d0bf11d5b57 to your computer and use it in GitHub Desktop.
Save Sh1pley/f558f79725b46da02b910d0bf11d5b57 to your computer and use it in GitHub Desktop.
Download ZIP
M4 Reflection
Raw
reflection.md

M4 Reflection

Fork this gist and answer these questions to reflect on your learning experiences.

  • What brought you to Turing?
    • I wanted a change into a new field. I spent way too much time fixing old things and want to apply my passion for learning into creating something new.
  • Where do you see yourself after Turing?
    • I would like to be in a stable position that allows creative freedom in solving problems or utilizing technology in new ways.
  • From concepts taught in class or your personal learning, what technical concepts do you enjoy exploring most?
    • I like the logic in programming, and enjoy SRP that well designed code offers. I want to learn more about functional programming and building functions, classes that offer expected results.
  • What technical concepts do you enjoy exploring least?
    • I am not so good with styling, so I enjoy that least (only because of my current skill). I would love to learn more as it seems like a fun thing
  • What technical challenges are the most fun for you to solve?
    • I enjoyed the mod3 final. It offered an expectation of a thing and allowed us to build towards achieving it. I also enjoy diving into logical algorithmic problems as well.
@neight-allen
Copy link

Thanks for the responses. It will help me throughout the module, but here's some initial thoughts:

  • Looking forward to creative freedom on the job, smaller teams tend to have less organization, and you can have more control over the functionality you're building, but a small team usually comes with some other headaches, mostly inconsistency. Larger teams will give you really specific functionality, but you'll still have some control over how to implement.
  • Remind me that you're goal is well written code over lots of functionality when we get to the capstone. If the rest of your team agrees, we can prioritize code quality over code delivery.
  • There aren't a lot of styling classes this module, but we want to give you guys the opportunity to audit classes in other modules and programs as we get later into the module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment