This article is amazing. I think any engineer outside of programming language builders would get something incredibly useful for it.
Not enough engineers engage with the concept of code and programming and as an industry we suffer for it. The beginning of this post does a phenomenal job of simplifying very basic but high level concepts as “what is a function” “what is a tag”.
99% or programmers don’t think about these things like this, and so get confused when these building blocks are manipulated and presented in seemingly strange ways like React components or server components or whatever. By breaking down these concepts (functions, blueprints) and having rebuilding them with simple definitions it allows the reader to start their mental model fresh and go from there.
This is a masterclass in technical communication.
Who gives a shit if it’s long. In fact I’m glad it’s long because every sentence is gold. These are deep subjects and foundational to programming and so ya, talking about them like this can take a few words.
99% of people who take the time to really read and process this post will come away as noticeably improved developers. That kind of bang for the buck is rare!
On a relative and even absolute basis the wealthy will lose substantially more money.
On a personal quality of life basis the middle class will get hit the hardest. It will impact retirement timelines, vacations, home renovations, car purchases, etc. seeing their 401k go down will make them feel poorer and want to save more and thus reduce their discretionary spending and reducing the amount of fun and entertainment they enjoy.
The problem with steps 2 and 3 is that most of the time people aren't really sure they know what they want. They may have narrowed things down to a category, such as laptops as you mentioned, but even then you'd be hard pressed to find someone that absolutely KNOWS they want a laptop. Maybe a netbook + desktop would be a better combo? Or an iMac-style nettop. Furthermore, at any given time people are usually in the market for more than one thing, all at various stages of the buying cycle.
So now if we can simplify and treat all cases as "I don't know what I'm looking for" then follow-up to that is "I'm looking".
In that case the experience can be optimized around the looking and searching. I think the key concept in searching is, unsurprisingly, speed. Let me look at a lot of products quickly, let me research an individual product quickly, jump back out quickly, jump between categories, jump between different lists, sorts, filters, etc.
And I think pg is missing something, as the path doesn't end when a product purchase is made. You have all the nitty gritty of the actual transaction + shipping, but then you have post-purchase life as well. Most stores have you buy the product and then have you go somewhere else for support. Sure you can review the product on the store, but what if you want to hack it? or you have a problem? or you want to upgrade? etc etc. Is it up to the manufacturer at that point? What if you can't find the manufacturer's support resources?
We're doing some interesting things here at ProductWiki, but our goal is to create a great base of content and data. I imagine that one day a company will take the open data to create a really nice and innovative shopping experience.