блин реально у меня страх писать челикам звать потрахаться тк боюсь что когда они приедут (а это через полдня/день) мне уже будет совсем не до них и я буду стрессовать что занят не делом а СоЦиАлИзаЦией

can we do a zero-night stand plz?

мне стрёмно ходить между полок книг в библиотеке. раньше (десять лет назад) мне всё хотелось взять и прочитать. теперь у меня выученная беспомощность от того, что почти всё это никак не применимо в жизни

— какие у тебя языки любви?
— дрочить на фотки тех кому лень написать

короче теперь я всегда буду пить кофе на дейтах чтобы эйфория от кофе выстраивала нейроны так будто я влюбился

We agreed to this pilot without negotiating neither salary nor equity. I want to show my value first and negotiate this stuff later on - in hope that it will rise the offer.

Yesterday we interviewed two junior candidates. Hopefully it’ll speed up the development process. Honestly, I’m lazy to code all things on my own - it’s just a no-grow. I want to take the role nobody else takes - the Forward Deployed Engineer role - the guy that is constantly communicating with users and translates their needs into product vision and programming tasks.

Our CTO has a different look on things - more waterfallish, long release cycle. He’s the guy who made the first versions of all our services. It probably took him some time to do that. It’s also interesting to know how maintainable and expandable the server-side will be in the end. I haven’t yet seen our PHP back-end, but it sometimes behaves strangely - so I expect anything.

Two juniors started performing surprisingly well and fast. I nearly have a feeling that now I'll be busy all the time just lying them the path with tasks. Which probably will turn me into a product thinker.

I somehow should track the progress of both juniors to value them by next Tuesday to make an offer with a reasonable salary. I'm lucky to have both at the same time, still it's gonna be hard to compare their skill and productivity.

The ultimate goal of life is to maximize oneself’s net present luck. Which in my case with Asap breaks down to maximize my career growth (skills + self-brand) and maximize my net present earnings. The latter turns into salary and option. Option turns into its percentage of the total valuation and the valuation of the company itself.

For now let’s only concentrate on the very last component. How can I grow the company’s valuation more efficiently? Asap raised $150k kinda two months ago. It looks like I’m the only guy who’s going to hire tech team members. Salary expenses is the biggest term on the cost breakdown during the seed round (say, 90%). If I knew how much free money we have left to have the runway of 12 months, my goal is to hire the right guys to implement our hypotheses in the code asap.

I wonder if I can finally not write any more code myself.

I’m slacking a little bit and searching for a work-life balance for the weekend. Looks like <> works the entire weekend because he may have a lack of many other hobbies - we’ll figure that out.

PHP wasn’t the choice of <>, there was some earlier guy that wrote the initial version of the back-end and then left the team. <> also says that we have a medium-size codebase - it can’t be rewritten overnight, but it’s also not that huge. So we can consider rewriting it in some more reasonable framework - holding the database the same. I wonder what kind of ORM lies in there.

Asap is a cool lifestyle - awesome and diverse - and we share a lot of dishes to enjoy the taste we can discover in the restaurants that we signed up for partnership. We’re also working in the most NYCish district in Moscow - it gives a sane dosage of dopamine at night on my way from the last cafe to the subway station.

It also allows me not to code. I enjoy learning architectural patterns and teaching guys software practices but I’m not passionate about digging into current quirks, chasing for a typo and spending life in the debugger. It distracts me from thinking about competition and customer love.

This week is gonna be our rollout to many cafes - or at least the next week for sure. Let’s see how it goes.

We had a long call with founders and agreed that we need to hire one more back-end guy (PHP Laravel 4.2) to match the capacity of the front-end. <> had big concerns that “our code may leak to some third party that may benefit from it eg. by rapidly launching a clone”. His idea is that our back-end consolidates the two-year knowledge obtained by iterations of what are the exact “parameters” under which the back-end with this particular product requirements starts being valid. Finally we managed to lower his concerns by explaining that business is not just “back-end” and NDA means quite a lot in the US, where we’re trying to establish a business eventually.

