Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Show HN: Sprocket – A bioinformatics workflow engine in Rust, from laptop to HPC (sprocket.bio)
    —discuss
  2. DraftKings Is Using AI to Supercharge the Harms of Online Behavioral Advertising (eff.org)
    —discuss
  3. A24, Sony, or the New York Times May Soon Swallow Letterboxd (gizmodo.com)
    —discuss
  4. Lessons for Software Developers from Heinlein (2009) (computerworld.com)
    —discuss
  5. How to Own a 3-Year Technical Roadmap (and Get the Time to Execute It) (vikmodi.medium.com)
    —discuss
  6. Blondin's Assignment America (1997) (blondins.com)
    —discuss
  7. The Antitrust Problem with Meta's Settlement with the States (techdirt.com)
    —discuss
  8. The model observes, a table decides: keeping an LLM out of pet triage (tailstory-app.com)
    —discuss
  9. It's called Luxir, it's open source from Yonik Seeley (yonik.com)
    1comments
  10. BizEmpire – Real-time multiplayer economic SIM with double-entry accounting (bizempire.app)
    —discuss
  11. Intel Total Storage Encryption on Panther Lake [video] (youtube.com)
    —discuss
  12. Crisis of the Late Middle Ages (wikipedia.org)
    —discuss
  13. Ask HN: Does a startup need both founder and company X accounts?
    —discuss
  14. Ask HN: Do you cuss at your agent?
    —discuss
  15. Toxic bosses: why do companies protect managers who make working life hell? (theguardian.com)
    —discuss
  16. Show HN: Multi-agent coding feels like pre-GitHub development (github.com/motif-labs)
    —discuss
  17. Laya "System 1" Code Intelligence for AI Agents (github.com/leonardoventurini)
    —discuss
  18. Full iPhone 4 'Antennagate' Q&A Video Surfaces After 16 Years – MacRumors (macrumors.com)
    —discuss
  19. Jamie Beaton might end up the world's most educated person (nytimes.com)
    1comments
  20. Vitvm: Git for VM State (github.com/numinous-technology)
    —discuss
  21. Docker releases cloud sandboxes, enabling safe agentic workloads in the cloud (docker.com)
    —discuss
  22. Gmux: Tmux for GPUs (github.com/numinous-technology)
    —discuss
  23. Platform-Independent SIMD in Go (go.dev)
    —discuss
  24. Protecting our knowledge of human genetic diversity (projecttimestamper.org)
    —discuss
  25. Show HN: Jev-pilot – Jev picks Claude Code's effort, model and skill per prompt (github.com/akramovic1)
    —discuss
  26. Preventive Software Maintenance (poolp.org)
    —discuss
  27. 4% of Sessions, 65% of the Bill: 30 Days of Claude Code Telemetry (promptarmor.com)
    —discuss
  28. Back and shoulder surgery is often worse than useless (economist.com)
    —discuss
  29. Software-only quantum tool, it breaks RSA-2048 live (dtec9.com)
    —discuss
  30. Danish Health Minister summoned over secret Wegovy court proceedings (dr.dk)
    1comments

Any nerds out there who've read a lot of research papers?

4 pointsby 3h ago
9 comments
Which are the most memorable abstracts you have read? I know I am a jackass who usually vibecodes my way through assignments but even I don't want to write a cookie-cutter intro for my paper. I wanna write something that stays with the reader. What paper has stuck with you, what made it memorable?
1h agoHN ↗

I'm well into the thousands of research papers read. Understood a fair fraction of them. Couldn't tell you what the abstract was for any. The memorable parts are the ideas and the results within the paper.

Some titles stick. "Attention is all you need". "SSA is functional programming". Plus more people see the title than read the abstract. Only one I got to name myself was "Shared Memory Remote Procedure Calls" which I now realise is in exactly the same theme of given the title, you don't need the abstract or the contents.

1h agoHN ↗

Gotta have a look at yours! And I remember the name "Attention is all you need" too!

16m agoHN ↗

Hard to separate the memorability of the abstract from the underlying material.

IMO the most memorable papers contain some unexpected simplification: a complicated problem turns out to reduce to something much simpler [0], perhaps for a counterintuitive reason [1].

So a memorable abstract should advertise that the paper contains some cute little trick. This may not help you actually publish though

[0]: Attack the RLHF problem with a simple classification loss: https://arxiv.org/abs/2305.18290

[1]: Frustratingly Easy Meta-Embeddings: https://arxiv.org/abs/1804.05262