Recent submissions

Comment · 1 month ago
It’s so much worse than that. This happens to me on a daily basis with both MacOS and iOS. Say I’m searching for Chess, I’ll get to the C-H and it’ll show the Chess app, but enter that next -E and it’s totally gone. It feels like the system is designed like “Well, I showed them Chess when they entered CH, but they kept typing, so they must not actually want Chess.” This ends up breaking for me like 95% of the time, and the only way around it is to search like “C”…wait for results…”H”…wait for results…etc. It’s maddening.
Comment · 1 year ago
Honestly, terrible conditions. Factory-farmed style eggs. The “better” eggs were already at the $3-7+ price point depending on the feature set you’re looking for. Organic pasture raised eggs? Closer to the $7+. Plain brown organic eggs were closer to the $3 mark.

The egg industry in the US is a mess of marketing words that aren’t really regulated. Words like free-range, cage free, “access to the outdoors” often have little impact on the well-being of the chickens.

Comment · 1 year ago
Prior to the price spikes, it was relatively easy to find a dozen eggs for around or below $2.
Comment · 1 year ago
Easily? No. Within the bounds of the US Constitution, yes.
Comment · 5 years ago
Is it, though? I’ve given Plaid the user name and password to my bank account. The same set of credentials that I use to log in, to pay bills, transfer money, etc. Plaid stores this information for future use in some sort of reversible encryption. So now we trust Plaid to keep both their data set of user names and encrypted passwords secure, and also to keep their decryption keys secure. Forget that noise. Like the previous commenter , they’re one breach away from exposing millions of bank account credentials. It doesn’t matter if the Plaid API is read only for the integration side - somebody has MY credentials, and that’s not read only.
Comment · 5 years ago
Yeah m
Comment · 9 years ago
Seen this as well. Does somebody in management really expect leadership roles to sit down every 6 to 12 months, discuss everything their employees have done, and do it objectively? That's a fast track to giving everybody but the absolute worst a 5 out of 5 every time.

I'm a big proponent of the one-on-one approach, and giving feedback as needed. I am curious, however, typically the review cycle is correlated with the raise and bonus cycle. How would you go about handling that process with the data points that the review cycle provides, however artificial they may be.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton