415 karma · joined July 27, 2011
Guy has pipes.
Oh his software was pretty good too.
Folks also need to remember that a lot of blog posts are written by engineers or managers that have their own agendas and careers and often external blog posts can be a form of self marketing or idea marketing that an engineer or director has been pushing internally.
I have no idea if this happened in mozilla's case but the person that wrote it seemed to talk about the their own internal harness / fuzz testing framework quite a bit, and I imagine it was probably a big part of that person's scope / accomplishments and will probably show up at their end of year review and on their resume.
My desires are pretty different in the two scenarios. Q&A mode if it's not quick to respond I'll think something is wrong with my phone.
Deep think mode I'm honestly kind of pissed off at how fast it tries to respond. I want it to slow down and give me a chance to process and use extra compute on its side (including newer models) so it doesn't just spew low thought bullshit at me.
It seems like the system could detect which of these two modes was happening and adapt, including protocol.
I haven't tried the voice mode since the new model updates, maybe it's gotten better.
Counter to everything I just said though and germain to the topic at hand, when I'm in q&a mode that's probably the worst time for it to drop audio as it changes the query significantly. vs when I'm talking at it for 2 minutes it could probably throw half away.
Like smaller models that show effectiveness on problems with verifiable rewards when run in a loop with external grounding context?
And I like your ideas but I don't see why the venues and artists don't want to capture more of what people are willing to pay enabled by what the parent comment suggested.
I wonder if in your system it actually attracts fans or just people that have the time to wait for tickets.
1. He kept citing things like PGP, C++ and distributed systems as things in common between Satoshi and Back, but would have described 75% of pragmatic comp sci folks at the time.
2. His end section about word correlations where he started with Back's weird isms and then started finding them in Satoshi's writings seemed like pure Texas sharp shooter fallacy. He started with broader scoring mechanisms and when those didn't work he started seeking out measures that fit his case better.
All of this based on a vibe of how the guy seemed in a Netflix documentary.
I have no idea if Satoshi is Back or not and would love to close this chapter. But this "reporter" seems to have started with a conclusion and then tried to find data that proved the conclusion.
It feels like a company should have to prove they didn't pass the tariff on to consumers in order to collect this.
Though I think one thing that is being overlooked is that Platforms are the hidden hero under all of this. A lot of AI products are benefiting from various cloud platforms that have been created that make it easy to deploy and opperate these apps. So as long as you are providing a sufficiently general, high productivity platform that can't be emulated by one of the major vendors you'll likely become the new runtime.
Conclusion: The brain drain lead to the outage...
I need an LLM trained explicitly on folks confusing correlation and causation and put a big old red dot in my address bar.
I love that there's a whole section "The talent drain evidence" trying to defend their journalistic integrity, but they then go on to totally face plant.
Where I see a lot of folks fall down:
1. Focus on problems that aren't attached to either important issues: tabs vs spaces isn't gonna sink the company. If you start getting triggered about a technical thing and can't explain the impact in terms of availability, cost, productivity you'll quickly get tuned out. That isn't to say the work isn't important, it's just not workable at the political level, you just gotta fix it through influence with other IC's.
2. Inability to explain how the problem is attached to important issues: Similar to above, even if it's a real problem the ability to craft a narrative so the managers and other leaders can connect it up to real value that they'll see.
3. Discomfort with taking risks: No important problem / political problem is without risks / gaps, either in terms of timeline, impact, decision paralysis (as there are truly multiple ways to skin a cat). If you need 100% certainty to kick into gear it'll be hard to influence at the top levels as it often requires taking decisions and the inherent risks involved in signing up for those outcomes.