Skip to content
View kvenn's full-sized avatar

Highlights

  • Pro

Block or report kvenn

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
kvenn/README.md

Hi there πŸ‘‹

  • πŸ”­ Working on: a new social app startup
  • 🌱 Attemping to master: Flutter, rock climbing, and Spikeball. If you have resources on any of those, send them my way!
  • πŸ‘― Hiring: people who love hacking on stuff
  • πŸ’¬ Ask me about:
    • mobile development (native iOS, Android, Flutter)
    • full-stack architecture (FE+BE)
    • scaling a team
    • how to get started on a side project
  • πŸ“« How to reach me:
    • email
  • πŸ˜„ Pronouns: he/him
  • πŸ“Œ Based in: NYC
  • ⚑ Fun fact: My first mobile app in the store was Cat Facts in 2014

StackOverflow

Link to Account

SO's Flair

Public Github Stats

Pinned Loading

  1. vimeo/vimeo-networking-java vimeo/vimeo-networking-java Public

    The Vimeo Java (Android) SDK

    Kotlin 121 49

  2. Velocity Tracking and Estimation.md Velocity Tracking and Estimation.md
    1
    ## Task Estimation 
    2
    
                  
    3
    Each task requires an estimated point value based on time, complexity, and unknowns. Ensuring tickets are broken down into sensible, actionable chunks can reduce unknowns and allow the team to point a ticket based on the task’s time and complexity. A good scale to use for point values is the fibonacci sequence (1, 2, 3, 5, 8, 13) [because it reflects that uncertainty on how to execute a task increases with task size](http://www.scrum-institute.org/Effort_Estimations_Planning_Poker.php).
    4
    
                  
    5
    A team should point each ticket as if any member were to take it on. This increases team flexibility and improves the quality of task estimation. Team members should therefore estimate each task as a group, and converge on a point value on which every member agrees. One method is planning poker, in which each team member reveals their individual point estimation of a task at the same time before the team collectively decides on the appropriate point value. 
  3. vimeo/Blueprint vimeo/Blueprint Public

    aka How We Collaborate

    42 8

  4. rd-watchapp rd-watchapp Public

    A Pebble watch app to notify you at random intervals to be more mindful

    C

  5. selfieaday selfieaday Public

    CSS