👋 Hi, I'm Joseph John Karl Workman (@JJKW1984) born Oct 1984.

I'm passionate about:

• 💻 Coding and software development
• 🎵 Music
• 🤝 Addiction and recovery
• 📖 Personal stories and human connections

Currently learning:

• 🌱 Azure DevOps
• ⚡ PowerShell
• #️⃣ C#
• 📋 Agile/SCRUM/SCRUMBan and general work management/flow philosophies
• The science behind of addiction and pathways to recovery

Looking to collaborate on:

• 💞️ Addiction Research
• Technical project regarding development or devops

• 📫 Email: joseph.workman@gmail.com
• 🐦 Twitter: @JosephJohnKarl

• Physical space: I appreciate being in person with people for deep conversation and ideation. In shared workspaces I may seem to disengage if if there is a lot of social activity happening and I am feeling overwhelmed or have to attend to project work. It isn't personal.
• Tools: Use Microsoft tools at work, google and apple technology at home
• Structure: I thrive when there's a clear understanding of project goals and requirements

• Typical hours: EST
• Response time: 4 hour by text,24 hours by phone, a day by two with email

For quick questions or updates:

• Text for same day
• Phone for next day
• Email for someday soon

For collaboration or complex discussions:

• Video calls
• Happy to meet with just about anyone when we have an agreed upon agenda

What helps me:

• Clear, direct communication
• Explicit expectations
• Context about the "why" behind requests
• Advance notice for meetings

• Be direct: I appreciate honest, constructive feedback
• Provide context: Help me understand the situation and impact
• Focus on solutions: I'm always looking to improve and grow
• Timing: Real-time or near-time feedback helps me course-correct quickly
• Format: One-on-one conversations or video calls work best for substantial feedback

I view feedback as a learning opportunity and won't get defensive. I want to understand how I can improve and be more effective.

• Clarity: Understanding the "why" behind what we're building helps me do my best work
• Context: Background information and the bigger picture
• Transparency: Open communication about expectations, priorities, and changes
• Collaboration: Opportunities to work with others and share ideas
• Purpose: Connecting the work to meaningful outcomes

• Ambiguity without context: When I am part of a team I find it difficult to contribute when I don't understand the purpose of or have an agreed upon vision for a project.
• Meetings without clear outcomes: I value everyone's time. If we are meeting let us have a clear objectives.
• Doing Less: I love ideating, kicking off projects, and answering calls for help... I am also learning to use "No" instead of "Yes" as my default.

• Problem-solving: Diving into challenging technical problems and finding elegant solutions
• Learning: Exploring new technologies, patterns, and approaches
• Mentoring and teaching: Sharing knowledge and helping others grow
• Building tools: Creating utilities and extensions that make developers' lives easier
• Community: Connecting with others who share similar passions and interests
• Recovery work: Supporting others on their journey and sharing experiences

• I bring my whole self to work and value authentic connections
• My interest in recovery and personal stories shapes how I approach teamwork - with compassion and without judgment
• I'm committed to continuous improvement in both my technical and soft skills
• I believe in the power of empathy and understanding in building great teams

• I'm (almost) always happy to discuss technology, music, recovery, personal developer with (almost) anyone via a virtual coffee.

This user manual is a living document. I'm always learning and evolving, so feel free to provide feedback on how we can work better together!