One of my tutors at university claimed that she was able to read 9th century manuscript Cyrillic faster than modern printed books because the orthography was more varied and easier to scan/speed-read.
(That wasn't something I found to be true)
774 karma · joined January 28, 2011
Email: david at dbuxton dot com
One of my tutors at university claimed that she was able to read 9th century manuscript Cyrillic faster than modern printed books because the orthography was more varied and easier to scan/speed-read.
(That wasn't something I found to be true)
However I think we should be thinking harder about how coding will change as LLMs change the economics of writing code: - If the cost of delivering a feature is ~0, what's the point in spending weeks prioritizing it? Maybe Product becomes more like an iterative QA function? - What are the risks that we currently manage through good software engineering practices and what's the actual impact of those risks materializing? For instance, if we expose customer data that's probably pretty existential, but most companies can tolerate a little unplanned downtime (even if they don't enjoy it!). As the economics change, how sustainable is the current cost/benefit equilibrium of high-quality code?
We might not like it but my guess is that in ≤ 5 years actual code is more akin to assembler where sure we might jump in and optimize but we are really just monitoring the test suites and coverage and risks rather than tuning whether or not the same library function is being evolved in a way which gives leverage across the code base.
Moscow’s street dogs are renowned for their intelligence. I have seen street dogs taking the escalators on the Metro. This dog worked out not just that the beeping + discomfort was worth the freedom, but also that he could wear out the battery faster by going up to the very edge of the fence - where the chirps became an uninterrupted beeeeep - and as soon as the beeping stopped, whoosh he was gone.
In practice high variance translates on the downside into failure to do basic things that a minimally competent human would basically never get wrong. In agents it's exacerbated by the compounding impact of repeated calls but even for basic workflows it can be annoying.
This is very interesting finding about how to improve capability.
I don't see reliability expressly addressed here, but my assumption is that these alloys will be less rather than more reliable - stronger, but more brittle, to extend the alloy metaphor.
Unfortunately for many if not most B2B use cases this reliability is the primary constraint! Would love to see similar ideas in the reliability space.
The most difficult part of the process (not dealt with in this version of Passport Application but maybe a future DLC pack?) was actually finding someone who could certify my evidence (you are meant to submit originals but they keep the docs including passports for 3-6 months which is a bit unrealistic if you are living abroad). I can't remember the exact rules but it wasn't possible to use a US notary or a normal solicitor certification process and instead I needed to go to a council office.
After calling about 5 councils all of whom disavowed any knowledge of the process or its requirements I ended up finding someone at Islington Council who was delightfully helpful. But it was one of the more frustrating UK government interactions I've had.
I am very excited for the whole STT/TTS to go away and for us to have models that really "hear" exactly what you said.
Sometimes this is about accent but a lot of the time, the AI won't spot areas where you e.g. fudge a case ending or the stress on a word. Yes, you can get some of that pronunciation right by the AI repeating back with the correct stress or clear case, but you never really get the confidence that you would get from an actual human.
Another product suggestion - turn off transcription (at least for the tutor side of the conversation; I'd suggest both). Personally I find it distracting at best for languages I already speak well and a crutch for those I don't.
Finally, I find it really very hard to enjoy having a random conversation that's not very directed ("What interests you most about artificial intelligence?"). I'd suggest that there are ways of making it more goal focused without being explicitly gamified - maybe something like, here's a position and you have to persuade me (AI debate club!), or something that brings out an actual opinion or relates to a concrete experience ("what's your main goal in your job this year").
Overall though this is the first product I've seen in this space that I might actually use, so well done.
- That it's still way cheaper in most instances to book a return (especially where the "trip" straddles a weekend) rather than a one-way fare when travelling long haul - even if you just throw away the return flight.
- That you can sometimes get access to totally different inventory by booking a package including accommodation, even if that accommodation is one night in a shared dormitory in a hostel (which you just don't go to).
At least group discounts have a recognizable economic rationale. But in these examples you are getting a strict superset of the same SKU (OK, maybe the change rules might be a little tighter, but not in a way that's perceptible) for less money.
(I haven't used Roam personally and have no idea if it even has a plugin architecture or is extensible, but this reminds me a lot of some of the knowledge management work we're doing with corporates)
Our experimental use case is enabling quick and dirty integration of web-based docs into an employee service agentic chatbot - lots of the questions are around “how do I max out my 401k”, which connects to internal information, but some are more like “how do I link a calendar to calendly”.
The one thing I’d love to have in the search product is a cruft cleaner for the results of web queries. Where you have cached the data presumably this wouldn’t add much overhead. Reduces what you have to feed to the LLM downstream and might improve the embeddings performance.
Genuine question!
Gives you a different lens on enterprise software adoption and implementation!
As a parent, I’m always super conscious that one is tempted to praise the achievement, but this is good summary of why that is a bad idea. Instead we try hard to praise the effort, especially when our kids fail. Not always easy!
I think this is basically another example of political polarization, combined with employment patterns. White collar workers broadly speaking place a higher value on their time and mostly belong to "tribes" that value their health and environment. Removing cars is great for that as bikes give control over journey times (and in most cases in e.g. London reduce them) while positively impacting the other.
Blue collar workers may not be able to do their jobs with just a messenger bag containing a laptop and airpods. Also, their political identity has been dragged further towards the radical-individualism end of the spectrum where collective action on e.g. environment is hard, and trust for bossy health authorities telling them to exercise more is low.
The slightly strange side effect is that you end up with an item which is way cheaper (a bike at e.g. school dropoff vs a car) that becomes a signifier of social status. I am sure there are loads of examples of this phenomenon but none spring immediately to mind!
The idea being to make sure that a payment credential has been requested by a legitimate chain and only then provide a single-use token (or similar).
Is there anyone working on agents that can consummate transactions out there who is thinking about this area that might like to chat? Email address is in my profile if so.
My current setup here in case useful to anyone: https://gist.github.com/dbuxton/3ccdfd88b05e1f2807c05fe32f50...
(If anyone knows how to show bluetooth in top menu all the time on Sonoma I'd love to learn - haven't done much investigation but option seems to have disappeared in the UI...)
The challenge Microsoft have set themselves however is that their problem domain is very large. They have to accommodate many different types of queries. We do benefit from having a specific type of usage pattern and much smaller data than a “real” Onedrive.
That said I am baffled that this product has performed as badly as it did in the review. These seem like pre-alpha type issues. I guess we should congratulate MS for being willing to put these things out to test at early stage but… come on!