HN user

guffins

56 karma
Posts2
Comments32
View on HN

Correction: I wasn’t aware of OpenAI’s “evals” tool. If that’s the kind of thing the author was referring to, I may have misjudged.

Part of me hates how certain ways of writing have been designated as hints that something was written by AI… I love using em dashes, for example. But yeah, ChatGPT models tend to overuse weird abbreviations of common words in a way that humans never do.

I’d say “in an eval” when talking on Slack with very close coworkers, but _never_ on a public post.

Still, I don’t want to make accusations based on writing style, because like I said, I have my own idiosyncrasies that common models coincidentally share.

That’s a great question. ISO 8601 doesn’t allow timezone offsets on date-only strings.

If you were born in the US, can you buy cigarettes at 12:00 am on your 18th birthday in London?

I’ve never heard of age verification laws caring what timezone you were born in. In fact, you couldn’t even pinpoint this from many people’s ID cards. Plenty of US states span multiple time zones, and I wouldn’t be that surprised if there were a maternity ward out there sitting on a TZ line.

Location: Atlanta, GA, United States (UTC -04:00) Remote: Yes

Willing to relocate: No

Technologies: AWS, Terraform, GitHub Actions, Python, PostgreSQL, shell scripting, etc.

Résumé/CV: https://gmarmstrong.dev/resume.pdf (or as HTML: https://gmarmstrong.dev/resume/)

Email: public AT gmarmstrong DOT dev

I'm a DevOps/SRE engineer focused on infrastructure automation, CI/CD, and cloud environments. Most recently working on Terraform, IAM centralization, and observability at New York Public Radio. Looking for roles in platform engineering, DevOps, SRE, etc.

Location: Atlanta, GA, United States (UTC -04:00)

Remote: Yes

Willing to relocate: No

Technologies: AWS, Terraform, GitHub Actions, Python, PostgreSQL, shell scripting, etc.

Résumé/CV: https://gmarmstrong.dev/resume.pdf (or as HTML: https://gmarmstrong.dev/resume/)

Email: public AT gmarmstrong DOT dev

I'm a platform engineer focused on infrastructure automation, CI/CD, and least-privilege access control in cloud environments. Most recently working on Terraform, IAM centralization, and observability at New York Public Radio. Looking for roles in platform engineering, DevOps, SRE, etc.

Location: Atlanta, GA, United States (Eastern Time)

Remote: Yes

Willing to relocate: No

Technologies: Python, Java/Kotlin, Terraform, AWS/GCP, PostgreSQL, CI/CD, shell scripting

Résumé/CV: https://gmarmstrong.dev/resume.pdf

Email: local-part “contact” at that domain name

Web presence: https://gmarmstrong.dev/identity

Backend software engineer passionate about security at every level.

Specialist in data privacy, CI/CD, DevOps, and SRE. Bonus experience in browser automation, web scraping, data engineering, and cost optimization.

Highly proficient in Python. Experienced with Java and Linux/NixOS. Just getting into Rust, Kotlin, and Go.

This is my experience exactly. I’ll add to the list of inconveniences:

- hyperlinks in iMessage/SMS aren’t clickable (but they can still be copied/pasted)

- installed apps that use JavaScript in their interfaces can have the same issues as websites (but you can turn Lockdown off for apps as well, if needed)

Overall worthwhile. Something about these “inconveniences” also gives me a sort of psychological disconnection from my phone that I personally find to be very healthy. Similar to how I felt limiting myself to F-Droid in my Android days.

I’m on my phone and haven’t double checked this, but from my understanding, I believe it’s part of an effort to encourage compatibility with other tools like podman. The ambiguity is somewhat intentional, as an active decision to separate the implementation name from the configuration standard.

They may work as advertised, but the problem is that the cables themselves have no indication of what was advertised in the first place.

The ability to know what the cable you’re holding can do is just not there. Unless you have some way of ensuring that all your cables are the same, you need to:

- discard/donate every cable that you can’t identify (as @brookst did) by its eMarker (though they’re required by spec) unless you own a specialized USB-C voltmeter or multimeter

- manually label every cable with all its unique specifications, either after running it through an eMarker reader or immediately after taking it out of the box

I don't have time to look too closely into it, but my guess is that it's a bug somewhere in the parser: https://github.com/muffinista/gopherpedia.com/blob/main/pars...

The markup behind that article isn't terribly complicated, but the parser isn't perfect either. For example: https://gopherpedia.com/gopherpedia.com/Gustave_Dore has some glitches in the lead sentence.

My suspicion was that it's getting confused by the line above the intro, but I pasted the article's source code into Wikipedia:Sandbox and gopherpedia read the intro just fine. Strange!