frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Show HN: I spent 6 years building a ridiculous wooden pixel display

https://benholmen.com/blog/kilopixel/
644•benholmen•7h ago•95 comments

Is It FOSS?

https://isitreallyfoss.com/
68•exiguus•2h ago•12 comments

Qwen-Image: Crafting with native text rendering

https://qwenlm.github.io/blog/qwen-image/
250•meetpateltech•7h ago•75 comments

NASA's Curiosity picks up new skills

https://www.jpl.nasa.gov/news/marking-13-years-on-mars-nasas-curiosity-picks-up-new-skills/
78•Bluestein•4h ago•25 comments

How we made JSON.stringify more than twice as fast

https://v8.dev/blog/json-stringify
133•emschwartz•9h ago•25 comments

EconTeen – Financial Literacy Lessons and Tools for Teens

https://econteen.com/
5•Chrisjackson4•26m ago•1 comments

What Does One Billion Dollars Look Like?

https://whatdoesonebilliondollarslooklike.website/
22•alexrustic•2h ago•17 comments

Indian Sign Painting: A typeface designer's take on the craft

https://bl.ag/indian-sign-painting-a-typeface-designers-take-on-the-craft/
101•detaro•2d ago•16 comments

Content-Aware Spaced Repetition

https://www.giacomoran.com/blog/content-aware-sr/
61•ran3000•4h ago•15 comments

Job-seekers are dodging AI interviewers

https://fortune.com/2025/08/03/ai-interviewers-job-seekers-unemployment-hiring-hr-teams/
474•robtherobber•15h ago•731 comments

Show HN: I've been building an ERP for manufacturing for the last 3 years

https://github.com/crbnos/carbon
5•barbinbrad•1h ago•0 comments

Hiroshima (1946)

https://www.newyorker.com/magazine/1946/08/31/hiroshima
25•pseudolus•2d ago•17 comments

OpenIPC: Open IP Camera Firmware

https://openipc.org/à
181•zakki•3d ago•105 comments

Cellular Starlink expands to support IoT devices

https://me.pcmag.com/en/networking/31452/spacexs-cellular-starlink-expands-to-support-iot-devices
57•teleforce•3d ago•38 comments

Once a death sentence, cardiac amyloidosis is finally treatable

https://www.nytimes.com/2025/08/04/well/cardiac-amyloidosis.html
75•elektor•3h ago•2 comments

DrawAFish.com Postmortem

https://aldenhallak.com/blog/posts/draw-a-fish-postmortem.html
221•hallak•11h ago•52 comments

How we built Bluey’s world

https://www.itsnicethat.com/features/how-we-built-bluey-s-world-cartoon-background-scenery-art-director-catriona-drummond-animation-090725
299•skrebbel•3d ago•137 comments

Thingino: Open-Source Firmware for IP Cameras

https://thingino.com/
5•zakki•1h ago•1 comments

Perplexity is using stealth, undeclared crawlers to evade no-crawl directives

https://blog.cloudflare.com/perplexity-is-using-stealth-undeclared-crawlers-to-evade-website-no-crawl-directives/
903•rrampage•9h ago•525 comments

AWS European Sovereign Cloud to be operated by EU citizens

https://www.aboutamazon.eu/news/aws/aws-european-sovereign-cloud-to-be-operated-by-eu-citizens
48•pulisse•2h ago•41 comments

A deep dive into Rust and C memory interoperability

https://notashes.me/blog/part-1-memory-management/
127•hyperbrainer•8h ago•58 comments

What Can a Cell Remember?

https://www.quantamagazine.org/what-can-a-cell-remember-20250730/
42•chapulin•4d ago•4 comments

Customizing tmux

https://evgeniipendragon.com/posts/customizing-tmux-and-making-it-less-dreadful/
75•EPendragon•7h ago•71 comments

My Ideal Array Language

https://www.ashermancinelli.com/csblog/2025-7-20-Ideal-Array-Language.html
109•bobajeff•10h ago•50 comments

Show HN: Sidequest.js – Background jobs for Node.js using your database

https://docs.sidequestjs.com/quick-start
42•merencia•7h ago•11 comments

Read your code

https://etsd.tech/posts/rtfc/
156•noeclement•10h ago•90 comments

Century-old stone “tsunami stones” dot Japan's coastline (2015)

https://www.smithsonianmag.com/smart-news/century-old-warnings-against-tsunamis-dot-japans-coastline-180956448/
124•deegles•10h ago•43 comments

Objects should shut up

https://dustri.org/b/objects-should-shut-the-fuck-up.html
263•gm678•9h ago•204 comments

Show HN: Tiny logic and number games I built for my kids

https://quizmathgenius.com/
66•min2bro•8h ago•25 comments

Is the interstellar object 3I/ATLAS alien technology? [pdf]

https://lweb.cfa.harvard.edu/~loeb/HCL25.pdf
72•jackbravo•10h ago•94 comments
Open in hackernews

Why Greptile just does code reviews and doesn't also generate code

https://www.greptile.com/blog/auditor
37•dakshgupta•8h ago

Comments

o11c•5h ago
This is advertising for an AI product. Slightly more interesting background story than most articles doing so, but still an ad for a product that probably won't actually work.
mooreds•3h ago
I have no direct experience with Greptile, but asked about AI code review assistants on a mailing list of engineering leaders I'm on. Several folks suggested greptile.

So, consider this hearsay that it works.

fastest963•14m ago
My employer uses greptile and I'm pretty happy with it. Sometimes it can be a bit overzealous but more often than not it catches real issues and gives the author a chance to reply or fix them before another human reviews the PR.
fragmede•1m ago
Calling it an ad is just lazy dismissal. Everybody is selling something. If you’re more focused on purity tests than evaluating whether the idea actually works, you’re not critiquing, you’re gatekeeping.
vouwfietsman•5h ago
I was so hoping that this would not be about AI, and actually talk about how we need to do better as an industry and start using objective measures of software quality backed by government standards.

Nope, its about AI code reviewing AI, and how that's a good thing.

Its like everyone suddenly forgot the old adage: "code is a liability".

"We write code twice as fast!" just means "we create liability twice as fast!". It's not a good thing, at all.

dang•3h ago
I had thought that putting quotes around the phrase "independent auditor" above would have prevented this sort of misunderstanding, but clearly not, so I've changed the title to something more straightforward now.

(Submitted title was "Software needs an independent auditor")

literalAardvark•2h ago
Improving automated code review does improve software, so idk why you're grinding that axe in this particular thread.
brynary•2h ago
This rings similar to a recent post that was on the front page about red team vs. blue team.

Before running LLM-generated code through yet more LLMs, you can run it through traditional static analysis (linters, SAST, auto-formatters). They aren’t flashy but they produce the same results 100% of the time.

Consistency is critical if you want to pass/fail a build on the results. Nobody wants a flaky code reviewer robot, just like flaky tests are the worst.

I imagine code review will evolve into a three tier pyramid:

1. Static analysis (instant, consistent) — e.g using Qlty CLI (https://github.com/qltysh/qlty) as a Claude Code or Git hook

2. LLMs — Has the advantage of being able to catch semantic issues

3. Human

We make sure commits pass each level in succession before moving on to the next.

dakshgupta•2h ago
Reading that post sent me down the path to this one. This stack order makes total sense, although in practice it's possible 1-2 merge into a single product with two distinct steps.

The 3. is interesting too - my suspicion is that ~70% of PRs are too minor to need human review as the models get better, but the top 30% will because there will be opinion on what is and isn't the right way to do that complex change.