69 karma · joined July 18, 2025
That ship has long since sailed for every search product. Companies have long-since learned that intent-based results are much more profitable (why show an empty result page when you can show something for people to buy or click on?), but it is also often genuinely useful when your search is not perfect or what you want doesn't actually exist. I agree that it is annoying when you really truly do only want something very specific and the ranking prioritizes the wrong things (e.g., sponsored results, more profitable items, etc.) over exact matches, but can you honestly and truly say you've never found any value from intent search algorithms?
That said, with enough stock growth, the stacking RSU grants can still enter into "never having to work again" territory depending on your role/level and how many grants you've been able to stack.
try (SomeResource foo = SomeResource.open()) { method(foo); }
or
public void method() { try(...) { // all business logic wrapped in try-with-resources } }
To me it seems like lexical scoping can accomplish nearly everything functional scoping can, just without any surprising behavior.
> Author also seems to expect that the result from MCP tool usage will feed directly to an LLM
Isn't this exactly what MCP is for? Most tools I've come across are to feed context from other sources directly to the LLM. I believe this is the most common use-case for the protocol.
AI responses seem to have very low information density by default, so for me the irritation is threefold—it requires very little mental effort for the sender (i.e., I often read responses that don't feel sufficiently considered); it is often poorly validated by the sender; and it is disrespectful to the reader's time.
Like some of the other commenters, I am also not in a position to change this at work, but I am disheartened by how some of my fellow engineers have taken to putting up low effort PRs with errors, as well as unreasonably long design docs. My entire company seems to have bought into the whole "AI-first company" thing without actually validating if the outputs are worth the squeeze. Maybe sometimes they are, but I get a sense that the path of least resistance tends toward accepting lower quality code and communication.
I have also observed that on my team, more than half of the people are either currently on immigrant visas or were previously on immigrant visas. Just to be absolutely clear—these people are great, and I don't fault them or hold any ill will for them having coming here to work.
At the same time, it seems that most hiring is done at the mid and senior level. If we only hire senior talent and rely on immigrant visa labor to fill these ranks, where exactly is each subsequent generation of seniors supposed to come from? I feel there should be some requirements in place to ensure that companies aren't perpetuating this shortage by hiring very few domestic workers at the entry level.