No formalities needed — just say what you need. Below are three channels I actually read, a few things I am happy to talk about, and some email templates. If you are not sure how to start, copy one, change a couple of lines and send it — I will follow.
I clear my inbox regularly, so email almost never gets missed; WeChat suits urgent things, GitHub suits code. Pick whichever is easiest — sending the same message twice only slows things down.
Attachments and long threads welcome
Please say who you are when adding me
Not only technical topics. These are just the areas I am confident in — questions outside the list are welcome too. If I cannot answer, I will say so rather than bluff.
Android AOSP, Linux BSP drivers, in-house cross-platform UI frameworks — architecture choices and migration paths from the lowest layer up to the application layer, and the pitfalls you only learn by hitting them.
Adaptation, certification and localisation for worldwide platforms: how to get from “it runs” to “it ships in volume”, and the parts of cross-border collaboration most likely to spin out of control.
Building a team ladder, engineering standards, knowledge assets; and what exactly you need to pick up on the way from engineer to technical lead.
How these dependency-free, offline-capable, mobile-first things get built. Tell me what is wrong with them, what you need, or simply which tool you wish existed.
If you have a role that fits, or need an outside technical advisor — write down the context, the goal and your timeline, and I will assess it properly and reply.
No agenda needed. A question, an idea, a complaint — anything except bulk advertising.
Each one opens an email with the subject and body already filled in — just replace what comes after each colon with your own details. Those are the fields I need most to decide whether and how to take something on.
Once you have added me, a line saying who you are and where you found me helps me avoid treating you as spam.
Best for short messages, setting a time or sending a link. Please say why you are adding me, or the request may end up deleted by mistake.
Occasional technical notes, industry observations and write-ups of things I have built. If you only want to read, this is the one to follow.
I know exactly how hard it is to send that first message. So please do not polish the email — just say who you are, what you want and where you are stuck. I will take it from there.