Direct Current Data Centers
4 by jk_tech | 0 comments on Hacker News.
New top story on Hacker News: Data Activation Thoughts
Data Activation Thoughts
6 by galsapir | 0 comments on Hacker News.
i've been working with healthcare/biobank data and keep thinking about what "data moats" mean now that llms can ingest anything. some a16z piece from 2019 said moats were eroding — now the question seems to be whether you can actually make your data useful to these systems, not just have it. there's some recent work (tables2traces, ehr-r1) showing you can convert structured medical data into reasoning traces that improve llm performance, but the approaches are still rough and synthetic traces don't fully hold up to scrutiny (writing this to think through it, not because i have answers)
6 by galsapir | 0 comments on Hacker News.
i've been working with healthcare/biobank data and keep thinking about what "data moats" mean now that llms can ingest anything. some a16z piece from 2019 said moats were eroding — now the question seems to be whether you can actually make your data useful to these systems, not just have it. there's some recent work (tables2traces, ehr-r1) showing you can convert structured medical data into reasoning traces that improve llm performance, but the approaches are still rough and synthetic traces don't fully hold up to scrutiny (writing this to think through it, not because i have answers)
New top story on Hacker News: How to Win Friends and Influence People: Unrevised Version
How to Win Friends and Influence People: Unrevised Version
4 by MrBuddyCasino | 1 comments on Hacker News.
4 by MrBuddyCasino | 1 comments on Hacker News.
New top story on Hacker News: Show HN: uvx ptn, scan a QR, get a terminal in your phone
Show HN: uvx ptn, scan a QR, get a terminal in your phone
11 by yxl448 | 1 comments on Hacker News.
Scan QR → web terminal → vibe coding in bed. Mobile-first terminal via Cloudflare Quick Tunnel. No port forwarding. Feedback welcome.
11 by yxl448 | 1 comments on Hacker News.
Scan QR → web terminal → vibe coding in bed. Mobile-first terminal via Cloudflare Quick Tunnel. No port forwarding. Feedback welcome.
New top story on Hacker News: Standard Ebooks: Public Domain Day 2026 in Literature
Standard Ebooks: Public Domain Day 2026 in Literature
26 by WithinReason | 1 comments on Hacker News.
26 by WithinReason | 1 comments on Hacker News.
New top story on Hacker News: Ask HN: How do I help a colleague who introduces a lot of typos?
Ask HN: How do I help a colleague who introduces a lot of typos?
4 by tornadofart | 4 comments on Hacker News.
Happy new year! Weird question but here goes. My colleague has a strong work ethic, works hard, learns fast, goes out of his way to increase test coverage etc. I would say his contribution is net-positive but some of his work causes problems, especially when it comes to config files, shell scripting etc. His typo rate is quite high. I suspect an undiagnosed dyslexia. Mistakes are often caught very late, mostly in staging, making it cumbersome. It led to a few production outages. We have code reviews, a solid test suite etc. but typos are slipping through - once you make them, it's just harder for others to catch them. I feel bad for him because it already led to a blame game within the team, with some asking how one can be so sloppy. I don't suspect sloppiness because he is otherwise thorough. On the other hand, it escalated because the subject is very touchy with him. I suspect he is weirdly aware of the problem and in denial at the same time, and therefore extremely defensive. His take is that we should increase test coverage. It is part of the answer. However, once he's involved in writing the tests, the problem is shifted to writing correct tests. What I'm thinking about: - engineer the problem away: adjust our tooling and config mechanisms, less strings in our configs, less dynamically-typed scripting etc. - asking him to let AI review his code specifically for potential typos - increasing test coverage, with other people than him writing the tests What I am not considering: - Telling him I suspect he has dyslexia. I'm not a doctor. I'm trying to broaden my horizon on this issue, maybe I am missing something. What would you do?
4 by tornadofart | 4 comments on Hacker News.
Happy new year! Weird question but here goes. My colleague has a strong work ethic, works hard, learns fast, goes out of his way to increase test coverage etc. I would say his contribution is net-positive but some of his work causes problems, especially when it comes to config files, shell scripting etc. His typo rate is quite high. I suspect an undiagnosed dyslexia. Mistakes are often caught very late, mostly in staging, making it cumbersome. It led to a few production outages. We have code reviews, a solid test suite etc. but typos are slipping through - once you make them, it's just harder for others to catch them. I feel bad for him because it already led to a blame game within the team, with some asking how one can be so sloppy. I don't suspect sloppiness because he is otherwise thorough. On the other hand, it escalated because the subject is very touchy with him. I suspect he is weirdly aware of the problem and in denial at the same time, and therefore extremely defensive. His take is that we should increase test coverage. It is part of the answer. However, once he's involved in writing the tests, the problem is shifted to writing correct tests. What I'm thinking about: - engineer the problem away: adjust our tooling and config mechanisms, less strings in our configs, less dynamically-typed scripting etc. - asking him to let AI review his code specifically for potential typos - increasing test coverage, with other people than him writing the tests What I am not considering: - Telling him I suspect he has dyslexia. I'm not a doctor. I'm trying to broaden my horizon on this issue, maybe I am missing something. What would you do?