Skip to content
View kyle-bowden's full-sized avatar

Highlights

  • Pro

Block or report kyle-bowden

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
kyle-bowden/README.md

User Manual

Introduction

Introduction
  • Name: Kyle Bowden
  • Role: Consultant - Software Engineering
  • Contact Information: [email protected]

Working Hours & Availability

Introduction
  • Typical Working Hours: 9 AM - 5 PM (GMT) but my most productive hours are between 10 p.m and 1 p.m.
  • Best Times to Reach Me: Mornings are best; usually responsive to emails within 24 hours.
  • Preferred Communication Channels: Slack, Telegram, Signal, WhatsApp, and Email although I'm much slower to respond to emails.
  • Out-of-Office Protocol: I set up an auto-reply and may not be immediately available.
  • Holidays: I value my free time as it allows me to spend quality moments with family and friends, so I'm completely unreachable during those periods.

How I Work Best

Introduction
  • My Ideal Work Environment: For deep focus, I prefer being at home in my own office space and set up, as I find offices distracting for concentrated work. However, for collaborative tasks like brainstorming, I enjoy meeting up with my team in an office setting.
  • Best Way to Collaborate with Me: Clear agendas for meetings, along with a mix of engaging or spontaneous moments to keep things lively and avoid monotony.
  • Focus Hours: I prefer not to be interrupted, as it disrupts my ability to concentrate. I will put a slack status on to let you know 😉

Communication Style

Introduction
  • Response Time: I usually respond to messages within 30 minutes during work hours.
  • Preferred Communication Tone: Direct and to the point, but open to friendly chit-chat.
  • Feedback Preferences: I appreciate direct and constructive feedback; best given in private.
  • Meeting Style: Prefer scheduled meetings with a clear agenda.

Strengths & Areas of Expertise

Introduction
  • Key Strengths: Problem-solving, hands-on approach, and a strong drive to get things done efficiently.
  • Technical Skills: Scala, JavaScript, ReactJS, and a wide range of other programming languages/frameworks, as I consider myself a polyglot in coding.
  • Soft Skills: Communication, teamwork, adaptability
  • What I Can Help With: Developing infrastructure solutions, optimizing CI/CD pipelines, creating microservice APIs, building frontend services, and tackling any other challenges you throw my way.

Things I Need From My Team

Introduction
  • Support: Clear requirements, access to necessary tools and resources
  • Communication: Honest and timely feedback, open communication
  • Collaboration: I see pairing as a valuable tool; it may not be needed for every task, but it’s highly effective in many cases. I also enjoy connecting with team members through occasional virtual hangouts or in-person meetups when possible.

How I Handle Stress & Conflict

Introduction
  • How I Manage Stress: I take short breaks, listen to music, go for a walk
  • Approach to Conflict Resolution: Prefer open and honest discussions; I value finding common ground

Personal Interests & Fun Facts

Introduction
  • Hobbies & Interests: Game development, drawing, sculpting, trying out new tech.
  • Fun Fact: I’m currently working on developing my own indie game!
  • Preferred Break Activity: Taking a quick walk, watching a tech or current events video on YouTube, or catching up on the latest tech news.

Things That Energize Me

Introduction
  • Motivators: Learning new things, solving complex problems, building something from scratch.
  • Inspirations: Seeing the positive impact of my work, and successful collaboration.

How to Provide Feedback to Me

Introduction
  • Best Way to Give Feedback: Direct, specific, and with clear examples
  • Feedback I Appreciate: Feedback that helps me improve my skills or approach
  • Feedback I Don’t Respond Well To: Vague criticism without actionable points

The End

Introduction

Popular repositories Loading

  1. mediafinder mediafinder Public

    Java

  2. crypto-watch crypto-watch Public

    A crypto dashboard for quick glancing at your cryptos assets

    JavaScript

  3. clik-less clik-less Public

    An app which helps in opening certain file types when they are put into certain watched folders that the user can specify.

    Java

  4. soft-drinks-industry-levy-frontend soft-drinks-industry-levy-frontend Public

    Forked from hmrc/soft-drinks-industry-levy-frontend

    As partial forms have been deprecated in contact-frontend this fork is to illustrate the change needed to use the static report a technical problem page

    Scala

  5. fh-registration-frontend fh-registration-frontend Public

    Forked from hmrc/fh-registration-frontend

    As partial forms have been deprecated in contact-frontend this fork is to illustrate the change needed to use the static report a technical problem page

    Scala

  6. cap-lock-popup cap-lock-popup Public

    A Windows application that provides an on-screen popup to display the current state of the Caps Lock key.

    Java