Skip to content

Instantly share code, notes, and snippets.

@drod1000

drod1000/reflection.md

Forked from case-eee/reflection.md
Last active March 13, 2017 21:26
Show Gist options
  • Save drod1000/f0c2ba05dae44e3450641baaa8bb7cc7 to your computer and use it in GitHub Desktop.
Save drod1000/f0c2ba05dae44e3450641baaa8bb7cc7 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 came to Turing to pursue a career that's both challenging and rewarding. I liked the idea of being able to create something myself to improve my own life, that of those around me, and my community.

  • Where do you see yourself after Turing?

It's tough to say but I see myself at a company that serves a real need for the average person. I also see myself having the time to work on side projects that interest me and leading the life I've always wanted.

  • From concepts taught in class or your personal learning, what technical concepts do you enjoy exploring most?

Project Management, Optimization, Design Patterns

  • What technical concepts do you enjoy exploring least?

I know that security is extremely important but I just don't find any joy in learning/implementing it.

  • What technical challenges are the most fun for you to solve?

I really enjoy visualizing how all of the pieces of the application are going to fit together and determining the most efficient way to get all of the tasks accomplished. I've always been the type of person that likes to plan and think logically so I really enjoy weighting the effects a change will have on the rest of the application or finding the best algorithm to tackle a problem.

@neight-allen
Copy link

Thanks for the responses. I want us both to keep these things in mind throughout the module, but here's some initial thoughts:

  • You can definitely find rewarding products to work on. Let me know if you want any tips on reaching out to companies you believe in.
  • You don't need to be an expert in security, but if you don't understand what the security risks are, follow best practices carefully. Small details can open up your whole system.
  • Breaking down the problem is half the battle, if not more. That skill will help you grow quickly as a developer.

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