deepfriedrice

Agreed. It's hard to believe that marketing pages, after decades of evolution and testing, haven't landed on what users actually want, rather than what they say they want.

Scrolling is such a natural behavior for internet natives. Being able to leverage a large screen to visually compare things has its place, but the article uses a horrible example:

> Our condensed product page prototype took the same information from the original dispersed page and arranged it in a 2x2 grid that allowed users to compare multiple services simultaneously, without having to remember the details of each service.

What's to compare? They're disparate services.

I do like the example of the product specifications. But that was more of an objective usability issue: requiring more clicks for more information.

Crazy idea. 2 factor authentication for the elderly where the second factor is, where applicable, a younger family member. It's socially irresponsible to allow the tech-illiterate to move their live savings around on the internet by themselves.

The article references Lockdown mode [0] which appears to be Apple's solution for this (and other) class of zero days.

[0] https://support.apple.com/en-ca/HT212650

> everyone else uses GraphQL incorrectly

Quite a hot take but I can't disagree. I was one of the people using GraphQL incorrectly for the longest time. I always knew something was off, that we might as well have just been using rest, but could never really articulate it.

Alan's article is a great read, thanks for sharing.

Had the same thought. With AWS et al. it's just too easy to use the same instances and avoid that variable.

The suggestion isn't to bypass, but to surface a missing use case to the relevant folks

> their solution, instead of getting rid of the 1000 cuts is to apply more band-aids

That's engineering at scale. It's impossible to remove more than a small fraction of those cuts within any reasonable time frame.

> This industry dug its own grave

The industry found a way to retain talent for cheap, a. la "I'll never leave my current company at this point"

I wish I could justify using SQL more. It's just way too easy to use Dynamo. Unless my data is complicated enough to warrant a relational model, it's going in Dynamo.

Random question: Why are there so many emoji "implementations"? I understand copyright, but is it really cheaper/easier/preferable for all these different companies to design their own emojis?

I was able to open "The technical interview [LEAKED]" without a dropbox account. Just had to close the login modal.

Since I saw almost no positive comments I'll throw my hat in the ring. I love stuff like this. I learned a handful of things to toss in my back pocket for future projects/hacking. Remix looks fascinating, albeit young and closed-source. I've been wanting to play with Prisma & MSW for a while, so it was great to see how he used them. His DX looks top-notch, I love hacks like his "server side HMR" [1]

Is it over-engineered? Maybe. Who cares. HN is so worried about juniors taking his architecture as gospel. Does the liquor store clerk have to tell me not to drink too much too fast? Juniors are going to over-engineer something regardless, it's one of the most valuable lessons they'll learn the hard way. The rest of us can read this piece, think critically, and maybe learn some new things.

[1] https://github.com/kentcdodds/kentcdodds.com/blob/main/index...

It's actually:

Your activity might still be visible to: * Websites you visit * Your employer or school * Your internet service provider

"might" makes sense because some or none of those may apply, depending on how you're using the browser.

The cdc [1] has some figures that show a remarkably clear trend upward after ~2007. But IIRC it's pretty even across gender.

[1] https://www.cdc.gov/nchs/data/databriefs/db352-h.pdf

What's wrong with solving problems the unix guys already solved decades ago, and doing so less elegantly?

Amazon uses it

Love the explanation of the DAA instruction. I wrote a gbc emulator in college, but couldn't figure out what that instruction was supposed to do.

I ended up just copying a lookup table from an open source emulator at the time, which of course didn't help my understanding: https://github.com/visualboyadvance-m/visualboyadvance-m/blo...

Funny to finally realize what this does, and now see how the lookup table works.

good stuff, thanks!

How did they find out he originally posted under his real name? They must have known that was his profile, and then SO handed over the data proving it?

I looked through the code. The model indices may have been generated, but literally everything else looks hand written (albeit probably lots of copy paste).

He doesn't even use any libraries for the 3d math, input, rendering, etc. Pretty inspiring.

Good stuff.

I don't get the example for #3. I understand using "unknown" instead of "any", but both examples look effectively the same in terms of type safety.

I also don't get the example for #4. Side effects are the inherit "blind spot" of TypeScript. If you're really worried about your API changing on you, it seems like you'd be better off modeling it in something like JSON schema. Unless maybe your API is trivial.

You can also get it with almond milk reduce it by another 1/3

Everyone I know does some variation of this. I'm currently enumerating gen 1 pokemon.