frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The Early Days of American Imperialism

https://www.theatlantic.com/newsletters/2026/01/old-american-imperialism-trump-power-abroad/685558/
1•petethomas•2m ago•0 comments

I6P: An IPv6-only P2P transport layer in Go (QUIC and ratchet)

https://github.com/TheusHen/I6P
1•TheusHen•6m ago•1 comments

Plaza.one

https://plaza.one/
1•indigodaddy•7m ago•0 comments

Show HN: ApiTap – Stream APIs to any Data Warehouse with SQL (Rust + DataFusion)

https://apitap.dev/
1•kotekaman•7m ago•0 comments

Slopware.wtf – Roasting AI-Generated Garbage Software

https://slopware.wtf/
1•airhangerf15•7m ago•0 comments

Cchistory: Track Claude Code system prompts over time

https://cchistory.mariozechner.at/
1•handfuloflight•8m ago•0 comments

Show HN: I built an AI that calls you until you wake up

https://wakecall.online/
1•rahma_tm•18m ago•1 comments

SHP: 700x faster context recall by treating memory as network

https://github.com/silentnoisehun/Silent-Hope-Protocol
1•Hope_Genom•20m ago•1 comments

A Year of Typing: My NumPy Fellowship Retrospective

https://blog.scientific-python.org/numpy/fellowship-program-2025-retrospective/
1•todsacerdoti•21m ago•0 comments

Anthropic bans use of API in OpenCode CLI tool

https://github.com/anomalyco/opencode/issues/7410
4•sergiotapia•22m ago•0 comments

We just open sourced the code-simplifier agent we use on the Claude Code team

https://twitter.com/bcherny/status/2009450715081789767
1•cleanexit0•22m ago•0 comments

SFC vs. VIZIO: who can enforce the GPL?

https://lwn.net/SubscriberLink/1052734/5903e175673caeef/
2•pabs3•24m ago•0 comments

GPLv2 and Installation Requirements

https://lwn.net/SubscriberLink/1052842/52c45fb8bcc3fade/
1•pabs3•25m ago•0 comments

Show HN: Open-source multimodal AI that runs in the browser

https://johnjboren.github.io/ai-assistant.html
1•EschatonCometh•26m ago•0 comments

Show HN: Layoffstoday – Open database tracking for 10k Companies

https://layoffstoday.io/
1•doremon0902•27m ago•0 comments

Pituffik Space Base

https://en.wikipedia.org/wiki/Pituffik_Space_Base
2•CGMthrowaway•28m ago•0 comments

From old English to modern American English in one monologue

https://www.youtube.com/watch?v=842OX2_vCic
1•gk1•28m ago•0 comments

Financial Hardship Shows Up in Baby Brains

https://nautil.us/how-financial-hardship-shows-up-in-baby-brains-1260476/
1•fleahunter•30m ago•0 comments

Testing 2 open-weight models across coding tasks: GLM 4.7 and MiniMax M2.1

https://blog.kilo.ai/p/open-weight-models-are-getting-serious
1•heymax054•30m ago•0 comments

When AI writes almost all code, what happens to software engineering?

https://newsletter.pragmaticengineer.com/p/when-ai-writes-almost-all-code-what
3•Brajeshwar•34m ago•0 comments

Show HN: A commitment model for usage billing

https://twitter.com/tryflexprice/status/2009226683849773430
1•sudeepsd__•34m ago•0 comments

Trump Lays Out a Vision of Power Restrained Only by 'My Own Morality'

https://www.nytimes.com/2026/01/08/us/politics/trump-interview-power-morality.html
10•Stevvo•35m ago•0 comments

Ask AI via Lightning payments (no accounts, no API keys, no stored history)

https://satsforai.com/
1•LightProx•37m ago•1 comments

The most popular Go dependency is

https://blog.thibaut-rousseau.com/blog/the-most-popular-go-dependency-is/
1•bzGoRust•40m ago•0 comments

Ralph Wiggum Experiment – Can AI meaningfully improve through iterative loops?

https://github.com/UtpalJayNadiger/ralphwiggumexperiment
1•iacguy•41m ago•0 comments

Implementing a web server in a single printf() call (2014)

https://tinyhack.com/2014/03/12/implementing-a-web-server-in-a-single-printf-call/
1•nateb2022•42m ago•1 comments

Kelly Evans: Goodbye, Google

https://www.cnbc.com/2026/01/07/kelly-evans-goodbye-google.html
1•cebert•45m ago•1 comments

Spirit Cave Resilience: How Do We Explain a 10k-Year Continuity

https://www.cambridge.org/core/journals/american-antiquity/article/spirit-cave-resilience-how-do-...
1•1659447091•47m ago•0 comments

Show HN: LSP Skill – IntelliSense for Coding Agents That Works

https://lsp-client.github.io/
1•observerw•54m ago•0 comments

Against the 'METR Graph'

https://arachnemag.substack.com/p/the-metr-graph-is-hot-garbage
1•zygmunt417•54m ago•0 comments
Open in hackernews

Welcome Back to the Office. You Won't Get Anything Done

https://thewalrus.ca/return-to-office-mandates/
12•billybuckwheat•22h ago

Comments

Teknomadix•22h ago
Read David Graeber's BULLSHIT JOBS. You will understand what it's all about.
wormpilled•17h ago
Your job wont be outsourced to mumbai as easily though.
hshdhdhj4444•15h ago
One of my frustrations with a lot of writing is a misuse of resources. For example, this article cites 3 resources to show remote work doesn’t hurt productivity.

Of the 3, the oldest, which is the only one that shows some correlation between industries with more remote work having higher productivity, only covers the period until 2022. We now know that much of the rise in productivity was a mirage that was a result of eliminating jobs that couldn’t be done remotely in the pandemic (think coffee shop barista) which while important, tends to be lower on average on measures of productivity.

The 2nd article that says there was no increase or decrease in productivity supports this idea and adds to it.

> the study finds a slight increase in output per worker in the economy. This growth did not result from employees in more remote-intensive jobs working more productively. Instead, people were better able to sort into roles that were better suited for them, and employment shifted toward sectors with higher output per worker.

So the gains that offset the losses in productivity were not due to improved productivity per worker, but because workers were sorting into jobs better.

Finally, the 3rd article, explicitly says that the research shows WFH hurts productivity and provides several citations to research indicating this. What the 3rd article does highlight is that hybrid work is potentially as productive as full time office, and by implication more productive than fully WFH, therefore justifying RTO from a purely productivity perspective, and not requiring explanations such as upper management desire for control.