Contact

Let's discuss what you are building

Choose the closest type of request and send a short description. A complete technical specification is not required.

Send a message

The more concrete the description, the more useful my answer will be.

Please tell me your name.

A valid email is required so I can reply.

Please check this field.

If something is broken, tell me what it does when it breaks. That is usually the most useful sentence in the message.

Describe the situation in a few sentences.

Please check this URL.

A private repo is fine. I do not need access to give you a first answer.

Please check this URL.

Please check this field.

Please check this field.

Please check this field.

Please check this field.

Please check this field.

If you prefer an answer there. Email stays required either way, so a reply always has somewhere to land.

Please check this field.

Direct

Or reach me anywhere here

All of these arrive in the same place. Use whichever one you already have open.

@ Email inbox.golovanov.dev@gmail.com IN LinkedIn linkedin.com/in/golovanov-dev · best for roles and hiring TG Telegram t.me/roman_xdev · best for short, fast questions GH GitHub github.com/golovanov-dev · issues and open-source collaboration

About replies

I read everything that arrives. I reply to anything concrete: a real problem, a real role, a real system. I'm not going to promise a response time I cannot honour, because I build and ship alone and some weeks are heads-down. If your message describes a specific situation, you will hear back from me.