frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
367•klaussilveira•4h ago•76 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
735•xnx•10h ago•451 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
127•isitcontent•4h ago•13 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
103•dmpetrov•5h ago•48 comments

A century of hair samples proves leaded gas ban worked

https://arstechnica.com/science/2026/02/a-century-of-hair-samples-proves-leaded-gas-ban-worked/
46•jnord•3d ago•3 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
230•vecti•6h ago•108 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
17•quibono•4d ago•0 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
300•aktau•11h ago•148 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
300•ostacke•10h ago•80 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
151•eljojo•7h ago•116 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
370•todsacerdoti•12h ago•214 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
41•phreda4•4h ago•7 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
298•lstoll•11h ago•222 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
98•vmatsiiako•9h ago•32 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
164•i5heu•7h ago•118 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
134•limoce•3d ago•75 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
221•surprisetalk•3d ago•29 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
32•rescrv•12h ago•14 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
948•cdrnsf•14h ago•409 comments

The Oklahoma Architect Who Turned Kitsch into Art

https://www.bloomberg.com/news/features/2026-01-31/oklahoma-architect-bruce-goff-s-wild-home-desi...
15•MarlonPro•3d ago•2 comments

I'm going to cure my girlfriend's brain tumor

https://andrewjrod.substack.com/p/im-going-to-cure-my-girlfriends-brain
21•ray__•1h ago•3 comments

Claude Composer

https://www.josh.ing/blog/claude-composer
89•coloneltcb•2d ago•65 comments

Show HN: Smooth CLI – Token-efficient browser for AI agents

https://docs.smooth.sh/cli/overview
76•antves•1d ago•56 comments

Evaluating and mitigating the growing risk of LLM-discovered 0-days

https://red.anthropic.com/2026/zero-days/
31•lebovic•1d ago•10 comments

Show HN: Slack CLI for Agents

https://github.com/stablyai/agent-slack
36•nwparker•1d ago•7 comments

How virtual textures work

https://www.shlom.dev/articles/how-virtual-textures-really-work/
22•betamark•11h ago•20 comments

The Beauty of Slag

https://mag.uchicago.edu/science-medicine/beauty-slag
26•sohkamyung•3d ago•3 comments

Evolution of car door handles over the decades

https://newatlas.com/automotive/evolution-car-door-handle/
37•andsoitis•3d ago•59 comments

Planetary Roller Screws

https://www.humanityslastmachine.com/#planetary-roller-screws
33•everlier•3d ago•6 comments

Masked namespace vulnerability in Temporal

https://depthfirst.com/post/the-masked-namespace-vulnerability-in-temporal-cve-2025-14986
29•bmit•6h ago•3 comments
Open in hackernews

The Secrets We Keep

https://blog.bl00cyb.org/2025/07/the-secrets-we-keep/
31•luu•6mo ago

Comments

juliusdavies•6mo ago
Very neat variation on the “I’m currently looking for work” post.
amelius•6mo ago
If you're not allowed to even publish your resume or have a LinkedIn account, then quitting and writing such a post must be a great relief.
Deeksha676•6mo ago
“A lot of what I worked on I can’t talk about. And I will continue to not talk about until they ship. That was the problem.” While I understand why these measures are in place at apple, the resulting effect is the siloing of information and a lack of idea exchange, or even communication which leads to many problems further down the road. It’s hard to build great things when you can’t even talk to the people working on pieces adjacent to yours.
JKCalhoun•6mo ago
Agree. And it wasn't like that at Apple in 1995 when I started. Steve Jobs came back soon after though and so did secrecy. (I'm talking specifically about internal secrecy.)

Would the iPhone have been as big a surprise if all of Apple knew what was going down? Probably not — it probably would have leaked, and leaked profusely.

I'll leave it to others to determine if leaks would have been a bad thing. I mean what we were told from above is: Apple gets a lot of free press from the surprise part of "surprise and delight". When Apple was not the behemoth we know today the free press was probably a powerful thing.

Regardless, as you point out, it's hard to imagine the iPhone would have suffered if more eyeballs and expertise had been able to play with it, weigh in on its shortcomings before it shipped.

I was just a programmer though, not a director. They probably knew what they were doing. I'm just pointing out that there were consequences.

I'll relay this: likely most readers here remember the failed roll-out of Apple Maps. At that point though in the iPhone's lifespan many of those internal at Apple, even those not among the chosen ones, had access to the beta builds. And I will say that there were plenty of people that called out the Maps deficiencies and filed Radars (bug reports) about them before it shipped. Maps shipped anyway. (And when the blowback came Apple apologized and I feel a scapegoat was sought. I'll leave it at that though.)

When Apple products were still in their top-secrecy mode though, many of those engineers not in-the-know had pretty low company morale. You were not "special" if you were out of the loop. Additionally it seemed financial benefits/bonuses flowed primarily to the inner-circle. That, I suppose, was also a Jobs thing.

greatgib•6mo ago
A lit bit ridiculous if you want my opinion. Nothing prevents you to speak about your work, especially with your own family without being too specific.

It's not like working on an atomic bomb algorithm for months...

amelius•6mo ago
Yes, it is ridiculous. If you cannot speak about your work, then why would I buy it? I'm not into buying "magical" IT equipment that I cannot understand and maybe if I'm lucky can ask questions about. Apple is sending me completely the wrong signals, the dissonance couldn't be worse.
greatgib•6mo ago
I agree with you on this but what I meant was more in the sense that even if not allowed to disclose the secrets of the thing you are working on, I'm quite sure that you still have plenty to talk about it with your family.

If you don't, it is just because you are your own jail, a lot wider than what your work contract can enforce.