Hacker News: mpetrovich

New comment by mpetrovich in "The Website Specification"

mpetrovich — Sun, 31 May 2026 10:58:05 +0000

I suspect they ask for email first in order to determine whether to log you in via SSO vs. require a password.

New comment by mpetrovich in "PHP's Oddities"

mpetrovich — Sun, 24 May 2026 06:44:19 +0000

I found php’s array methods lacking as well. The inconsistencies are a pain. I ended up porting many of the methods from lodash, underscore, etc. to php: https://github.com/mpetrovich/dash

Maybe you’ll find it helpful

New comment by mpetrovich in "OpenAI Adopts Google's SynthID Watermark for AI Images with Verification Tool"

mpetrovich — Wed, 20 May 2026 02:37:02 +0000

Seems inferior to C2PA, which is actually an open standard: https://contentauthenticity.org/

New comment by mpetrovich in "GitHub is investigating unauthorized access to their internal repositories"

mpetrovich — Wed, 20 May 2026 02:30:12 +0000

If that’s true and they do intend on shredding their copy on sale, what stops GitHub from buying it back themselves? (through a proxy, obv)

New comment by mpetrovich in "You need to calm down"

mpetrovich — Wed, 13 May 2026 12:12:53 +0000

AI isn't changing the fundamentals of building software. It's changing the speed. Don't confuse the two.

You need to calm down

mpetrovich — Wed, 13 May 2026 12:12:53 +0000

Article URL: https://petro.blog/you-need-to-calm-down-71a177c99c9f

Comments URL: https://news.ycombinator.com/item?id=48120895

Points: 1

# Comments: 1

New comment by mpetrovich in "Show HN: Turn any workflow diagram into compilable, running and stateful code"

mpetrovich — Sun, 18 May 2025 08:01:45 +0000

Some feedback: show example input & output without requiring me to create an account.

Looks interesting, best of luck!

New comment by mpetrovich in "Show HN: An API that takes a URL and returns a file with browser screenshots"

mpetrovich — Thu, 06 Feb 2025 20:45:47 +0000

Reminds me of this open source library I wrote to do the same thing: https://github.com/nextbigsoundinc/imagely

It uses puppeteer and chrome headless behind the scenes.

New comment by mpetrovich in "Show HN: AI Generated (Not-Real) User Avatar Images for Development Needs"

mpetrovich — Sat, 17 Feb 2024 17:10:02 +0000

Good point. What if we combined the best of both: more realistic images from tpdne.com and API-accessible metadata from your site?

Seems like a matter of crawling the former to get all the images and then tagging them and serving them via your API.

Anyway, I think your approach is great and only wanted to propose a possible approach to the original feedback above :)

New comment by mpetrovich in "Show HN: AI Generated (Not-Real) User Avatar Images for Development Needs"

mpetrovich — Sat, 17 Feb 2024 13:28:57 +0000

Perhaps something powered by thispersondoesnotexist.com would better for that. That site returns completely AI-generated faces that seem much more realistic and candid.

New comment by mpetrovich in "ChatGPT is now a brilliant tool for winding up telemarketers and scammers"

mpetrovich — Sat, 01 Jul 2023 13:37:34 +0000

The demos on the Jolly Roger site are hilarious. The bot sounds so realistic, and the bot even had the audacity to ask the scammer, “Are you a real person?!”

“Hold on, there’s a bee on my arm”

New comment by mpetrovich in "Is ORM still an anti-pattern?"

mpetrovich — Tue, 27 Jun 2023 20:56:26 +0000

In my career, the biggest problem with ORMs I’ve used is something the author touched on:

They can be terribly leaky abstractions. It seems that many ORMs end up re-implementing SQL in their own domain-specific language.

However, an understanding of SQL is often needed to debug and optimize ORM queries.

So why not just use SQL directly then?

New comment by mpetrovich in "The Messy Page Or: why I don't like greenfield projects"

mpetrovich — Sun, 07 May 2023 15:00:14 +0000

My goodness, this describes me perfectly as well. The countless choices of a blank slate brings anxiety to a recovering perfectionist like me. Do I choose A or B or Z?

I prefer improving things rather than creating them from nothing. I’ve come to a similar conclusion as the author as far as how to get out of the fog of greenfield: Satisfice instead of optimize.

In this context, optimizing refers to choosing the best among N options. In contrast, satisficing means choosing the first option that’s good enough. Often, the opportunity cost saved from satisficing is greater than the marginal value gained from optimizing.

New comment by mpetrovich in "U-Bahn station in Berlin is decorated with radioactive uranium glazed tiles"

mpetrovich — Tue, 07 Feb 2023 13:07:28 +0000

No, he’s talking about the movie. You know, the one with the sub.

New comment by mpetrovich in "Enabling the Future of GitHub's REST API with API Versioning"

mpetrovich — Tue, 29 Nov 2022 00:04:49 +0000

Oh, so you’re saying that omitting the version from the header will ALWAYS return this specific version, NOT the latest version?

That certainly addresses the footgun I mentioned.

EDIT: From the docs: Requests without the X-GitHub-Api-Version header will default to use the 2022-11-28 version.

New comment by mpetrovich in "Enabling the Future of GitHub's REST API with API Versioning"

mpetrovich — Mon, 28 Nov 2022 23:34:05 +0000

You’re saying that it’s LESS likely to specify the API path at the callsite than the HTTP header? o_O

New comment by mpetrovich in "Enabling the Future of GitHub's REST API with API Versioning"

mpetrovich — Mon, 28 Nov 2022 23:18:13 +0000

I agree with you, so then why not stick with the previous /api/v2 url approach?

And it would annoy me far more if my app that talks to GitHub inexplicably breaks in a few years because of a release I wasn’t aware of.

These changes make no sense to me.

New comment by mpetrovich in "Enabling the Future of GitHub's REST API with API Versioning"

mpetrovich — Mon, 28 Nov 2022 23:02:30 +0000

Making the version optional is a bad idea, IMO. It lets consumers use your API without versioning, which is like telling them, “here, create a time bomb that may or may not explode when the next breaking api change is released.”

There’s zero practical user benefit to NOT specifying the version, so why not enforce it? You’re creating a footgun otherwise.

Furthermore as others have pointed out, this is a purely cosmetic change. Using /api/$UNIQUE_STR in the URL vs. X-GitHub-Version: $UNIQUE_STR in the header are functionally equivalent, so…

Why bother making this change then? What was suboptimal about the previous way? What benefit does this bring?

EDIT: Serves me right for not reading the docs more carefully. From the docs [1]:

Requests without the X-GitHub-Api-Version header will default to use the 2022-11-28 version.

See phphphphp’s reply below for context.

[1] https://docs.github.com/en/rest/overview/api-versions?apiVer...

New comment by mpetrovich in "Intentionally making close friends"

mpetrovich — Mon, 28 Nov 2022 20:25:00 +0000

The systems angle mentioned later in the article may seem a bit …engineered, but it works!

I’ve moved a ton in my life, and I have an annoying habit of losing touch with friends when I move away. Out of sight, out of mind, ya know?

Anyway, to combat this annoying habit, I started scheduling monthly phone/video calls with each of those friends. It’s been a game changer, especially as folks have kids and busy lives.

New comment by mpetrovich in "Show HN: I made a sliding puzzle game"

mpetrovich — Sat, 26 Nov 2022 17:41:43 +0000

I hadn’t considered it since it’s mobile-first, but that’s a great idea to try!

I imagine that the arrow keys would control the movement of the empty space, right?