@championswimmer@chrislciaba@GergelyOrosz yeah I would have thought an ex-Amazon senior engineer and startup founder would understand the absolute basics of business
Wanted to provide more clarity about this.
Yesterday, we had a regression in merge queue behavior where, in some cases, squash or rebase commits were generated from the wrong base state, making earlier changes appear reverted in branch history. 2,804 pull requests out of over 4M merged on April 23 (roughly 0.07%) were affected. We fixed the issue, we've contacted every impacted customer, and we're expanding our automated test coverage for merge queue operations. The team will be updating the status page with RCA details as well.
@_0xBenjamin_@bankoncrypto@shawmakesmagic this will work for about the first 80k - 120k tokens of the context window. after that your rules will start to get forgotten.
@rahuldoval@cjayls@rabi_guha haha “predict intent from context”
what context? you don’t have any context until the user gets there, and then you need to show them something right?
explain how this solves that
@dragosilinca@NickSpisak_ very few right now, niche applications where latency matters but quality doesn't AND deterministic conventional compute can't do it (way faster than 17k tps).
this approach doesn't work until model lifetimes are well over 6 months.
@adelwu_@lizwessel@JenniferHli@sdianahu@chetanp yeah but the underlying assumption is “be a company with a great idea that you’ve executed super well”
most startups aren’t this
I’ve invested in great companies that only became great later after growing in to one or both
the advice is good but limited
@aakashgupta what you describe isn’t an equilibrium - why would anyone maintain open source if they didn’t get status from download numbers?
this dynamic just means everything is closed source and less is shared
@Black_Mage01@theo it’s just really hard to build good consumer software and the only way it’s successfully been done is by big teams at for-profit corporations
AI might change that I guess