tirumaraiselvan
tirumaraiselvan on Hacker News
> But here’s the catch.
> If human SREs (okay, now we have to use adjectives like human ) only engage with Tier 3 incidents, i.e. the novel, never-before-seen outages, where do they build the intuition to handle them?
How did they do this before AI? I have done a bunch of complex production level debugging and these Tier 3 incidents are always "starting from scratch" never seen before issues. The main "intuition" I built is persistence and verifying/refuting random hypothesis. In other words, I think we can build an intuition for Tier 3 issues only by engaging with Tier 3 issues.
Although, psychologically, some success in T1 and T2 issues is what gives us the confidence to even approach the T3 issues.
Otherwise this question should bother a parent in every generation.
Maybe mass education picked up during industrial revolution because of the immense needs of operating factories but the curriculum has obviously been reformed in every generation.
It may be obvious to conclude that good programmers are good reviewers but I think all variations exist. I wonder how many people don't like their jobs anymore because they don't like reviewing code written by AI.
1. Paper has not been replaced by any tech because its form still has unique use-cases
2. AI is stuck in "chat" form and not all use-cases can be solved with chat.
Hence "AI will never replace paper" ..... well anything can happen really isn't it? 1 and 2 are quite independent statements.
But the real irony is that even the author points that their authentic work is under constant suspicion because "what if this is AI" has prevaded everyone's consciousness.
Artificial intelligence is capitalism's final destination
Open Letter about the Mathathon
Thousands of students are attempting to march to India's parliament
The semantic layer is dead. Long live the wiki
[1]: https://www.reuters.com/technology/openai-tells-investor-not...
``` The teams that succeed don’t just throw SQL schemas at the model. They build:
Business glossaries and term mappings
Query templates with constraints
Validation layers that catch semantic errors before execution ```
Unfortunately, the mixing of fluffy tone and high level ideas is bound to be detested by hands on practitioners.
Ask HN: Is Docker Compose service disrupted?
Seem to getting the following when pulling images via compose (docker compose up --build)failed to solve: ghcr.io/hasura/v3-engine: failed to resolve source metadata for ghcr.io/hasura/v3-engine:latest: error getting credentials - err: signal: killed, out: ``Website seems to suggest there is some "Active incident" but nothing else.
If you want to see the other style of writing in Rushdie, I can suggest Shalimar The Clown or The Ground Beneath Her Feet. But these are nowhere near as grand as Midnights Children.
In either category, a fair amount of interest in history helps to enjoy his books.
PromptQL is a programmatic approach to LLM tool composition which has shown remarkable improvement in accuracy (~2x) and repeatability (~4x) when compared to traditional tool calling and chaining approaches.
Fundamentally, PromptQL separates the creation of a query plan from the execution of the query plan. PromptQL uses the LLM to first create a program to compose the different tool calls hence avoiding the challenges with in-context tool chaining like accuracy, repeatability and context limits.
Show HN: PromptQL – Solving Context Size and Accuracy Issues in LLM Tool Calling
BreakTime: Brickbreaker Inside Google Calendar
Fun fact the cover image if this edition was kind of a decoy (perhaps to accentuate the shock): https://www.newyorker.com/magazine/1946/08/31
Comparing Different "SQL over HTTP" APIs
Claude does artifacts using 8 few shot examples
This. Not sure why RAG triggers vector search for everyone. Retrieval Augmented Generation is as generic as it can get.
To me it seems a more risky use-case since you don't have control/observability over what an untrusted user is asking for?