Let's talk

Have a project, a stubborn bug, or a slightly weird idea?

A polished brief is not required. Tell me what you are trying to make, what is getting in the way, and where things currently stand. We can figure out the rest from there.

Book a call

Pick Your Route

02

Book a call

Better explained out loud?

Grab a thirty-minute introduction. No sales deck and no elaborate preparation; bring the problem and whatever context you have.

Find a time
03

Open source

Found something in WebTricks?

Bugs, feature ideas, and implementation questions are most useful when they stay close to the code. Open an issue so the answer can help the next person too.

Go to GitHub issues

No perfect brief needed

A useful first message can be four lines.

Enough context helps me give you a useful answer, but you do not need to solve the problem before contacting me. That would rather defeat the point.

01

The goal

What are you trying to build, fix, or figure out?

02

What exists

A live site, codebase, design, rough idea, or nothing yet are all valid answers.

03

The constraints

A rough timeline, fixed launch date, current stack, or important limitation.

04

The useful links

Share anything public that helps explain the problem. Keep credentials out of it.

Prefer regular email?

hello@thecoderaccoons.com

Write an email

Please do not include passwords, API keys, private customer data, or other credentials in the first message. I reply personally, and if I am not the right fit, I will tell you.