frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Why a 175-Year-Old Glassmaker Is Suddenly an AI Superstar

https://www.wsj.com/tech/corning-fiber-optics-ai-e045ba3b
1•Brajeshwar•11s ago•0 comments

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•2m ago•0 comments

Japanese rice is the most expensive in the world

https://www.cnn.com/2026/02/07/travel/this-is-the-worlds-most-expensive-rice-but-what-does-it-tas...
1•mooreds•2m ago•0 comments

These White-Collar Workers Actually Made the Switch to a Trade

https://www.wsj.com/lifestyle/careers/white-collar-mid-career-trades-caca4b5f
1•impish9208•2m ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•3m ago•0 comments

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

https://new.knife.day/blog/reddit-steel-sentiment-analysis
1•p-s-v•3m ago•0 comments

Federated Credential Management (FedCM)

https://ciamweekly.substack.com/p/federated-credential-management-fedcm
1•mooreds•3m ago•0 comments

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

https://app.writtte.com/read/kZ8Kj6R
1•lasgawe•4m ago•1 comments

The Story of Heroku (2022)

https://leerob.com/heroku
1•tosh•4m ago•0 comments

Obey the Testing Goat

https://www.obeythetestinggoat.com/
1•mkl95•4m ago•0 comments

Claude Opus 4.6 extends LLM pareto frontier

https://michaelshi.me/pareto/
1•mikeshi42•5m ago•0 comments

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•8m ago•0 comments

Google Translate apparently vulnerable to prompt injection

https://www.lesswrong.com/posts/tAh2keDNEEHMXvLvz/prompt-injection-in-google-translate-reveals-ba...
1•julkali•8m ago•0 comments

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

https://bsky.app/profile/fullmoon.id/post/3meadfaulhk2s
1•todsacerdoti•9m ago•0 comments

Software development is undergoing a Renaissance in front of our eyes

https://twitter.com/gdb/status/2019566641491963946
1•tosh•9m ago•0 comments

Can you beat ensloppification? I made a quiz for Wikipedia's Signs of AI Writing

https://tryward.app/aiquiz
1•bennydog224•11m ago•1 comments

Spec-Driven Design with Kiro: Lessons from Seddle

https://medium.com/@dustin_44710/spec-driven-design-with-kiro-lessons-from-seddle-9320ef18a61f
1•nslog•11m ago•0 comments

Agents need good developer experience too

https://modal.com/blog/agents-devex
1•birdculture•12m ago•0 comments

The Dark Factory

https://twitter.com/i/status/2020161285376082326
1•Ozzie_osman•12m ago•0 comments

Free data transfer out to internet when moving out of AWS (2024)

https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-internet-when-moving-out-of-aws/
1•tosh•13m ago•0 comments

Interop 2025: A Year of Convergence

https://webkit.org/blog/17808/interop-2025-review/
1•alwillis•14m ago•0 comments

Prejudice Against Leprosy

https://text.npr.org/g-s1-108321
1•hi41•15m ago•0 comments

Slint: Cross Platform UI Library

https://slint.dev/
1•Palmik•19m ago•0 comments

AI and Education: Generative AI and the Future of Critical Thinking

https://www.youtube.com/watch?v=k7PvscqGD24
1•nyc111•19m ago•0 comments

Maple Mono: Smooth your coding flow

https://font.subf.dev/en/
1•signa11•20m ago•0 comments

Moltbook isn't real but it can still hurt you

https://12gramsofcarbon.com/p/tech-things-moltbook-isnt-real-but
1•theahura•24m ago•0 comments

Take Back the Em Dash–and Your Voice

https://spin.atomicobject.com/take-back-em-dash/
1•ingve•25m ago•0 comments

Show HN: 289x speedup over MLP using Spectral Graphs

https://zenodo.org/login/?next=%2Fme%2Fuploads%3Fq%3D%26f%3Dshared_with_me%25253Afalse%26l%3Dlist...
1•andrespi•25m ago•0 comments

Teaching Mathematics

https://www.karlin.mff.cuni.cz/~spurny/doc/articles/arnold.htm
2•samuel246•28m ago•0 comments

3D Printed Microfluidic Multiplexing [video]

https://www.youtube.com/watch?v=VZ2ZcOzLnGg
2•downboots•28m ago•0 comments
Open in hackernews

Ask HN: If AI is intelligent, why do we still need programming?

6•alwinaugustin•9mo ago
There's a lot of talk about "AI code generation," but if AI were truly intelligent—able to understand and solve problems autonomously—would we still need programming at all?

Programming is how we translate understanding into instructions. If AI had intelligence, wouldn’t it just solve problems directly, without needing prompts or code?

Current tools still depend on human guidance and structured inputs. So is this really “intelligence,” or are we anthropomorphizing what’s essentially pattern-based automation?

Should we start calling it what it is—statistical code synthesis—rather than framing it as "intelligent" code generation?

Comments

01-_-•9mo ago
because AI isn't smart enough to deal with the security part and the maintenance of the code.
uejfiweun•9mo ago
You're absolutely right. It's not intelligence in the way we have traditionally understood it. It's a pattern matching system that uses massive scale to handle a vast number of cases, and it's very useful, but it routinely fails on even basic tasks. The labs are just playing whack a mole with the failure cases because fundamentally the architecture doesn't have common sense in the same way we do. Your moniker of "statistical code synthesis" is probably more accurate but this is a capex intensive technology and you're gonna get a lot more investor interest by playing to people's imagination with terms like "intelligence" or "superintelligence".
gloomyguy•9mo ago
“AI” is fine as a shorthand—but the moment we treat it like a synonym for "thinking" or "understanding," we risk confusing metaphor with mechanism. Using clearer terms may help ground expectations and promote responsible usage.
austin-cheney•9mo ago
1. The current trend in AI is LLMs, which is only intelligent at interpreting human wording. LLMs are very good at searching the web and correlating answers to questions, but not much else.

2. Most human software developers cannot architect or write original applications on their own. We are extremely far away from software doing any of that, especially from doing it better than the few humans who can do it.

3. Most human developers cannot measure things. I know we are all taught to use rulers as little children in school, nonetheless most developers cannot gather data about software. Unexpectedly, AI is even worse at this than humans, which is an astonishingly critical failure.

4. LLMs hallucinate at a current rate of at least 1 in 20 inquiries and as early as 1 in 6. That is a tremendous amount of risk to accept. Humans that make mistakes at that frequency, without regard for the harms, tend to go to jail for fraud.

In summary, AI is currently really good at writing code that is only one or two layers more abstract than copy/paste. That is actually enough to entirely replace a great many, possibly most, developers. Business is not willing to take that step, however, because the low trust in AI and high failure rate introduce more costs than value returned at higher risk.

A safer strategy is to only select human developers more capable of writing original software solutions and/or training humans to do so. Businesses have historically been unwilling to do this due to their inability to account for bias and retain employees. Because of this historic inability to commit to a human/code selection solution it is likewise safe to assume it will not commit on a AI solution so frequently prone to critical failure.