Skip to content

Instantly share code, notes, and snippets.

View wlffann's full-sized avatar

Annie Wolff wlffann

  • Denver, CO
View GitHub Profile
@wlffann
wlffann / oss_blog.md
Last active April 15, 2017 17:13
blog post about open source contributions with Code for Denver

When I first ventured into the world of open source contributions, I was immediately overwhelmed. Until that point, I had not fully considered the all of the work that went into creating and maintaining the tools that I used in my projects every day.

All of the github issues, the comments, the waffle boards, and the first-timer tags made my head spin. I dug through repos looking for the just the right sized project with just the right amount of activity and just the right code base. Turns out, it didn’t exist.

I found myself missing the human aspect of development after a few hours of scanning projects. I wanted to talk to someone about why what they were building was important, what needed to be fixed on it and maybe even learn about who they were in the process. I returned to Google with a new search in mind: local open source. The first search result returned the Meetup page for Code for Denver and it just so happened that their next project night was the next day. I resolved to go and try to contribut

I've been trying to get a some different types of experience in my multiple interview prep sessions. For technical interview prep, I reached out to my mentor to pair on an example algorithm challenge. I asked him to pair with me as he would with someone he's interviewing and we worked through a challenge over screen hero. I was embarrassed at one point because he showed me a ruby concept that I had never learned before! He was very helpful and explained the concept to me and I've been trying to use in in new places. I've also participated in a few Turing-organized algorithm practice sessions and they have been very informative.

For non-technical interview prep, cold outreach meetings have been extrememly helpful. They are not expected to be a formal interview, but many of the same questions come up, and I've gotten more and more confident with those answers. I feel great about my personal elevator speech by now!

@wlffann
wlffann / open-source-proposal.md
Last active March 22, 2017 15:47
A proposal for potential open source contributions.

Open Source Proposals

Original Assignment This is a collection of possible open source contributions that could fulfill Turing School's graduation requirements.

OpenSUSE's osem project

Repo
Contributing.md
Issues

  • Why: This seems to be a pretty junior-friendly project. They have many issues that are labeled for first-time contributors and very clear guidelines for contiubting.
@wlffann
wlffann / mod-4-action-plan.md
Last active February 27, 2017 15:51
Mod 4 Action Plan

Annie Wolff: Module 4 Action Plan

This is your deliverable from the Job Search Strategies I session

Module 4 Goals

I want to have recieved a job offer by the end of Module 4. I would like for this job offer to one I want to accept.

Strategy To Achieve Goals:

In order to achieve this goal, I will need to spend at least 3 hours a week (and up to 5 hours a week if possible) searching for opportunities and actively applying to them and reaching out to people at those companies.

Coding (both including your module 4 curriculum and anything outside of it):

@wlffann
wlffann / interview_reflection.md
Created February 21, 2017 03:34
Reflection on Interviewing with Ingrid

Job interviews begin the moment that you walk in the door and end when you send a thank you email afterwards. At every moment, it's important to be putting your best self forward in order to show that you are a great candidate for the job and that you are interested in the company. Perparation can help lower your stress level. Practicing questions outloud beforehand can help you focus on what's important in what you want to say. It can also be helpful to write your questions down beforehand so that you are ready with smart and relevant inquiries.

Technical interviews can be intimidating but are really to show how you think and collaborate. If you can feel confident talking through your thought process and expressing the way you're approaching the problem, you will be ok.

You're not only selling yourself, though. It is important that you ask questions of the interviewer as well. This is your best oppurtunity to gauge whether you think that the company would be a good fit for you and your career goals.

RehearsalTracker

Pitch

I want to build a production management tool that brings the benefits of agile practice to the world of the theatrical design team.

Problem

Currently, production teams use a combination of email, dropbox, pinterest and hard paperwork to track rehearsal reports, designs, measurements and blocking. This makes finding information and notes an arduous task and clear communication nearly impossible. Technical departments, such as props or costumes, can easily lose track of notes or required items that hold up the process.

@wlffann
wlffann / css_transforms_lightning_talk.md
Last active December 12, 2016 14:18
CSS Transforms Lightning Talk

Getting Started with CSS Transitions and Transformations

  • Two properites to know: transition and transform
  • With these two properties, any selector or pseudo-selector can be made interactive for the user and way more awesome.

Transform Options

  • transform is used to specify the changes that will be made to the element itself.
  • transform-origin can be used to specify the position of the transformation. Default is the center of the element.
  • Some fun transform options:
    • scale(): effects the size of the element
    • skewX() & skewY(): tilts the element to the left or right

A.) While our group was very successful, I feel that our GitHub workflow could have been much better. We paired on most of our project, so documenting was not our priority. It was rare for us to have multiple branches with different features in play, so sometimes we wouldn't even commit at the end of a session. This meant that if there was code on a partner's computer but not on git, the other partner would not have access to it over the night. This issue also prevented us from keeping true record of our process. Commits would have messages that were long and undescriptive of the changes that we made. Moving forward, I would place a heavier emphasis on commits, branch management and version control.

B.) My role was to lead the broader concepts and design of the project. I really enjoyed making the connections between the objects and using these links to extract information. I did much of the typing for the project, which means that I also did most of the typos.

C.) My partner was strongest in the technical

@wlffann
wlffann / Molecules_and_Modernism.md
Last active October 24, 2016 20:16
outline for lightning talk on impressionism and technology