4 8 1 0 9 3 7 2 6 5 1 8 0 4 9 3 2 7 5 6 1 0 8 4 3 9 7 20 1 7 4 2 9 5 3 8 6 0 7 1 4 9 2 5 8 3 6 7 0 1 9 4 2 8 51 0 1 1 0 0 1 0 1 1 1 0 0 1 0 1 0 1 1 0 1 0 0 1 1 0 1 09 2 6 3 5 8 1 4 7 0 9 6 2 3 8 5 4 1 7 0 6 9 3 2 5 8 4 77 3 0 8 4 1 6 9 2 5 7 0 3 8 1 4 9 6 5 2 0 7 8 3 4 1 9 62 5 9 1 6 0 3 7 4 8 2 9 5 1 0 6 7 3 8 4 5 2 1 9 6 0 3 76 4 3 7 0 2 8 5 9 1 6 3 4 7 2 0 5 8 1 9 3 6 7 4 2 0 5 81 0 0 1 0 1 1 0 0 1 0 1 1 1 0 0 1 0 1 0 1 1 0 1 0 0 1 18 1 5 2 7 4 0 6 3 9 8 5 1 2 4 7 6 0 9 3 1 8 2 5 7 4 3 03 7 2 9 1 6 4 0 5 8 3 2 7 9 6 1 0 4 8 5 7 3 9 2 1 6 5 05 9 4 0 8 3 2 1 7 6 5 4 9 0 3 8 1 2 6 7 9 5 0 4 8 3 7 10 6 8 5 3 7 9 2 1 4 0 8 6 5 7 3 2 9 4 1 6 0 5 8 7 3 1 2
Let’s talk about your project
A couple of paragraphs about the problem is plenty for a first conversation. I read and answer every message myself — no templates.
I reply within two business days. If you have not heard back, the email did not reach me — please send it again.
What I turn down: patching someone else’s legacy code with no access to the team, front-end markup and visual design, “finish it over the weekend” emergencies, and projects where the decision is already made and what’s wanted is a pair of hands with no questions.
github · linkedin · rss · hello@kenakamu.org