Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
noashavit
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
31.
▲
by
noashavit
5mo ago
Gemma4 is a huge improvement and it's fast. Qwen 3.5 really slows down my machine though. LMK if there is a better model to use for the code assist aspect- performance wise
32.
▲
by
noashavit
5mo ago
Relying on external APIs network failure points and unavoidable latency from the round trips. There is also the AI API rate limits that come into play. We might find that for critical workflows, local compute is the only reliable architectu
33.
▲
by
noashavit
5mo ago
The race for unstructured data continues. It feels like everyone is trying to crack unstructured data extraction with the underlying goal of ultimately using AI to classify and tag insights from unstructured data to create a structured data
34.
▲
Claude Code auto daily /weekly recap notes
(github.com)
3 points
by
noashavit
5mo ago
|
1 comments
35.
▲
by
noashavit
5mo ago
What you built, summarized for you.
36.
▲
by
noashavit
5mo ago
This looks helpful. Context is the main issue agents face. How does this fix issues with messy data though? Like in the real world when you have 2 reports for the same metric with different results. Will the agent have enough context to pro
37.
▲
by
noashavit
5mo ago
People in SF need this. Too many cracked open Macs running agents have been spotted outside public bathrooms haha ;-)
38.
▲
by
noashavit
5mo ago
Looks interesting! Your demo vid in the README didn’t load for me btw.
39.
▲
by
noashavit
5mo ago
I cannot agree with this more. This is a turning point for many. Opportunity is the name of the game if we just view it that way. "somewhere in your org, there are ~five people who are going to deliver you 100x the amount of value you
40.
▲
There are only two paths left for software
(a16z.news)
6 points
by
noashavit
5mo ago
|
2 comments
41.
▲
by
noashavit
5mo ago
I would do 1 and 3 in tandem until you have confidence in the agent’s output across different use cases (personas, channels). Start on a small limited scope. It should be a something you can do in your sleep with data you know and understan
42.
▲
by
noashavit
5mo ago
It’s not just cost per seat. It’s lock in, eroding skills, latencies. I worry about this a lot. There are companies that rely on Claude or Cursor in a way that is not easy to rip out, even if rates 10x.
43.
▲
by
noashavit
5mo ago
How is this different from using local models with Ollama?
44.
▲
by
noashavit
5mo ago
Claude academy has some courses for free and couple certifications too. Otherwise, I found the best way for me to learn is by doing. So I just use oss models through ollama as part of my workflow to keep costs in check. Local models on cons
45.
▲
by
noashavit
5mo ago
I just hired an IC and heard horror stories from candidates about ghosting and code tests for non-devs. Also recent mass layoffs in tech have flooded the market with high quality talent. Feels like a “sellers market”
46.
▲
by
noashavit
5mo ago
You’re not alone and I really hope this isn’t the future of work. It’s unsustainable to push out code you dont understand. It’s one thing to prototype, or build internal tools, but this cannot scale to commercial offerings (for much longer)
47.
▲
by
noashavit
5mo ago
An architecture where compute grows linearly with context length seems dangerous. It can get very expensive as context grows and performance degrades
48.
▲
by
noashavit
5mo ago
Agent-native CLIs will need to handle state, stitch together conversation history across sessions, and execute multi-step workflows. I
49.
▲
by
noashavit
5mo ago
Perimeter defense is outdated. AI changes the attack surface from network edges to the data pipeline itself. We need to securing the prompt, the model, and the data.
50.
▲
by
noashavit
5mo ago
Add a downvote option!
51.
▲
by
noashavit
5mo ago
100% Agents need reliable state management, conditional logic, and structured execution paths. Prompt engineering is a surface layer solution to a deeper problem
52.
▲
by
noashavit
5mo ago
In real communities bots gets exposed
53.
▲
by
noashavit
5mo ago
Gemma4:e4b is a huge upgrade
54.
▲
by
noashavit
5mo ago
I think there is a massive divide in the market between large enterprises and smaller org. The large enterprises are their typically laggard self. Prioritizing governance over innovation. Everyone else, at least in tech or tech adjacent, is
55.
▲
by
noashavit
5mo ago
I feel for Gen Z. If it’s hard for those with years of experience, judgment and taste how can you even get into the game?
56.
▲
by
noashavit
5mo ago
If this is repeatable and holds true across testing groups and practitioners that would be amazing! Doctors could finally spend time with patients rather than rushing to probe, document, test and diagnose. They are so pressed to maximize th
57.
▲
by
noashavit
5mo ago
Why are we still discussing which model is “the best”. The model is just one small part of what you need. Think agentic harness, data governance, AI guardrails, machine access controls, etc
58.
▲
by
noashavit
5mo ago
I feel like build vs buy is the conversation now. I’m not a developer but I’ve built agents I use daily. When most people can vibe code their way to a custom app, value will most likely hinge on support and other “services”. Just my 2 cents
59.
▲
by
noashavit
5mo ago
I built a search intelligence tool with AI and vibes. The vibes ran out in 30 minutes. Here’s what happened. It started as a Claude artifact. Hardcoded queries for topics I track closely, auto-refreshing regularly. It worked, but lacked fl
60.
▲
Agentic AI Security
(straiker.ai)
3 points
by
noashavit
5mo ago
|
1 comments
More ›