Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Founding Engineer, AI and Full-Stack(bettrlife.ai ↗)
    discuss
  2. Notebook interpolates smoothly between projections of the globe(observablehq.com ↗)
    discuss
  3. Show HN: MP3 to MIDI Lab – Convert MP3/WAV to MIDI in the Browser(mp3tomidilab.com ↗)
    discuss
  4. Elegant Shape of Eiffel Tower Solved Mathematically by CU-Boulder Prof (2005)(colorado.edu ↗)
    discuss
  5. Bytemail – One-time-purchase native email client for macOS (no subscription)(bytemailapp.com ↗)
    discuss
  6. Programming languages hit a decade low on Hacker News(orangecrumbs.com ↗)
    discuss
  7. Curated list of hosting (VPS, GPU, infra, AI)(github.com/dalisoft ↗)
    discuss
  8. How I see software dev in AI era(dhilst.github.io ↗)
    discuss
  9. The End of Upward Mobility(noemamag.com ↗)
    discuss
  10. Divide by Depth for Instant 3D(gabrieloc.com ↗)
    1comments
  11. PC ports of old console games are the new AI vibe coding battleground(pcgamer.com ↗)
    discuss
  12. Detecting and mitigating a multi-stage AiTM phishing and BEC campaign (2023)(microsoft.com ↗)
    discuss
  13. How the incident happened: a play in one act(surfingcomplexity.blog ↗)
    discuss
  14. Show HN: KillSwitch – a programming language designed to be difficult for LLMs(killswitch-lang.org ↗)
    discuss
  15. Escaping Docker's Hypervisor(accomplish.ai ↗)
    1comments
  16. Testing Jev as a validation gate for drug-discovery agents(frederickparsons.substack.com ↗)
    discuss
  17. Jevmetrics – probabilistic metric reduction inside OpenTelemetry(github.com/ishantanu ↗)
    discuss
  18. Solving rubiks cubes "without search"(arxiv.org ↗)
    discuss
  19. Firefox Telemetry Dictionary(telemetry.mozilla.org ↗)
    1comments
  20. Finding Bugs(matklad.github.io ↗)
    discuss
  21. What do you think is the prevalence of this phenomenon in current AI discourse?(wikipedia.org ↗)
    2comments
  22. Economics Nobel Laureates' Letter Supporting the California Billionaire Tax [pdf](gabriel-zucman.eu ↗)
    4comments
  23. Markers to Deter Human Intrusion into Waste Isolation Pilot Plant (1993) [pdf](gwern.net ↗)
    discuss
  24. ZK-JPEG: Zero-Knowledge Image Editing and Compression(iacr.org ↗)
    discuss
  25. Disney+ changes subscriber agreement to allow ads on every plan(dexerto.com ↗)
    1comments
  26. Screens Ubiquitous in Classrooms; Teachers Split on Efficacy(gallup.com ↗)
    discuss
  27. Tiny radio transmitters reveal a hidden survival tactic in birds(theconversation.com ↗)
    discuss
  28. The Working Class Face a 'Class Ceiling' in Elite Occupations(nytimes.com ↗)
    1comments
  29. Proxmox runs QEMU-img convert with cache=unsafe; write errors are dropped(proxmox.com ↗)
    discuss
  30. No Easy Fix for Bogus Respondents in Online Opt-In Polls(pewresearch.org ↗)
    discuss

Ask HN: How do you interview devs in a post-AI world?

8 pointsby 1h ago
2 comments
Since the rise of AI coding assistants, about 80% of the dev candidates that I interview tell me that they aren't writing much code themselves anymore - they are directing agents instead. This makes me deeply uncomfortable (although maybe I'm just being old-fashioned). I still want to know that devs on my team can actually write code themselves, and have some idea of what they are doing when it comes to system design. This is increasingly challenging given how rapidly the AI tools are evolving.

I'm curious what other folks are seeing in a post-AI hiring landscape and how you are approaching candidates that tell you they are fully agent-pilled when it comes to their development process. Should I keep doing the conventional leetcode and design interviews? Or just give up and expect everyone is going to use Claude Code no matter what?

1h agoHN ↗

Leetcode doesn’t tell you anything apart from someone memorised set of questions and their solution.

For your question, I assume you want people who can solve problems, can explain their thought process and reasons of decisions. I did interview devs recently, and my questions were related to their experience in their CV. Something like, tell me about project X in Y company, what did you do, what did you use, why, what did you learn from it.

My personal opinion is that LLMs are no difference from developers who over engineer and over complicate things. You can get them to do good work with the right steering and right understanding of the whole system within the context of the company.

1h agoHN ↗

Recently, I was screen-interviewed for coding speed with a fairly easy project. The company used a 3rd party platform which gave me 90m to complete 4 levels, each one building upon the other.

I think that was a nice test, but the platform is too buggy to recommend.