EricHolden12

inside job /exit strategy.

Cheaper steam engines meant more coal burned, not less.

inb4

- Don’t me think steve krugman - Design of everyday things - something by nielsen norman

…

seriously: - The best interface is no Interface - Collaborativeproduct design - orly -

But now they’ve allowed alternative app stores so why are PWAs still required?

Patient care apps as PWAs? Yikes.

Such a sensationalist post.

The ramble about designers being responsible is very shallow. “Designers” at these companies don’t have much say in what needs to be designed, they just have to figure out how it will look.

From coffee makers to software, there are plenty of people and companies that have the “do one thing well” ethos. You just have to be willing to pay a premium because in the modern age of global capitalism where making something abundant and cheap is easy, the opposite is much harder.

You fell for the Keurig meme. You want a coffee maker that just makes damn good coffee and will last you a long time? Get a solid italian made espresso machine. Or a Moka Pot, or a Chemex.

You spent $12 on a coffee maker (Westinghouse? Black and Decker? Sunbeam?) and yes it’ll make you a cup of black coffee, but nobody wants just black coffee. I want my black coffee to have hints of orange, chocolate, and citrus. I don’t just want black coffee.

Same with software. Simple doesn’t mean “black cup of joe” which would be akin to a command line app.

Simple means something intentionally made that sweats the smallest details within a specific function. I want my software to do one thing well, but be delightful to use. I want it to be fast, I want it to look nice, I want it to be simple and easy to use. And if it is all those things I will pay a premium for it.

“Things” app is an example that comes to mind.

Another thing that helped imessage cement its position was that teens often had an ipod and you could use imessage on an ipod, so those teens talking to their friends were using imessage and when they switched to iphone that mental model carried over. Blue bubbles were familiar and green bubbles were alien.

This whole debacle has somehow made Apple. responsible for fixing SMS, which is not their job to do so.

I really hope Apple holds their ground and doesn’t cave to this pressure to make iMessage more interoperable.

For the longest time nobody batted an eye to iMessage, claiming it’s garbage and suddenly when it’s grown to the size, feature set that it’s at now there’s a mark on it.

Blue vs green bubbles is a subtext of an unspoken class system:

iPhone = for rich people Android = for poor people

Thus if you’re a teen and you have a green bubble, you are poor.

You are a great example.

It’s this mentality which is the problem — that only PMs are thinking about customer/biz success and so they must prioritize and figure out what everyone should work on and when it should be done.

Let’s do a rewrite in Rust. What does this engineer know that we don’t? Why would they say something so incredulous. What if they are thinking about the customer and biz but from a different angle.

Builders - people writing code and designing the actual functionality and experiences somehow became strictly “resources”. The thing that made tech great and allowed for so many companies to flourish was the tech/geek/nerd/hacker spirit that let those who write code decide what to do and how to do it.

Now, we’ve McKinsey’d the whole thing into boring processes that make work for people who don’t design or code. Jira, Google Docs, Slack, etc etc etc

You buy a first class ticket for an airline and you get access to the lounge in the airport with fast wifi and snacks.

Outside there are people with different tickets screaming to be let in because they know someone in there and it’s not fair that they can’t go in.

And Migicovsky is on the side trying to dig a little tunnel into the lounge.

iMessage is a perk of using an iPhone. You want to use iMessage? Get an iPhone.

Frameworks have chosen to add abstraction layers that “simplify” writing code because it makes it easier for the not so great programmers to write code.

This has been desirable for one main reason: making writing code easier for the surge of new programmers entering the field. It’s the reason Facebook made React — the people they were hiring out of college were smart and capable but we’re not nerds about the technology.

The biggest proof of that is how many devs are still scared of CSS and don’t feel comfortable writing it, and why the adoption of Tailwind has surged.