frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

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

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•15s 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•38s 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•38s ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•1m 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•1m ago•0 comments

Federated Credential Management (FedCM)

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

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

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

The Story of Heroku (2022)

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

Obey the Testing Goat

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

Claude Opus 4.6 extends LLM pareto frontier

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

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•6m 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•6m ago•0 comments

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

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

Software development is undergoing a Renaissance in front of our eyes

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

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

https://tryward.app/aiquiz
1•bennydog224•8m 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•8m ago•0 comments

Agents need good developer experience too

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

The Dark Factory

https://twitter.com/i/status/2020161285376082326
1•Ozzie_osman•10m 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•11m ago•0 comments

Interop 2025: A Year of Convergence

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

Prejudice Against Leprosy

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

Slint: Cross Platform UI Library

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

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

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

Maple Mono: Smooth your coding flow

https://font.subf.dev/en/
1•signa11•18m 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•22m ago•0 comments

Take Back the Em Dash–and Your Voice

https://spin.atomicobject.com/take-back-em-dash/
1•ingve•22m 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•23m ago•0 comments

Teaching Mathematics

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

3D Printed Microfluidic Multiplexing [video]

https://www.youtube.com/watch?v=VZ2ZcOzLnGg
2•downboots•26m ago•0 comments

Abstractions Are in the Eye of the Beholder

https://software.rajivprab.com/2019/08/29/abstractions-are-in-the-eye-of-the-beholder/
2•whack•26m ago•0 comments
Open in hackernews

Leprechauns, root causes, and other fairy tales

https://www.tomdalling.com/blog/software-processes/leprechauns-root-causes-and-other-fairy-tails/
29•ingve•6mo ago

Comments

lucianbr•6mo ago
Air accidents investigations somehow seem to result in increased safety, so something can work. First idea that comes to mind is that those reports point out multiple causes usually.
satisfice•6mo ago
This article is itself an example of oversimplifying a complex process.

Five whys and the notion of a single root cause are both weak heuristics— but also almost no one sees them otherwise. People are generally smart, not stupid, and already understand that systems are complex.

Still, it is useful to ask “how did this problem come to be?” and “what can we do to improve our system?” Neither of which require or even encourage oversimplification.

derbOac•6mo ago
> understand that systems are complex.

For what it's worth, this is not my experience. My experience is that there's often an attempt to assign blame to a small component of the system. My sense is it is ultimately to reduce effort or embarrassment, to blame whatever can be "fixed" with less work or indictment of "higher level" components. So the littler or less well-integrated person or more minor policy gets blamed over management or administration, or core operating policies, or culture, because the latter are harder to change or involve more admission of fundamental problems that could cause reputational harm.

It's uncommon in my experience to acknowledge systemic problems or problems with very fundamental policies.

My only criticism of the piece is that sometimes you can identify a root cause, but it's at a very high level of generality and/or involves an error of omission, which is harder to identify than an error of commission. For example, a policy or protocol that isn't present that could be.

satisfice•6mo ago
"There is often an attempt..." is completely compatible with my point. SOME people oversimplify. Other people are merely simplifying. Assigning blame is also a relative matter. Some people might claim that all the blame belongs in one place, while most would admit, under cross-examination, that not ALL belongs in any one place.

Of course blame follows the lines of ideology and self-interest. This is also not indicative of people being stupid and not understanding complexity-- because it's not a problem with understanding. It's a problem of damage control.

It's entirely rational to want to control damage!

Yes, it's uncommon to acknowledge systemic problems. My point is that educating people about such things won't help much, since lack of education is not to blame for this pattern. See what I did there?

JonathanRaines•6mo ago
I think you are right that once the exercise becomes hunting for a scapegoat it's pointless.

However, it can be a way for everyone to understand the system better. The goal should be making each of the dominoes less likely to fall. Doing so can simplify rather than add complexity.