jrcplus

Joined 11 years ago

Karma
118
Submissions
47
Member since
Sep 11
https://jrcpl.us

[ my public key: https://keybase.io/jrc; my proof: https://keybase.io/jrc/sigs/WNXTquNWcloOPtQ65S3bDLFsukcmx-uOOqUGsXDshPY ]

View on Hacker News

Recent submissions

Comment · 5 months ago
Any idea what the relation is between this (Aluminum OS?) and Android Desktop Mode?
Comment · 6 months ago
Elaborate please
Comment · 7 months ago
Greg Christie

My memory is hazy, but I thought drawers had a preferred side but would open on the other side if there was no room.

Comment · 8 months ago
+1. I got excited but https://lasuite.numerique.gouv.fr/ doesn't seem to be in English or any other European language. If you guys are hoping for Europe-wide adoption, start there.
Comment · 11 months ago
I remember.
Comment · 1 year ago
Another factor: I'm pretty sure it's more common that people have debit cards than credit cards in Europe, which equals less credit card fraud.
Comment · 1 year ago
Yes!
Comment · 1 year ago
Scrappy co-creator here. As an old-school Mac user (from the days of desktop publishing) I do know the difference between hyphen and en-dash and em-dash :)

We used AI sparsely for wordsmithing and definitely not for generating the text. Believe me, putting it together was a lot of work (Pontus did the heavy lifting).

Comment · 1 year ago
Scrappy co-creator here. I fully agree that software longevity is important. We designed Scrappy with a local-first architecture, so we have no traditional backend. Our only cloud dependency is a lightweight sync server. (We hurriedly added an FAQ with some more technical details after we discovered that this blew up on HN.) I believe this is an important point of distinction, both technically and financially, from most low-code/no-code tools which are SaaS'es.

One idea we had early on is the ability to save scrapps as single-page self-contained HTML files. We experimented with this but the functionality isn't currently exposed.

Comment · 1 year ago
Comment · 1 year ago
Idea: everyone, anytime you hit a bug or error, post a screenshot to the social media of your choice and tag it say #applesoftware. Over time this might start attracting PR attention, which seems to be most effective at getting Apple to do anything.
Comment · 1 year ago
I worked at Apple on Mac OS X until 2008. For QA, Bertrand believed in a lightweight touch, with dedicated QA staffing only at the top of the stack (plus a few key places like the filesystem), with the idea that any bugs will bubble up and be found through real-world usage. Most QA was informal, through heavy dogfooding.

You felt a real sense of ownership to the thing that you worked on. You worked hard and fixed bugs because it felt like it mattered, because you thought about how e.g. your mom would end up using the product, and also Steve Jobs would see it, so it had to be great. Also, teams were small. Something would involve only 1-2 people, and then we would look over at Redmond and they'd have dozens of people working on the same thing. The need-to-know secrecy was not just for PR value; it helped keep circles of communication tight, cutting out a lot of noise, so you could just focus. The organization was stable (and relatively flat, around 5 levels from junior engineer to SJ). I think in my 9 years or so there, there were no major reorgs. Avie phased himself out and retired, and Bertrand moved up. The only major disruption was when the iPhone project happened.

Release cycles were annual. Throughout most of the release cycle, it was pretty free up to each team and engineer to decide what to work on and how to prioritize it. Near the end of a release, it would get more and more strict on what you were allowed to change, up to the point where Bertrand sometimes would even ask to see code diffs.

I don't really know what is going on over there now. They have moved to a more agile approach, with more frequent integration checkpoints. In theory this should be better, but I suspect there's less sense of ownership and more of a feeling of a software factory. But it's probably mostly to do with the fact that the systems are way more complex, both the tech and the org, with way more moving parts. Even the programming language itself (Swift) is a moving target. I know (from talking to friends) there's a lot more politics and career-building going on, the kind of corporate douchebaggery that would not have been tolerated under Steve Jobs. People are thinking about RSUs and their promotions, rather than the products.

Ultimately, I think it boils down to this observation by jwz at Netscape, that there's "two kinds of people: those who want to go work for a company to make it successful, and those who want to go work for a successful company." Post-iPhone, Apple has filled up with the latter. A majority of the people at Apple now didn't work there under SJ, and the senior management who did experience that is now aging and retiring. At least from the outside, as a customer and end-user, it feels obvious that the founder-led product-obsessed culture is gone.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton