Skip to main content

Let's Connect

Have a tech debt war story? Want to share a technique that worked? Found something that could be improved? I'd love to hear from you.

Email Me

Send me your thoughts, questions, or suggestions

[email protected]

Rotating email for your amusement - all go to the same inbox

Connect on LinkedIn

Let's connect professionally and share insights

View LinkedIn Profile

34 years of software engineering wisdom to share

Response Time

2-4 Hours

I typically respond within 2-4 hours during business hours (US Central Time). For urgent matters, please mention it in the subject line.

General Questions

Usually same-day response

Suggestions & Ideas

Love to hear them!

Collaboration

Open to partnerships

What to Expect

I Will Respond To:

  • Technical debt questions
  • Content suggestions and corrections
  • Real-world case studies to share
  • Speaking/consulting inquiries
  • Collaboration opportunities

Please Don't Send:

  • Spam or marketing pitches
  • Requests for free consulting
  • Job recruitment (not looking)
  • Unsolicited product demos
  • Link exchange requests

Frequently Asked Questions

Most inquiries receive a response within 2-4 hours during business hours (US Central Time). Complex consulting requests may take slightly longer as we review your specific situation before responding with a thoughtful recommendation.

Yes. An initial 30-minute call to understand your situation and determine whether our consulting services are a good fit is always free. This helps both sides understand the scope and ensure alignment before any engagement begins.

Engagements range from one-time technical debt assessments and executive presentations to ongoing advisory relationships. Common engagements include debt audits, remediation roadmap development, team training workshops, and helping teams build the business case for debt reduction investment.

Technical debt principles and remediation strategies are largely technology-agnostic. Whether your stack is .NET, Java, Python, JavaScript, or something else, the frameworks for measuring, prioritizing, and reducing debt apply. Specific tooling recommendations are tailored to your stack.

Yes. Speaking topics include technical debt management, making the business case for code quality, AI-generated debt, and building engineering cultures that prevent debt accumulation. Reach out with event details to check availability.