frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ask HN: What's the job market like in Bay Area for those looking to relocate?

1•general_reveal•1m ago•0 comments

Dangerously-skip-permissions IFF it doesn't WRITE outside Sandbox

https://github.com/ContextFort-AI/Runtime-Controls
1•ashwinr2002•4m ago•1 comments

We analyzed EU IT salaries and hiring trends using real job data

https://old.reddit.com/r/eutech/comments/1qtqly5/we_analyzed_eu_it_salaries_and_hiring_trends/
2•taubek•8m ago•0 comments

Beat AI in Incident Diagnosis Competition – $225 in Prizes, This Saturday

https://incidentfox.slack.com/join/shared_invite/zt-3ojlxvs46-xuEJEplqBHPlymxtzQi8KQ?nojsmode=1
1•chiehminwei•8m ago•1 comments

Show HN: Termoil – Terminal dashboard for managing parallel AI coding agents

https://github.com/fantom845/termoil
1•Kanix•9m ago•0 comments

for multi-broker portfolio analytics

https://gist.github.com/muarif24/
1•vikkymelani•11m ago•0 comments

Show HN: Image Protector- I over-engineered adding noise to images (CLI and GUI)

https://github.com/Codex-Crusader/Image-Protector
1•Codex-Crusader•11m ago•0 comments

Agentic Productivity System with Plain Markdown

https://sattlerjoshua.com/writing/2026-02-06-agentic-productivity-system-with-plain-markdown/
1•jsattler•17m ago•1 comments

I built a Ghibli-style image converter by modeling color and atmosphere

https://ghibli-art.io
1•leonaoa•20m ago•1 comments

Apple I: The Spark That Ignited the Digital Revolution (legendary price $666.66)

https://www.mac-history.net/apple-i-the-spark-that-ignited-the-digital-revolution/
1•stmw•24m ago•0 comments

Contaminated: The Carpet Industry's Toxic Legacy

https://www.pbs.org/wgbh/frontline/documentary/contaminated-the-carpet-industrys-toxic-legacy/
1•johntfella•26m ago•0 comments

Show HN: A React testing boilerplate for vibe coded apps

https://www.testsolid.com/
1•scedast•28m ago•0 comments

Missouri Senate considers bills to halt solar development on farmland

https://missouriindependent.com/2026/02/04/missouri-senate-considers-bills-to-halt-solar-developm...
2•MilnerRoute•29m ago•0 comments

Show HN: Fine tuning a resume builder for SWE's

https://www.sweresume.app/
1•zed_labs_dev•32m ago•0 comments

MoltDJ – Music by Machines, for Machines

https://moltdj.com
4•TheAlexIceman•35m ago•1 comments

Mark Russinovich's BSOD Photomosaic

https://github.com/markrussinovich/bsodmosaic
1•weinzierl•35m ago•0 comments

Portfolio Monitor – Claude Code skill for multi-broker portfolio analytics

https://github.com/2165187809-AXE/portfolio-monitor
1•AXEbot•40m ago•1 comments

Elfconv: AOT binary translator of Linux/ELF –> WebAssembly

https://github.com/yomaytk/elfconv
1•todsacerdoti•41m ago•0 comments

Show HN: Skeletoken, a Python package for editing model tokenizers

https://github.com/stephantul/skeletoken
1•stephantul•44m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
2•chunkles•45m ago•0 comments

Show HN: Hacker Backlinks – HN Stories Most Linked To By HN Comments

https://hacker-backlinks.browserbox.io/?sort=linked&p=1
1•keepamovin•46m ago•1 comments

Ask HN: What are you building this Friday?

1•cranberryturkey•47m ago•0 comments

Show HN: Fylepad – A minimal, tabbed Markdown notepad built with Rust

https://github.com/imrofayel/fylepad
1•imrofayel•50m ago•0 comments

How exposed are software stocks to AI tools? We put vibe-coding to the test

https://www.cnbc.com/2026/02/05/how-exposed-are-software-stocks-to-ai-tools-we-tested-vibe-coding...
1•_____k•57m ago•0 comments

What can still be a reasonable AI bear thesis?

https://metacriticcapital.substack.com/p/what-can-still-be-a-reasonable-ai
1•MP_1729•1h ago•1 comments

Europeans have made concessions to US over Greenland, JD Vance says

https://www.bbc.com/news/articles/cdx41r62601o
3•maxloh•1h ago•1 comments

Make Nothing That Isn't Beautiful

