Hacker Newsnew | past | comments | ask | show | jobs | submit | derivagral's commentslogin

I had always thought the primary focus on single-payer was risk pool economics, not administrative efficiency.

https://en.wikipedia.org/wiki/Risk_pool


> buyers think they’re buying domestic

This is hard to tell from the discussion, but are you defending this practice?


> this also loses you taste

I won't forget the in-person interview round where I coded a frontend visualization for a data graph (tracking global shipping), then fielded a post-work general interview round from the whole company (~10 ppl) about specifics and "choices" made during a rush to finish. I ended up not going due to comp, but they were acquired months later. Life is funny.


Late thought, but you could set up "beacon" locations for each client to pull a local grid derived from coordinates?

Wouldn't solve that 1s latency thing, but might be interesting in other applications.


That free upgrade refuses to work with my hardware. I am glad they are continuing security, but they are literally forcing me to install another OS (as I understand the security difference).


This project improves the AI, but might not be quite what you want?

https://github.com/induktio/thinker


> "feel" systems

I used to play a tcg a bit too seriously, and sometimes seeing incorrect game states would trigger something. Part of tracking game states and derivations I guess. Only sometimes helpful in software.


Even the article points out this analysis includes both condos and single-family homes, despite their wildly different demand situations.


The average consumer now sees mostly ads above the fold. Also, lots of internal stuff like this coming out. Not sure how this is meant to benefit the consumer aside from "they have to love what we deign to give them."

https://searchengineland.com/google-ads-search-and-chrome-bo...


Some time ago, this was important to decipher the marketing behind MongoDB. Their benchmarks ran with a loose isolation (read_uncommitted iirc) that didn't guarantee a durable flush, and they'd benchmark against defaults from postgres, etc, which didn't use this isolation.

Clearly it worked for them, but I spent a few different stints cleaning up after developers who didn't know this sort of thing.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: