- sporklandNot dismissing your point, but Looking at the article, it looks like it's in rust unsafe code. Which seems to me to be a point that the rest of the rust code is fine but the place where they turned off the static safety the language provides they got bit.
- As told in Innovator's Dilemma mainframe companies would have told the exact same story right up until the cheaper alternative met all of their core needs. But in this case I don't think you get disrupted by copycats but instead by savvy business users building their own disposable alternatives which get just enough done.
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.
- Hearing about Richard Nixon at the Bohemian Grove gave me similar vibes.
- Garbage reporting: 1. AWS had an outage 2. AWS has lost a lot of employees
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.
- I've been using divvy, had no idea it isn't maintained... but I'm not sure if I'd need any more features outside of what it already does. What items do you want to see them add?
- I currently use divvy and effectively a desktop per app. It's not perfect but gets me most of the way there.
- As someone that has influenced company politics as an independent contributor (non-manager) repeatedly, I find you have to go through a lifecycle: 1. When you first join you need to show you can actually accomplish things, likely through code contributions / launching something. 2. After you do that you start becoming part of conversations and can start influencing directly. The key here is problem identification and bringing useful independent data. Whether we like it or not managers have built in leadership authority, IC's have to establish it by above, so usually the leadership group is dominated by managers, but if you can bring useful technical data / solutions and become a "voice of the people" if you will that lets managers not have to dig in and solve every problem you will start influencing politics.
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.
- Before that people just took flex days and it was fine. With RTO enforcement and measurement it's made it less flexible
- Thought the same, but it's much less insightful than the original.
- This is the correct answer. You do a pre-filter on a permissions correlated field like this and post-filter on the results for the deeper perms checks.
- If you have a field like and acl_id or some other context information on the data that is linked closely to a user's files. You can pass in the user's set of those field values to the vector database to pre-filter the results and do a permissions post check with a fairly relevant set.
The vector db definitely has to do some heavy lifting intersecting the say acl_id normal index with the nearest neighbors search but they do support it.
- Does anyone have data on how much better these 1M token context models produce better results than the more limited windows alongside certain RAG implementations? Or how much better in the face of RAG the 200k vs 1M token models perform on a benchmark?
- The founding fathers didn't see the corrupting influence of political parties on the separation of powers. It's covered quite well in this SMBC related comic: https://www.lawsandsausagescomic.com/comic/101
- While I'm sure some of these predictions will come true and we'll have to layer some additional prompting and context engineering in here...
MCP seems to be the ultimate inheritor of ReSTful architectural practices as described by Roy fielding but instead of needing a human on the other end to interact with links (hateos) you can have an LLM bridging the gap between user intent and concrete subsequent calls.
So many issues around versioning and the fragility here will likely start to disappear. Like embeddings I'd put a bet on this being one of the major unexpected architectural improvements that lets us build our scaffolding a bit higher before it collapses to use a Steve Jobs analogy, LLM's at key glue points to create looser coupling.
- The problem with this line of thought is that everyone just uses it to hate on people they already hated on. You go after rich tech monopolies, progressives generally go after big business, conservatives use it to go after the biggest business of all, the government.
We all just need to focus on monopoly in all its forms, instead of letting the politicians continue to separate us using division without difference.
- And they managed to get it flagged. The longer HN mods pretend this is just natural flagging because folks are sick of the same old topics and not a coordinated effort to control the narrative, the more I'm going to start seeking alternative sources for interesting news.
At the very least someone showing data that in aggregate there are just more follow-on duped stories about things and they're letting one through un-flagged (ideally the top up voted one) to show that there is or isn't bias creeping in via the flagging system would be helpful in re-establishing trust.
I probably have a unique view as I view HN through an RSS feed of posts with over 100 up votes. Every single time I see a post critical of X or Musk and click through the story has been flagged. I'll try to do data analysis via that lense and see what it turns up.
- As someone that criticized a number of their employers API's for not being sufficiently ReSTful especially with regards to HatEoS, I eventually realized the challenge is the clients. App developers and client developers mostly just want to deal with structured objects that they've built fixed function UX around (including the top level) and desire constructing URLs on the client. It takes a special kind of developer to desire building special mini-browsers everywhere that would require hateos and from the server side.
I think LLM's are going to be the biggest shift in terms of actually driving more truly ReSTful APIs, though LLM's are probably equally happy to take ReST-ish responses, they are able to effectively deal with arbitrary self describing payloads.
MCP at it's core seems to design around the fact that you've got an initial request to get the schema and then the payload, which works great for a lot of our not-quite-ReST API's but you could see over time just doing away with the extra ceremony and doing it all in one request and effectively moving back in the direction of true ReST.
- I find having a therapist for an hour each week and then using chatgpt or gemini for specific scenarios that pop up providing some context from my understanding in therapy as well as telling it to be brutally honest with me and don't mirror or trying to make me feel better leads to some pretty useful insights into my psyche off cycle from therapy.
Please note this is after at least a decade of therapy and couples therapy so I've got a solid base of self insight that I'm working from.
- yeah I've been thinking about them as stochastic content addressable memory. You can put as many next = userInput; while(true's) { next = mem[next]; } around them as you need in different forms. Single shot. Agents. etc and get wildly cool results out, but it's gated by some of the limitations there.
- Over a decade ago I was starting a java process up with local MySQL and getting 45k rps read, request per thread with load wasn't hard to achieve. Not sure why this is an accomplishment.