Which to be fair isn’t that great in either country regardless if you work in tech or not. In major cities if you rent or have a mortgage (taken out recently) it’s basically poverty level.
Porsche did something similar for the 4 cylinder 718s. There is a microphone, processor and amplifier above the exhaust that feeds a speaker unit in the cabin to “enhance” the sound that is muffled due to the turbo.
It is good for aggressive driving but just creates a bad drone when highway cruising. Good have been implemented much better. Lots of people pull the fuse to disable it.
Omarchy!! shipping a window manager with defaults and or a terminal with a config - what an unspeakable sin.
Linux should be hard and shitty and it should break all the time!
What is this newfound obsession with distros that just works and have some great setups and defaults.
Where do we end up if you can just close your laptop lid or copy paste with the same key or or or if even… gasp… the theme is automatically applied across all apps?
Having literal billionaire best buds backing the project probably helps one gain traction, no? Toss in a dash of weird culture war bullshit, and… well. Distro popularity isn’t exactly a meritocratic system.
Respectfully, in the best case you don't really know what you are talking about. These three cities certainly cannot be categorised as tax havens in any sense of the word, and the local legislation is objectively different - as evident to anyone comparing it.
This reads like an AI writing to a point an author wants to make without there being evidence.
It is completely incoherent. Apparently we just need markdown and git, but also a knowledge graph and pgvector which accounts for most of the performance.
We don’t need semantic search, because we use… hybrid search (semantic search plus bm25)???
Really bad look for an AI consulting company this.
The way this argues against its own premise is really ChatGPT like.
This happens when you ask it writing about something that isn’t actually true.
Which again is funny because as an AI consulting company you should have expertise to know what you want to weite about
But good news, this company also has a free ebook. I am sure it is fantastic.
The second feature shown in this global launch is ... widgets. Like, Windows Vista widgets. And then, I could also open phone apps but not on my phone but on my computer (because I'd want to do that) and then the remaining feature is file sync.
I am just lost.
I wanna watch a documentary on how this kind of thing gets thought out and made and approved by a lot of people and then comes to being annouced as an actual hardware product.
Maybe as a comment, you really put weight on intent classification. I am not sure why. For it to work, you are gonna need my expert domain input. And given that, I feel like the classification bit is basically solved. I wonder a bit why this is the feature you seem to put front and center (e.g. screenshots)
tl;dr: Langsmith + homegrown intents doesn't scale with contributors and agent usage as an Analytics solution. Voker adds trend and usage insights on collaborative dashboards that work for the whole AI product team.
Nice, sounds like you've set up your own solution in house. We definitely see some teams do that, and for some it works perfectly, for others, its too expensive to maintain - they get new requests for new dashboards or different subcuts of data from product or design teams, or they run into an issue like way too many intents generated to be useful, and its not worth the tradeoff of investing time in building internal tooling. But for some it makes sense to roll your own! It also really depends on how many people on the team are involved in building the agent products, and how much volume your agents have. If you have millions of conversations a month with thousands of unique intents, you have to set up data eng pipelines just to process categorize, and store all that data in a way thats usable for the whole team.
When it comes to Langsmith, we hear about them a lot from our customers, pretty much all of them love it as an obs tool, but most say that only the engineers have access or spend time in it, and they've told us the strength of Langsmith is its technical tracing, not its visualizations, ui, or usability. They've told us any "insights" are very canned (because thats not Langsmith's key focus).
We add self-serve analytics - like how Google Analytics lets marketers see how their website is performing without needing to ask engineers to write SQL queries on cloudwatch logs.
Ex: PM can self-serve and look at trends in what users are asking of agents, notice a problem, do a quick RCA, look for reproducibility across other sessions - before deciding to assign as an issue to engineer. Old way would be: PM hears a complaint from a customer, asks the engineer to "look into it" and the eng spends 4 hours combing through Langsmith logs to hunt down one session without even knowing if its actually a widespread issues
reply