HN user

fengb

123 karma
Posts6
Comments29
View on HN

In retrospect, it makes a lot of sense. Genesis was huge in NA/Europe, but it was considered somewhat of a failure in Japan.

Sega has always floundered with its home consoles — they released 3 competitors to the NES after all. Genesis ended up being more of a one-trick pony than any indication of longterm success.

Mostly anecdotal opinion as a Chicagoan —

Our tech scene has been largely driven by fintech and a few unicorns. And our unicorns tend to be much more bust than boom — Groupon being the highest profile one. Not sure if it's correlation or causation, but VC investment tends to be more conservative, and the ones I do hear about are mostly fintech.

On top of which, Chicago wasn't all that tech friendly. Pay has been rather stagnant, and promotions above senior engineer didn't exist before Covid/remote stretched everything out. The exception to comp has been prop trading firms, which make oodles of money but... trader culture dominates over eng.

Lifecycles map closer to how the underlying UI layer works, but not to developer expectations. I've lost countless hours to desynced implementations such as failing to account for componentDidUpdate when overriding componentDidMount or missing a corresponding componentWillUnmount cleanup.

Li-ion cells provides 3.6V, which makes them incompatible with traditional alkaline or NiMH. I don't think we've invented a standard for Li-ion batteries yet.

A corollary to this is: the code should match the problem domain.

If the business problem is complicated, trying to further simplify the code usually makes it awkwardly abstracted and extra brittle. The fix should not be _just_ cleaning up the code, but rather trying to resolve the original usecase.

Stay-at-home dads explains 2 million of this article's main statistic. So even if the remaining 5 million of the "needs work", the employment number is closer to 89%.

Edit: there's a reason economists usually use "looking for work" for unemployment numbers: it's really hard to gauge why people don't look for work.

If you pay off the entire amount, you keep the device. If you upgrade before the contract ends, you have the option of paying off the remaining amount and keeping it (or returning it).

It's most likely a terrible idea to return the device instead of paying off and selling it, and AT&T probably makes free money from that, but the rest of the plan is pretty reasonable.

How is Yahoo doing better? Mayer has definitely changed a lot, but I'd argue that much of it is for the worse.

Her most prominent changes, stack ranking and acqui-hires, are pretty bad in general (inciting cutthroat competition and burning cash for disloyal employees).

I've always thought of semver as documenting common sense: fix bugs often, add features when possible, and don't break the public API unless you have to.

If all projects strictly followed semver, we wouldn't have this debate. But it's not semver's fault that some developers ignore common sense.