HN user

pockmarked19

339 karma
Posts1
Comments81
View on HN

The first snippet of code makes me nauseous and the second makes me murderous, so the former is obviously better.

That being said, these people should all be miles away from mission critical code.

I wouldn't call json a schema.

What you see there is a protobuf, serialized as JSON. If a protobuf definition isn’t a schema, I don’t know what is.

Recently I was reading about blind people’s experience of Netflix having been poor (no audio descriptions) for years and years and the media never picking it up despite organized groups begging them to do so…until Daredevil was released and outrageous headlines like “blind people can’t enjoy a show about a blind superhero” became possible.

And of course, Netflix released audio descriptions post haste once the headlines hit…turns out it was trivial all along.

The moral of the story is, if you want it in the press, make it outrageous first.

Yes, but it’s the same level of garbage as “Facebook was built in a week”, where the hidden part is “after The Harvard Connection spent two years iterating on the product and got everything stolen”.

Society and people in general don’t want to hear these “sour grape” gripes. Unless they are the ones affected adversely.

Look their product up, look at their story, and consider this joke:

"Do you want to be a millionaire? If so send me $10 and I'll send you the instructions."

Let me put it this way: if someone came to you and their story was that they could never figure out how to make money from investing and decided to make money from telling others how to invest instead, what would you think?

The glimmer of hope here is that they have customers, who will with any luck guide them to a real value.

I’ve never met an artist who would prefer to make money by making a mockery of their art. Only people who are already dead inside do this (which, admittedly, some in poverty are).

Or rather, because Steve took great care not to hire the bozos most companies are staffed with. This is an extremely difficult and underappreciated thing to do, and Steve himself failed spectacularly at it on at least one occasion (which probably made him even more cautious).

Now, I could look at this relatively popular post about Google and revise my opinion of HN as an echo chamber, but I’m afraid it’s just that the downvote loving HNers weren’t able to make the cognitive leap from Gemini to Google.

WikiTok 1 year ago

Nice to know HNers don’t read past the first word. Can’t say I am surprised.

Not high level, you need to know exactly how it’s done. If you don’t at the start, then you will by the time you arrive at the working commit.

The exception (in that you must learn something) is in design, though. If you ask AI to add something to your API, and do it repeatedly, you will end up with a very poorly designed API, with separate endpoints for updating separate fields in the same record, etc, which will happily work fine.

Unless you knew what to do from the start, you’re going to make a lot of tech debt.

WikiTok 1 year ago

Your question doesn’t quite make sense.

Agreed, yet it is the standard question most people throw out for any unfamiliar idea. God forbid they have to form a single thought to grok something…although more charitably it is a form of “why should I care?”.

Your rephrasing is a bit different, it discards the selfish aspect of the question which I think is not correct.

Funnily though, anyone asking why they should care probably shouldn’t care yet.

Why can't people accept that their role in this new process simply isn't the one we've always called artist?

I think what has happened here is that you are talking about something very specific. Putting text into midjourney, maybe. That's not the only way people use AI in their art. Are "prompt engineers" artists? Maybe, maybe not, maybe not yet. Maybe they are only as much of an artist as I was back in 2005 while clicking "generate clouds" in Adobe.

We all have to start somewhere.