Skip to content

Instantly share code, notes, and snippets.

@noetic97
noetic97 / Transhumanism_outline.md
Created September 20, 2017 19:17 — forked from EvanSays/Transhumanism_outline.md
transhumanism outline

Gear Up - Transhumanism Outline

Intro (10 mins) (Joe)

1) Quick overview on Transhumanism and what we will be doing today.

2) Article

3) Divide group into spectrums (move around room) Joe plays devils advocate, against. Spectrums  = for, against, unsure

Post-Grad Job Search Action Plan

Some things to consider:

  1. What do you envision for your career?
  • Working my way into a senior dev position in 5+ years and then into a larger PM role in 5-10 years.
  1. What do you want your 2nd and 3rd jobs to look like?
  • Intermediate dev hire. I want to have my feet firmly under me. Nice pay raise!
  1. How do you want to be involved with the Turing community? The greater developer community?
  • I plan on being a fixture in the tech community through writing and speaking at events. I would love to be a mentor or fellow at Turing to continue to give back directly to the community that gave me so much.

Documentation of Practice/Actual Interview Participation

For me, the most valuable practice that I recieved from the interview prep work that I did was defining my process. Understanding that process is going to open more doors that knowledge makes a ton of sense. It's important to be able to ask for clarification and show that you are engaged in the technical part of any interview. As for the culture fit, doing the advance work of cold reaching out to current employees will help immensely in figuring out if you will fit well. Showing that the position is more than just a paycheck is also important, so doing research about the companies that I apply with will be at the forefront of my outreach efforts.

@noetic97
noetic97 / Joe-Heitkamp-job-search-action-plan.md
Last active July 31, 2017 15:57
Job search action plan for Mod 4

Joe Heitkamp Module 4 Action Plan

Module 4 Goals

I plan on having gone to at least 4 interviews and potentially having a job offer by the end of Mod 4.

Strategy To Achieve Goals:

I will be reaching out to employees at companies that seem interesting each week. I will find these employees through linked-in and Meetups.

@noetic97
noetic97 / flower-exercise.md
Last active July 31, 2017 15:00
Flower Exercise

Joe Heitkamp's Flower Exercise

My Favorite People to Work With:

  • Problem solvers
  • Team Players
  • Patient
  • Constructive
  • Enthusiastic
  • Open to change

Who you are?

I'm driven by a need to improve the world around me. My skills of working with diverse groups of people will help me keep an open mind about implementations of tech that can impact the most people. I thrive in environments where there is a challenge, but also support that helps everyone meet the challenges they face. It's incredibly important that the people I work with and for have a passion for the work that we are doing. Ideally I am working in Denver or remotely from Denver where I have family. I would also like to have support for pursuing my own ideas. I want to be in an environment of continued learning when it comes to coding.

Must Haves/ Nice to Haves

Must Haves
  • Live in denver
  • healthcare for me and family
  • 60K+

Write: Reflect on your experience at Turing thus far and write out your story, answering the questions who are you, why are you here, what's next? Think about how others might root for you as a character and what's at stake for you in your career transition. Consider:

  • Your Strengths: what makes you the "hero" of this story?
    • If you took StrengthsFinder, reflect on how developing your strengths at Turing has influenced your story
  • How have you grown at Turing? What obstacles have you overcome?
  • What turning points led you to make this career change?
  • What does your third act look like? How does transitioning to this career bring some closure to this narrative arc?
  • Describe causality -- what made you want to make this career change? How is it grounded in your character?
  • How you can create trust with the listener
  • Creating coherence in your story

Joe Heitkamp - M2 Portfolio

Areas of Emphasis

For module 2, I set out to to build a stronger understanding of javascript fundamentals and find ways to become a more valuable member of the Turing community. I think that I have succeeded in both endeavours. While there is always room for continued improvement, I have been able to help new students navigate through the hardships of Mod 1 while also proving to myself that I am showing consistent improvement in my programming skills.

Rubric Scores

  • A: End-of-Module Assessment: 3
  • B: Individual Work & Projects: 3

Feedback III Reflection

  1. What are you doing well as a pair programmer and collaborator?
  • I am focusing on the needs of my pair partner to make sure they feel comfortable with the rate of progress and have a strong understanding of the code we are writing. On the flipside, I take the time to ask for clarification on the pieces that I don't understand.
  1. How do you use your strengths as a team member?
  • I use empathy to guage the needs of my pair partner. Input is a valuable strength because I generally have a plethora of options to try in any given situation. As a learner, I strive to constantly better understandand examine the code.
  1. How would you like to continue to develop your strengths?
  • I think that I would like to make sure that my strengths are at the forefront of my mind as I move into new projects. It can be easy to get frustrated with not understanding a complex subject, but it becomes easier when I remember that learning and inputare strengths of mine in those moments.
@noetic97
noetic97 / agile-practices-reflection.md
Last active June 5, 2017 19:22
Agile Practices/ Project Management

Agile Practices and Project Management

  1. What project management strategies did you use in your projects this module?
  • In both Game-Time and Weatherly, we used several sprints to focus on features that we wanted to implement with timelines that were shorter than the overall project timeline. Putting working software over fully factored and documented code was essential in moving forward. Responding to change was way more important than following the plan.
  1. What went well?
  • Pivoting when something did not go according to plan. Celebrating small victories over a fully working project kept our moods up.
  1. What would you do differently next time?
  • Better map out the incremental roadmap to be able to constantly take advantage of the positive ipact of small victories.