I lead engineering teams @happening_xyz building sports betting products. I occasionally have opinions on tech, business, strategy (sort by confidence desc).
@GergelyOrosz Out of curiosity, where did you get the 26-30m estimate from? iirc, GutHub had about 100m accounts in 2023 (so, pre-ai). Stack Overflow has about 20m accounts.
@GergelyOrosz Not to mention many who probably nuked their sites in a panic-induced rush to stop the bleed, thereby creating unnecessary work and outages to customers.
@GergelyOrosz “Organize world’s information and make it universally accessible” and “Don’t be evil” were quoted frequently 2014-2019, but I suspect a lot of that changed as internal narrative shifted in recent years.
@grok@elonmusk MOXIE was run in Mars atmosphere, is that really comparable to operating on Earth?
Can you elaborate on the photoelectrochemical systems efficiency point you made? Where can I learn more?
@grok@elonmusk Do we have a more efficient way of converting CO2 to oxygen?
Obviously, still a pretty good point on deserts (or roofs for that matter).
@ivanburazin I've had very similar thoughts and did a talk about it ~1y ago: https://t.co/6VpG8kPhPk
My conclusion though was different - the only moat that's long term sustainable is a healthy, self-healing culture - it's what allows you to continuously adapt to a changing environment.
@d_stepanovic I'm more interested in the questions that have to be answered in order to try to estimate effort on a project than the estimate itself.
Understanding what are the hard parts and solving them first is the useful part.
Fairly happy with how the talk went - there are obvious thing to improve in delivery, but I think I got the message across. LMK what you think.
https://t.co/6VpG8kPhPk
So, we're organizing a hangout at our Zagreb office and I'll be talking a bit about everyone's fake Peter Drucker quote. I was told there'll be beer as well.
https://t.co/8qpZhAe0Ic
@gunnarmorling@NikkiSiapno With idempotency, replaying multiple, potentially unrelated messages isn't an issue.
And with single-writer principle, you ensure the same key (e.g. customer-id) is always processed by the same pod, allowing for eventual consistency.
@gunnarmorling@NikkiSiapno Got it, thanks. Transaction support is frequently first to die when you want to cheap horizontal scaling :-)
We've successfully side stepped issues you mention by designing services with single writer and request idempotency principles in mind.
@gunnarmorling@NikkiSiapno Can you expand on the concurrency control issue? What behaviour would you expect in Kafka and why is it crucial for event sourcing?