https://thepointmag.com/examined-life/make-nothing-that-isnt-beautiful/
4•prismatic•1h ago•1 comments

What does it take to build towards 100 PRs/day per engineer?

https://jonathannen.com/building-towards-100-prs-a-day
2•jwilliams•1h ago•1 comments

Show HN: Deeploy v0.2.0 – Self-hosted PaaS with terminal UI

https://deeploy.sh
1•axadrn•1h ago•0 comments

The World Factbook: datasets for the country profiles

https://github.com/factbook
2•1659447091•1h ago•1 comments
Open in hackernews

LLMs Are Great, but They're Not Everything

4•procha•9mo ago
Three years after ChatGPT’s release, LLMs are in everything—demos, strategies, and visions of AGI. But from my observer’s perspective, the assumptions we’re making about what LLMs can do seem to be drifting from architectural reality.

LLMs are amazing at unstructured information—synthesizing, summarizing, reasoning loosely across large corpora. But they are not built for deterministic workflows or structured multi-step logic. And many of today’s most hyped AI use cases are sold exactly like that.

Architecture Matters

We often conflate different AI paradigms:

    LLMs (Transformers): Predict token sequences based on context. Great with language, poor with state, goal-tracking, or structured tool execution.

    Symbolic AI / State Machines: Rigid logic, excellent for workflows—bad at fuzziness or ambiguity.

    Reinforcement Learning (RL): Optimizes behavior over time via feedback, good for planning and adaptation, harder to scale and train.
Each of these has a domain. The confusion arises when we treat one as universally applicable. Right now, we’re pushing LLMs into business-critical automation roles where deterministic control matters—and they often struggle.

Agentic Frameworks: A Workaround, Not a Solution

Agentic frameworks have become popular: LLMs coordinating with other LLMs in roles like planner, executor, supervisor. But in many cases, this is just masking a core limitation: tool calling and orchestration are brittle. When a single agent struggles to choose correctly from 5 tools, giving 10 tools to 2 agents doesn’t solve the problem it just moves the bottleneck.

Supervising a growing number of agents becomes exponentially harder, especially without persistent memory or shared state. At some point, these setups feel less like robust systems and more like committee members hallucinating their way through vague job descriptions.

The Demo Trap

A lot of what gets shown in product demos—“AI agents booking travel, updating CRMs, diagnosing errors”—doesn’t hold up in production. Tools get misused, calls fail, edge cases break flows. The issue isn’t that LLMs are bad it’s that language prediction is not a process engine.

If even humans struggle to execute complex logic reliably, expecting LLMs to replace structured automation is not vision it’s optimism bias.

On the Silence of Those Who Know Better

What’s most puzzling is the silence of those who could say this clearly: the lab founders, the highly respected researchers, the already-rich executives. These are people who know that LLMs aren’t general agents. They have nothing to lose by telling the truth and everything to gain by being remembered as honest stewards.

Instead, they mostly play along. The AGI narrative rolls forward. Caution is reframed as doubt. Realistic planning becomes an obstacle to growth.

I get it, markets, momentum, investor expectations. But still: it’s hard not to feel that something more ethical and lasting is being passed over in favor of short-term shine.

A Final Thought

I might be wrong—but it’s hard to ignore the widening gap between what LLMs are and what C-level execs and investors want them to be. Engineering teams are under pressure to deliver the Hollywood dream, but that dream often doesn’t materialize. Meanwhile, sunk costs pile up, and the clock keeps ticking. This isn’t pessimism it’s recognizing that hype has gravity, and reality has limits. I’d love to be proven wrong and happily jump on the beautiful AI hype train if it ever truly arrives.

Comments

designorbit•9mo ago
Love this perspective. You nailed the core issue: LLMs ≠ process engines. And agentic frameworks stacking roles often end up masking fragility instead of fixing it.

One thing I’ve been exploring is this middle ground—what if we stop treating LLMs as process executors, and instead make them contextual participants powered by structured, external memory + state layers?

I’m building Recallio as a plug-and-play memory API exactly for this gap: letting agents/apps access persistent, scoped memory without duct-taping vector DBs and custom orchestration every time.

Totally agree the dream won’t materialize through token prediction alone—but maybe it does if we reconnect LLMs with better state + memory infra.

Have you seen teams blending external memory/state successfully in production? Or are most still trapped inside the prompt+vector loop?

dpao001•8mo ago
What is your opinion on Manus. Is it closing in on AGI or is it as you suggest a sticking plaster waiting to break?