Appreciate the effort you put into building and getting this product live. It's already more than most do even with LLMs!
However, I think the value proposition should be much higher than simply "GitHub in Rust". GitHub is still a great, complex product, despite its recent problems. There should be some sort of x10 (or at least x5) improvement that will make people _consider_ migrating.
Did they really care about your day though? I feel that in France this type of conversation is rare but much more genuine and not a part of a “service”.
What’s the cost of a single laser? Russia is launching hundreds of those per attack, over a large territory. With a range of 5-7km you’d need _a lot_ of lasers to effectively cover a reasonably large city.
> I've gone back to consuming a limited amount (~1.5 cups) only between 10am and 6pm. I used to have none on weekends feeling a bit off to reset but eventually even this seemed pointless, so 10am-6pm every day has been working well.
That! I lived on zero coffee for many years, however, it is much more difficult to do so once I became a father. I am consuming a maximum of 2 cups of coffee: first one around 10am, the second one in the afternoon but strictly before 5pm. I do that Monday-Friday and I either consume less or no coffee at all on weekend.
I also use decaf if I want to a coffee (as a drink, not as a boosting drug) and if I already consumed my daily 2 cups.
While I agree that the key to success is _a lot_ of communication, there is much more to the management of remote teams than that: you should treat them like the on-site teams; communicate a lot but prefer video conferencing; try to give your remote teams the overall context; stick to as few means of communication as possible (if it's email, then stick to email).
Yes, they do but it depends on the context. In my previous company (web agency) they were solving several issues at the same time:
- Project Manager (Proxy Product Owner) is communicating with the client on a daily basis and is getting some important updates about the progress of the Sprint;
- if there are some unexpected developments (for example, some User Stories appeared to be more complex) the Team and the PO can make a decision about it together, discuss various options, etc;
- the distributed team has a chance to see each other (we were encouraging video calls via Google Meet).
However, there are some certain rules which should be followed in order to make Daily Scrums effective:
- video (or at least audio) conferences for distributed teams – it can actually be slower to have this meeting via Slack;
- they must be timeboxed (15 minutes max);
- stay pragmatic about what you are discussing and ask the feedback of your team about it.
However, it is still better than in the most of the other European cities and it would probably take less or equal time if you had to do the same trip by car.
Tech-related:
1. TypeScript
2. GraphQL
3. Rust
4. AWS (serverless-related)
5. Functional programming in general
Less-tech:
1. Lean Startup
2. Reading "Cultivating communities of practice" by Etienne Wenger
3. Trying to understand the rentability of real estate investments
Crimea was an "oblast" (or region) of Ukrainian SSR and the referendum was about re-establishing the Crimean Autonomous republic which was the case and was signed by Ukrainian SSR council: http://zakon1.rada.gov.ua/laws/show/712-12
During the separation of republics from USSR, Crimea stayed as a part of Ukraine (and voted for the independence of Ukraine, btw) which was a logical move in terms of infrastructure.
However, I think the value proposition should be much higher than simply "GitHub in Rust". GitHub is still a great, complex product, despite its recent problems. There should be some sort of x10 (or at least x5) improvement that will make people _consider_ migrating.