ryanbrunner

5 dni temudiscuss

There's some natural experiments that show that this happens, and is successful, when funding dries up a little. The early to mid 2000s were marked by a huge amount of bootstrapped companies that were quite successful. But VCs can distort a market to a huge degree and have huge effects on the labour market and even things like sales by preferring insider deals and introductions that it can crowd out smaller companies who can't outspend the VC-led companies.

ryanbrunner

5 dni temudiscuss

I've worked for startups that worked on genuine problems that had high customer demand, and there was still the problem of selling what the product could be instead of what it is. At least in my experience, it's omnipresent in B2B and has to be specifically handled regardless of how well your solution addresses a problem.

ryanbrunner

28 dni temudiscuss

It's great for document formatting. For app layout, it's very easy for the cascading aspect to shoot you in the foot if you're not careful (which is why even the most purist CSS writers will tend to layer abstractions or rules on top of it, even if it's only convention based ones without technology like BEM.

ryanbrunner

29 dni temudiscuss

I'd argue that it's impossible to have locality in all aspects. If your style, logic, and DOM are separated almost certainly you have a separation in domain - you're going to have styles, logic, and DOM concerned with "widgets" in your product and if they're separated by whether they are style or logic that means they can't be correlated by their "widgetness".

Really the decision comes down to whether it's better to separate based on style/logic/dom or on the business domain, and I think at least for web apps, separation by domain wins out in most cases.

ryanbrunner

29 dni temudiscuss

Artists and DJs are a separate category than what the original article is talking about, and I'd agree that there's more need for creativity in those cases (although I have definitely seen websites for people in more creative fields that have thrown usability and legibility out the window in pursuit of annoying "gee whiz" overly designed sites.

The mechanic is a separate argument - the article is talking about uniqueness of design and creativity, not cleanliness / orderliness. These sort of Tailwind designs are exceptionally clean and orderly, they're just predictable and not unique. To apply the article to your analogy, I wouldn't particularly care if my mechanic had the same coveralls that most mechanics wear as opposed to some unique design of coveralls.

ryanbrunner

29 dni temudiscuss

I like predictable UI even if it's a little "boring" because given the choice between utility and style, I'll choose utility every time. It is possible to make stylish things that also have very high utility, but it's a lot harder than favoring one, and I will always favor utility.

Take the author's example in this article - he calls out two things more than anything - a single sentence "pitchy" description of the product, and plan cards that look and feel extremely samey from site to site. I'd argue that both of these "downsides" are an upside for me as a consumer:

- Having a one sentence quick summary of what a product does allows me to make a quick decision about whether I'm interested in reading more about this product.

- Consistent plan cards lets me leverage my shared understanding of how plan cards work to instantly answer questions like what the monthly / annual pricing is like, what tiers are available, etc, that a bespoke presentation would require me to think about.

If I come to a landing page for a product, I'm more interested in answering questions like "is this a product I would like" and "how much does it cost" than appreciating the design of a page.

comments