Yesterday I also started coding the order logic and I felt like I should spend some time deeply understanding React/Redux concepts to make better architectural decisions. It’s hard to find the time slot for reading manuals, books and docs, though.

I assume that we’ll spend the next two-three weeks in a steady development by figuring out the team process - ticket system, who does what, code review, cross-project priorities - and then we’ll maybe try to grow.

<> has accepted the offer with a great question afterwards: “How do you yourself think about your offer? Is it average or lower than market or higher or what?”. It’s a great trick to gain a negotiation power for the future.

I kicked off a major refactoring in an attempt to match industry cleanness and architectural standards. Not only do I personally feel bad about coding into our codebase, but I also want to understand it as a whole before it’s not too late. I also feel like I’m the only guy in our team who’s capable of setting up the most efficient coding patterns to speed up our development process.

I don’t yet have time to pull our task list from my Google doc into any Trello-like board, as CEO is asking it for a week already. I’m balancing on their credibility and I’m trying to make an integral effect of super-rapid development during the next 4 weeks. And then, maybe, there can be a point where we can negotiate something.

I still haven’t seen the back-end source and I got eager to see it soon. Given the stub structure of the front-end app that <> provided I suspect that he might adhere to coding practices that generally slow down the coding process 2x-3x - bad architecture, code repetition first of all. Good signs are that his documentation for the API is clean and well-written, but so far our back-end is performing slowly even on basic request. I’m yet to find out if there’s any reason related to a “home-made-ness” of <>'s programming skills.

On Friday evening I said to <> and <> that I’m gonna be off for two days and at the same time I managed to delegate the preparation of the next release to <>. <> worked the entire Saturday sitting next to <> and <>, and therefore the release is nearly ready. Therefore the self-managing front-end team is not far from reality, and I can concentrate on more product and more expansion.

I asked <> about the actual blockers of our American expansion. By inertia he thought it was the development, but actually the B2B sales cycle is gonna be way longer than our software building cycle. So he confirmed to rethink this more during the next week. The path is actually clear, and we should actually start if we don’t want to sit in Moscow for ages.

On Sunday I started making Snakify 2 a reality. My focus is:
- Exercises only, no extra content
- JavaScript first
- Clean, flat, responsive
- Teacher’s access
- Hidden monetization through sell of access to extra content.

We failed to release on time. The more we go from emulator to real device to vendor’s device, the more bugs we catch. I still don’t think we need to go for things like feature freeze, code cut-off and such, but it’s hard to predict now when we can release the thing because there are so many things that can break.

I rapidly went from “claim 3 days work week before the cool offer to go for full time” and the concept of skills - equity - salary balance (and basket) to discussing these very things with <> (suddenly today) and <> (planned for tomorrow). Looks like by the end of this week I’m gonna have a draft offer or something.

Yesterday I got access to our old mobile app and today I successfully managed to extract APIs and put them into the new one. Today I finally got an access to the back-end, initially by claiming it as a blocker to understand hiring needs for the second back-end developer and then to kick off hiring. I’ll probably dig into it this week more and implement something that I urgently need right now. There are many things in it though, 160 models, similar amount of controllers, vendor/ and management/ - a big monolith of used, projected and deprecated functionality full of minor cases and such.

I start spending evenings and weekends in ShAD where’s Mobilizatsiya currently sitting. The cowork space where I spent last two years when not being abroad - doing Snakify - was always a place full of machine learning enthusiasts. Now it’s full of 19 yo junior front-end guys moved to Moscow for three summer months - such a cool atmosphere to be surrounded while making Snakify 2. They learn how to make products using new technologies and industry methodologies, with team roles assigned and mentorship and ideas coming from Yandex.

I reread my Snakify 2 manifesto written in April. Surprisingly, nothing changed from that time except for moving towards an instant code evaluation due to JavaScript-first approach. Which isn’t the game changer in any way. It was just a cool branch explored while experimenting.